Check coverage
Ask for an invoice or timesheet and the agent checks the period first: what is tracked, what is already aggregated, what is missing a rate or a client.
It answers from your measured sessions, commits, and invoices, and only changes something when you confirm it.
Confirm before anything changes
Draft an invoice, approve timesheet items, attach an issue to a session, and the agent proposes the change instead of making it. You see the card, you click Confirm or Cancel, and that's the only way anything moves.
The hours are in Sessions. The billable ones are in Timesheets. The invoice is in a different screen entirely, and the team numbers live somewhere else again. Asking "what can I invoice for Acme this month" should not mean opening four pages and doing the subtraction yourself.
Ask for an invoice or timesheet and the agent checks the period first: what is tracked, what is already aggregated, what is missing a rate or a client.
If the period has not been aggregated yet, it proposes running the aggregation. One click builds the timesheet items.
It lists what is pending and proposes approving it. Confirm, and those items become ready to invoice.
It proposes the invoice draft itself. Confirm creates it. Nothing is ever sent from here. Push to Xero from the Invoicing page, same as any draft.
What it returns
"What did I do on Project A last week?"
"18.4h across 11 sessions, most of it Tuesday and Thursday. Longest session: 2h 40m. 14 commits, all on feature/project-a-auth."
"Aggregate June for Acme and show me what's still unapproved."
"June aggregated: 22 work items, 61.2h billable. 14 already reviewed, 8 pending. Want me to propose approving the pending ones?"
"Draft the July invoice for Acme, unbilled only."
"34.5h ready to invoice across 2 projects. Proposing a draft invoice. Confirm to create it."
"Who logged the most agent time on the team this month, and what's Client B's project status?"
"One teammate led agent hours at 38% of the team total. Client B's shared project shows 3 contributors and 46 commits this month, all covered by the workspace commit report."
Boundaries
Two ways to ask
| Capability | Agent (/agent) | MCP server |
|---|---|---|
| Where you use it | In the DevClocked web app | Your editor or terminal (Claude Code, Codex, Cursor, and others) |
| Auth | Your signed-in session | A DevClocked API key |
| Reads | Sessions, timesheets, invoices, token usage, delivery and issue reports | The same personal read tools |
| Writes | Proposes changes you confirm: invoices, timesheet items, issue links | Read-only |
| Team data | Team analytics, roster, shared-project rollups, workspace commit report | Not available |
Everything you need to know about DevClocked
Pro and above, and it is included in the free trial. Free accounts see it in the sidebar but need to upgrade to use it.
A general-purpose language model configured on our end. We do not commit to a specific vendor in the product, since the model behind it can change without changing what you can ask.
No. Your conversations are stored so you can come back to them, not sent anywhere for training.
Yes, any time, from the agent page. Deleting removes the conversation and its messages.
If you are in a workspace, yes. It can answer team analytics, roster, shared-project rollup, and commit-report questions, with analytics, rollups and commit reports scoped to the last 90 days and at the same day-level detail the Team Analytics page shows. If you are not in a workspace, those questions do not apply.
A few reasons: the question needs a plan you are not on, it asks about a workspace you are not a member of, it asks for a window longer than the tool allows, or the request tripped a content filter. It will tell you which.
One operating layer for humans and agents shipping in parallel.