Yojo
client · billable4 commits yojo/care-app — consent flow · 2 messages #care-eng at 08:47
AI-era time tracking
You never pressed start.
Clockhound reads your commits, calendar, chat and deploys, works out where the day actually went, and asks you about the holes. It proposes. You rule. Nothing it reconstructs counts until you say so.
Tuesday, reconstructed — confirm a record and watch it settle
Clockhound · day book
Tuesday 4 August
6 records found. 2 ruled, 4 waiting on you.
worked 10:18
ruled 3:10 of 10:18
ruled 3:10 of 10:18
0:53
09:05–09:30 — Nothing at all. Coffee, or off-screen work?
Yojo
client · billable11 commits yojo/care-app · calendar “Care sync” 10:00
confirmed 09:41
Clockhound
internal · not billable9 commits weisheme/clockhound · deploy mcp@0.4.1
confirmed 12:44
12:40–13:25 — Quiet for three quarters of an hour. Lunch?
Ongelukje
equity · billable6 commits weisheme/ongelukje — claim intake · review on PR #212 at 14:10 · 14 messages #ongelukje
15:50–16:10 — Twenty minutes, nothing.
Yojo
client · billablereview on PR #488 · calendar “Vendor call” 17:00 · 45m · 2 deploys care-api
18:35–20:40 — Two hours dark. Dinner, or off the keyboard?
Clockhound
internal · not billable7 commits weisheme/clockhound — grill verbs · no calendar, no chat
How it works
Reconstruct, don’t stopwatch.
01
It follows the trail
Commits, calendar events, chat, deploys, mail. Read by your Hound in your own Claude and reported in — the server never fetches and never polls; there is no always-on process watching you work.
02
It proposes a day
Claude reads the signals and writes work records: this stretch, that project, this evidence. Every one arrives proposed — legible, and visibly not yet a fact.
03
You rule
Confirm, reject, retime, move it to another project. Where nothing happened at all, it asks instead of guessing. Only what you confirm can ever reach an invoice.
Billable, not billable, and the overshoot
The hours you can’t charge are still hours.
Every record lands on one side of the money axis or the other, per project and per contract. When a client’s cap is reached, the work over the line does not vanish and does not get quietly rounded away — it is named. That number is overshoot, and it is the one this whole thing exists to show you.
Equity time is hours against something that isn’t cash, and it is tracked exactly as carefully. Internal work is nobody’s invoice and still worth knowing.
Where the day went
Billable · Yojo5:03
Billable · Ongelukje (equity)2:25
Not billable · Clockhound2:50
Worked10:18
Billable after Yojo’s monthly cap4:00
Overshoot1:03
Chargeable today€500.00
Provisional. Confirmed hours only: 3:10, worth €218.75 — the rest is still the hound’s word, and no batch will take it.
Flex & vacation
Bank the hours before or after the fact.
A Saturday worked in March can pay for a Friday taken in June, and the entry knows which day it counts toward — not just when you wrote it down. Overdraft is allowed, because real weeks work that way.
Daily summary
The “what got done” writes itself.
A short narrative for each day, drawn from the same signals as the records — so standups, client updates and your own memory of last Thursday all come from evidence rather than recall.
MCP-first
Every capability is a tool before it is a screen.
Clockhound is an MCP server first and an app second. Your assistant reads your day and makes your corrections in the place you already work — the day book is where you go to see the page, not the only way to keep it.
Everything is scoped to you. The tools act as the account you connected, on its own data. A day stays an estimate until you close its period, and nothing that returns hours will hand you an estimate shaped like a fact.
- mint_hound_tokeneach Hound’s own key — it reports its signals, reads them back, nothing else
- report_signalsyour Hound hands in what it read; the server never fetches
- get_day_recordsa day as your signals read it now — an estimate until its period closes
- edit_day_rangesay what the signals got wrong: not work, the bounds, another project
- close_periodpreview, then close — the days freeze into the only hours a batch bills
- get_worked_hoursyour hours, derived live — never stored
- bank_flex / draw_flexhours banked before or after the fact
- open_batch / submit_batcha closed period becomes a batch; submitting freezes its money
- assign_invoicethe sent Odoo invoice marks them billed
- get_daily_summarythe “what got done” narrative, written for you
Early access
Built for one engineer with too many clients.
Clockhound is being built in the open by weisheme, against its author’s own week — several clients, a couple of equity-earning startups, and the overshoot that comes with both. If that is your week too, say hello and you’ll get it early.
or mail erik@weisheme.io