OAK — Your first review

This walks a change from an agent's edit to a reviewed decision. If you'd rather explore with data already in place, oak demo --fast produces a complete session — tasks, a subagent, a workflow, and pending edits — as an isolated demo-* session and an observatory-demo/ folder in the current directory; oak demo --clean removes both.

1. Let an agent work

With capture on, start a Claude Code session in your project and give it a task. Every file it changes is snapshotted as it goes — you don't have to do anything to record it.

2. Open the observatory

Launch the terminal app:

oak

The Observatory tab lists each machine's sessions by workspace. Pin one to read its conversation beside the list, with its workers and tasks; r opens the session's change map and edits on the Review tab. Or open the same record in VS Code / JetBrains — a file with pending edits carries a count badge in the editor's own file tree.

3. Read a change

Select an edit to see its diff in the agent's own colors, paired with the reasoning it recorded nearby (Observations). Revisions of the same lines are already collapsed into one review unit, so you read the net change, not every intermediate state.

4. Decide

Keep the ones you understand and want; Undo the ones you don't — each undo is conflict-guarded, so reverting one leaves the others standing. Resolving one edit moves you to the next still awaiting review. To act on a whole scope at once, Accept or Reject a file, a task, or the session.

💡

Try it on the demo

Run oak demo --fast, then oak, and practice the whole loop on the demo session before you point it at real work; oak demo --clean removes it afterwards.

Where to go next

To understand what you're looking at, read the OAK model. To review inside your editor, see VS Code or JetBrains. To record agents other than Claude Code, see Supported agents.