The review tab

The review tab carries the same review the editors do, in the terminal: each edit's diff in the agent's own colors, with the decision verbs one key away.

Per-edit diffs

Every edit opens as its own diff — the tool that made it, the before and after, and its churn — never one session-wide diff to untangle. Revisions of the same lines are already collapsed into one review unit, so you read the net change.

The verbs

The same two verb pairs as everywhere else, on the keyboard: Keep and Undo act on one review unit; Accept and Reject act on a scope — a file, a task, a prompt, or the whole session.

The change map acts too. A pending row carries [ ✓ ] keep and [ ✗ ] undo buttons and a reverted row [ ↺ ] redo, and the heading carries keep-all, undo-all and resolve; each asks its question on the same row. Map and Diff are separate panes, on F4 and F5, and F folds or unfolds every file in Traces.

Sessions on another machine

A session that runs on a saved machine is reviewed on that machine. The tab reads its review there and runs every decision there — Keep, Undo, Redo, Resolve, diffs and review comments — over SSH with that machine's own oak, because the edit store and the files never leave it. No store, transcript or working file is copied between machines, and the session header names the machine (on build-box).

The session picker (b) lists this machine's sessions first, then each saved machine's, under that machine's name; the find palette offers them too. They come from each machine's own session list, which OAK reads in the background and refreshes about every fifteen seconds. A machine that has not answered yet, or cannot be reached, is one line in the picker that says so. The session under the Observatory’s cursor, previewed or pinned, is the one this tab shows, as is a session opened with r. Started outside any repo with no --session or --root, this tab opens on the session that most recently took a turn on any machine, this one or a saved one (on a machine running this version, reopening a session, as herdr does when it restores its panes, is not a turn), as the machines first answer and until you choose a session or act in the tab. oak --tab review --session <id>, with or without --once, reviews a session this machine does not hold on the saved machine that lists it; when none does, --once fails and the panes say so, naming the machines asked. While the owning machine does not answer, the panes name the failure instead of showing an empty review; a sync mirror of the session on this machine is never read in its place. Scripts reach the same machine with --machine <label> (see the CLI reference).

Automatic remote refreshes wait at least ten seconds, or twice the last read's duration when longer. Decisions bypass this delay for their next read. An older remote CLI that cannot expand review units produces an update-required error before acting. Remote status facts remain separate from the local session catalog. Observatory also reads its conversation, metadata and edit previews on the owning machine.