Hatchlog troubleshooting
Most problems clear from the app. If an agent can't see Hatchlog, run Repair in Settings and start a new session. If a card didn't move, check the agent is connected and the task is in Todo. If token numbers look low, tracking may be off or the work was done by an agent that isn't measured.
The agent doesn't see Hatchlog
Open Settings → Agents and choose Repair for that agent. Repair puts the connection back. Then start a new session — the Hatchlog tools load at the start of one.
You can confirm it with Test connection in the Connect agents sheet. See Connect Claude Code for the exact steps.
A card didn't move
An agent only starts the top task in Todo. If a card sat still, check it's in Todo and not Backlog, and that the agent is still Connected.
The agent moves a card when it works on it, not on a timer. If it hasn't run since you added the task, start a session and ask it for the next task.
Token numbers look low
Three things explain a low number. Token tracking may be off — turn it on in Settings. The work may have been done by Cursor or Codex, which aren't measured. Or it happened before you turned tracking on, so it shows as Untracked.
For what each label means, see Token cost.
Still stuck?
The agent still can't see Hatchlog after Repair.
Start a fresh agent session after Repair. The Hatchlog tools load at the start of a session, not in the middle of one.
Why are some token numbers blank?
Token cost is measured for Claude Code only. Work done by Cursor or Codex has no cost figure.