Local-first, no service to sign up for
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.
What did you come to do in Workbench? Where did you get stuck? Share feedback
harness.json. The approval shows the commit and destination and applies only to that push. An unattended CLI run stops before pushing when approval is required.harness.json. The approval shows the commit and destination and applies only to that push. An unattended CLI run stops before pushing when approval is required.harness.json. The approval shows the commit and destination and applies only to that push. An unattended CLI run stops before pushing when approval is required.
OpenSpec Workbench assigns a sandbox to each Codex stage and reads the result of the turn through the native CLI or ACP.
A run inside one of the repository's worktrees is given that worktree's own agents, whose sandbox is that worktree. Any other run gets the workspace's, whose sandbox still refuses a directory that is neither.
Agent workflow rules now say when to commit and push. A new change is committed and pushed as it is made. A card of a change's own worktree offers Commit Change, and the git stage commits what the stages left.
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.
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.
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.
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.
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.
Install OpenSpec Workbench from the
Visual Studio Marketplace
or find it in the VS Code Extensions view. For an offline installation,
download the .vsix from GitHub Releases
and choose Install from VSIX… in VS Code.
The standalone app is built from source. Run npm install, build the server
workspace, and start it against the directory you want to inspect. Open the
localhost URL with the one-time token printed by the server.
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.