Human effort, agent execution, and billable time
Timerrr records human effort, agent execution, and waiting separately. A work receipt connects those measurements to a client, a task, notes, and optional artifact links. An agent can propose a timesheet; a person reviews it before entries are created.
A concrete example
You spend twelve minutes reviewing a checkout fix. An agent runs for twenty-six minutes, with four minutes overlapping your review. If those intervals cover the entire session, elapsed time is thirty-four minutes. The receipt reports twelve human minutes and twenty-six agent-minutes. The proposed time entries contain the recorded human intervals.
Execution records are evidence, not proof of continuous effort
A runner records how long a command is alive, including any waits inside it. MCP tool calls can report actor transitions, but a model may miss a transition. Artifact timestamps do not establish how long someone worked. Timerrr preserves source labels and flags disconnected agents rather than inventing missing hours.
What happens when an agent disconnects?
An agent execution interval uses a 120-second lease. Heartbeats renew it, normally every thirty seconds. Recorded execution ends at the earlier of the last lease expiry or the session’s agent budget deadline. A receipt can still include up to 120 seconds of uncertainty after the last heartbeat. Server reads cap the duration even before an expired span is finalized by the next write.
The budget is an elapsed deadline from session start; parallel agents share that deadline. It is not a pooled agent-minute budget. The optional runner terminates its local command at the cutoff. An ordinary MCP client must honor the returned deadline and continue_work flag itself.
How a draft becomes a timesheet
- Finish work sessions and attach useful references.
- Choose a date range of up to 93 days. Only finished, unreviewed sessions fully within the range are included.
- Review the proposed human intervals, edit their notes and boundaries within the session, or exclude them.
- Approve the draft in the website. Overlapping human intervals and overlaps with existing entries are rejected.
- Use the existing Timesheets screen to generate a CSV at the client’s configured hourly rate.
Agent execution and explicitly recorded waiting are excluded from proposals. A session without human activity produces no proposed hours. Review finalizes all sessions in that draft, including excluded intervals, and records the decision in their receipts. Existing entries can still be corrected through the Entries screen.
What is included in a work receipt?
The session title and client, server timestamps, actor intervals, execution leases, budget, source-labeled events, artifact URLs, warnings, and human review outcome. The original evidence is retained when review adjusts proposed time. Download a receipt as JSON from Agent work.