DocsScreens
Worklog
Worklog shows what the agent did for a commit, turn by turn and file by file, rebuilt from the agent's conversation.
Open Worklog
Click a commit in the Graph, then choose Worklog next to Commit in the panel that opens. The tab stays selected as you move between commits.
Summary
The large number is the time from the start of this commit's work to the commit. Below it are the range, such as First prompt 14:02 → commit 15:10, the number of instructions, and how many of the commit's files are traced to the conversation.
The TIME bar splits that span into Agent and Between turns, with ticks for the minutes when Other sessions were active. Click an agent part of the bar to open that turn. See Agent sessions and turns.
A line below counts builds, tool errors, subagents and decisions, and TOKENS shows output tokens. See Tokens.
How a commit meets its conversation
Worklog covers the time since the worktree's previous commit and reads the agent sessions in its terminals. The match is made by time, so the range carries a matched by time · inferred chip. See Recorded and inferred.
A row tagged Continued is an instruction given before that range whose work carried into it. A tag such as commit 2/5 marks the second of five commits made during that instruction.
Change by turn
Each row is one instruction, named by its time, oldest first. Its bar grows left for lines removed and right for lines added, and dashed pieces are files outside this commit. The counts are the agent's edits, so they can differ from the commit's. With many instructions, runs of small changes fold into one row.
Inside a turn
Click a row to see the instruction, the changed files, build and tool error counts, and the start of the agent's Report. Click a file to see its edits in that turn.
Conversation adds each Decision, with the answer you chose and the options you didn't, plus progress notes and the full report.
By file
By file draws each file as a bar, first line on the left. Places edited many times are hotter, and the positions are approximate. Click a spot to see which instruction added or removed each line there.
Uncommitted changes
Click Uncommitted changes at the top of the graph, then Worklog next to Changes. It covers the time since the worktree's last commit and refreshes as the conversation grows.
When Worklog is empty
When there's nothing to show, Worklog says why:
- No record for this commit: the commit was made before Whaatcher started recording.
- No record of this commit being made here: it may come from another clone or a worktree that no longer exists.
- No observed agent conversation in this window: the work may have been done by hand or by an agent outside Whaatcher.
- Made together with other commits: its conversation and tokens were counted on the commits made with it.
- The conversation is gone: the agent's transcript is no longer on disk.
Only sessions Whaatcher observes count. See Agent sessions and turns.