Skip to content
OpenSpec Workbench

Local-first, no service to sign up for

See your OpenSpec changes. Run your agents from the same window.

OpenSpec Workbench runs and supervises coding agents on OpenSpec changes. It is a dashboard over Changes, Archive, Specs and Tasks, and a launcher for Claude, GitHub Copilot, Codex and Gemini CLI agents — with one command and event protocol behind all of them. It runs entirely on your machine, as a standalone web app or as a native VS Code extension, over the same shared core.

Get it on GitHub Read the source
  • VS Code Extension 0.71.0
  • Standalone App 1.34.1
  • Core 0.107.0

Current releases

Published 20 Sep 2026

VS Code Extension

Version 0.71.0
  • OpenSpec Workbench inside VS Code.
  • MINORgit decides a working directory is done, and the sweep removes it

Download vsix Changelog Docs

Standalone App

Version 1.34.1
  • Local web application, no editor required.

Changelog Docs

Core

Version 0.107.0
  • Execution engine shared by both delivery targets.
  • MINORgit decides a working directory is done, and the sweep removes it

Changelog Docs

Release history

4 – 21 Sep 2026
VS Code Extension
0.36.0 MINOR
0.39.0 6 releases MINOR
0.41.1 3 releases MINOR
0.43.0 2 releases MINOR
0.46.0 6 releases MINOR
0.47.0 2 releases MINOR
0.50.2 11 releases MINOR
0.50.8 6 releases PATCH
0.52.2 10 releases MINOR
0.56.0 4 releases MINOR
0.58.2 4 releases MINOR
0.59.4 5 releases MINOR
0.60.3 6 releases MINOR
0.63.0 7 releases MINOR
0.66.1 4 releases MINOR
0.71.0 8 releases MINOR
Standalone App
1.13.19
1.13.21 2 releases PATCH
1.13.23 2 releases PATCH
1.13.25 2 releases PATCH
1.16.0 6 releases MINOR
1.18.0 2 releases MINOR
1.20.7 10 releases MINOR
1.22.2 4 releases MINOR
1.23.7 10 releases MINOR
1.26.1 4 releases MINOR
1.26.4 3 releases PATCH
1.27.1 3 releases MINOR
1.28.4 5 releases MINOR
1.30.0 6 releases MINOR
1.32.0 3 releases MINOR
1.34.1 8 releases MINOR
Core
0.50.0 MINOR
0.52.0 2 releases MINOR
0.54.0 2 releases MINOR
0.56.0 2 releases MINOR
0.61.0 6 releases MINOR
0.63.0 2 releases MINOR
0.73.0 10 releases MINOR
0.76.1 4 releases MINOR
0.85.0 10 releases MINOR
0.87.0 2 releases MINOR
0.89.1 3 releases MINOR
0.90.1 2 releases MINOR
0.92.1 5 releases MINOR
0.98.0 6 releases MINOR
0.100.0 2 releases MINOR
0.107.0 8 releases MINOR

What it looks like

Standalone app

The Run a command panel: a completed show command with Claude CLI selected, its run analysis and streamed events
Commands stream their output as they run.
The change editor with a proposal's Markdown beside its rendered preview, and tabs for design, tasks and spec
Edit a proposal without leaving the dashboard.
A harness run in the change editor, paused at a checkpoint and asking whether to continue to verify with claude-cli
A harness run stops at a checkpoint and asks before the next step.
The pipeline view: each active change on a card under the step that can start it, one blocked waiting on another, and a hint with the command that gives a ready change somewhere to run
What can run now, what is blocked, and what to do about it.
A diff of a change's two edited files, the proposal rewritten and its tasks rewritten with one ticked
What changed in a change, line by line — the reason this exists.
The OpenSpec view summary listing one active change with one of three tasks done
One view over changes, specs and tasks.

VS Code extension

VS Code with the OpenSpec UI side bar showing Changes, Archive, Specs, Processes, Templates and Change Graph
A native tree view, not a webview pretending to be one.
A change open in the VS Code tree down to its proposal, design, tasks and spec, two tasks ticked and two still open
A change opens down to the task, done or still open.
The context menu of an archived change in VS Code, over its ticked tasks: unarchive, rollback, timeline, cost
An archived change keeps its tasks, and a menu of what to do with it.
The Pipeline open as a VS Code tab, two ready changes on cards with a Start button, and a hint with the command each one needs to run
The pipeline opens in a tab, beside the code it is about.
Harness settings for one change in a VS Code tab: a named configuration, and an agent chosen per stage for propose, review, apply and verify
Which agent runs which stage, set for one change or for all of them.
A spec opened from the Specs view in the VS Code editor
Specs open in the editor you already use.

Articles

All articles
The OpenSpec Workbench owl beside the words Run, Watch and Stop

Supervise the agents that build your OpenSpec changes

OpenSpec Workbench starts a coding agent on a change, shows what it is doing while it works, and lets you stop it where its work is sound. A tour of the Pipeline, the agents it drives and the limits it keeps.

The OpenSpec Workbench owl beside the words A viewer is not a cockpit

A viewer is not a cockpit

Showing an OpenSpec change is a solved problem. Supervising the agent that builds it is not. Three things that went wrong while building OpenSpec Workbench, and what a cockpit has to do about them.

Why it exists

Diffs between archived versions

openspec view shows you the current state. It does not show you what changed between two versions of an archived change. That gap is why this project started, and it is still the thing it does that nothing upstream does.

One protocol, four agents

Claude, GitHub Copilot, Codex and Gemini CLI agents — plus a local model behind an OpenAI-compatible API — are driven through a single command protocol (plan, implement, review, status, cancel) and a single event protocol. Swapping the agent does not change how you work.

Your machine, and nothing else

There is no account, no server to reach, and no telemetry. The standalone app binds to localhost behind a one-time token; the extension talks to the shared core directly. Normal use needs no internet connection at all.

Two products, one core

If you live in VS Code, the extension uses the native API — tree views, the diff editor, the built-in Git integration — rather than a webview imitating them. If you do not, the standalone web app is the same product in a browser. All the behaviour lives in one shared core; the hosts are thin adapters.

Questions

How is this different from openspec view?

openspec view is an interactive dashboard for specs and changes, and this project does not try to replace it. The three things it adds are diffs between versions of archived changes, launching CLI agents from the UI over a unified command and event protocol, and VS Code integration as a native extension rather than another window. Anything already covered upstream is deliberately not reimplemented here.

How do I install it?

The VS Code extension ships as a .vsix on the GitHub Releases page: download it, then use Install from VSIX… in the Extensions view. The standalone app is built from source — npm install, build the server workspace, and start it against the directory you want to inspect. It prints a localhost URL containing a one-time token; that exact URL is the only way in.

Does it send my code anywhere?

Not by itself. It reads your repository from disk and runs the CLI agents you have already installed, under your own credentials — so whatever those agents send is between you and them, on the same terms as running them in a terminal. The application has no backend of its own, collects no telemetry, and treats repository file contents as data rather than as instructions it may act on.