Automatic tracking you can switch off, cached tokens, sub-agent runtime, and more
Automatic tracking you can switch off
Your working hours are applied to work that has already happened. If your hours are irregular, that was mostly a guess, and there was no way to turn it off. Settings → Time Tracking now has three switches, each on by default so nothing changes until you choose:
| Switch | Off means |
|---|---|
| Working hours | Nothing backfills to a start time, a day left open closes at its last activity, and a first commit with nothing before it stays at 0h until a clock-in or an agent session opens the day. |
| Same-day backfill | No fill from the start of your day, and no fill up to a clock-out on the same day. |
| Between-days backfill | No entry for a day left clocked in, and no carry-over across midnight. The day still closes. |
The welcome flow asks up front: I work set hours or My hours vary, and only asks for the range if your hours are set. Automatic tracking describes what a day looks like with each switch off.
Cached tokens on their own
The AI agents report used to show one token total per period: input, output and cache reads and writes added together. On a long session most of that is the same conversation being re-read every turn, so it came out far above anything your agent's own screen shows.
Tokens are now split into cached, fresh and output, adding up to the total, with the share of input that came from the cache. The split is shown for the period, per model, and per ticket, where it's divided on the same share as the ticket's cost.
Runtime counts every agent, not just the one you talked to
Claude Code's active time measures the main conversation and nothing it hands off. A session that fanned its work out to sub-agents recorded only the coordinator, so the busier your agents, the more runtime went missing. Sub-agent runtime is now counted too. Cost was never affected.
To send it, update to CLI 0.4.0 and run clocktopus agent setup again. It adds the missing settings without a teardown. Until then, clocktopus agent doctor reports not being sent: sub-agent runtime.
Fixes & improvements
- The Tokens column is back on the AI agents table.
- Rows in the ticket ledger add up to the project row above them, to the last digit shown.
clocktopus agent statusno longer claims there's no matching project for unattributed sessions, which is only one of several causes. It points you toclocktopus agent doctor, run in the checkout, to find the real one.- The docs and the ledger spell out the difference: Unattributed means no project, No ticket means a project but no ticket.
- The runtime tooltip says sub-agents and agents running at the same time each count, so runtime can be longer than the time on the clock.