Editor extensions

OAK ships two editor extensions — the VS Code extension and the JetBrains plugin (IntelliJ, PyCharm, WebStorm, and the rest). Both are thin renderers over the CLI, so every number matches the terminal app — one record, rendered in whichever editor you live in. The demo below is the same self-playing session as the homepage — an agent editing a Python pipeline while the observatory fills in around it; pause or step through it with the controls.

The Observatory Traces sidebar, inline review, and the Dashboards dock — all live, filling in as the agent works.

What's inside

• The Overview panel — the master-detail board: Sessions, Workers, Workflows, Tasks, and Processes, with the change map scoped by selection.
• The Traces sidebar — every captured edit in the project tree, grouped by file, with per-row Keep and Undo.
• Inline review — pending edits in the editor itself, and the review bar that carries the verbs.
• The stacked diff view — Open all in editor reads the pending work as one scroll, each diff with its own Keep and Undo.
• The Timeline panel — Feed, Prompts, Observations and Actions in one panel.

Two editors, one setting

Which review surface appears is a setting, spelled the same way where the editors overlap. JetBrains IDEs expose a floating-toolbar layer, so the review controls sit as a floating toolbar over the editor. VS Code exposes no floating-widget API, so it uses a compact bar built on a comment thread, plus a review bubble one click away. A file with pending edits carries a count badge in the editor's own project tree — and on the editor tab in VS Code.