dvoid docs
WorkbenchGuides

Workstreams and harnesses

Group linked checkouts into a workstream, keep it current, and launch Claude Code, Codex, Hermes or pi in it.

dvoid-io/workbench · public

A workstream is one piece of work across one or more repos: linked checkouts under <estate>/workstreams/<project>/<name>/, all on one branch. The canonical clones they come from live under <estate>/repos/; you read those, and you work in the workstream.

dvoid workstream list lists your workstreams.

Start one

dvoid workstream new opens a wizard: pick the project, a name, the repos and your goals (in the console, Workstreams has the same create action). To script it, dvoid workstream new --help names the arguments. Creating a workstream does not open a terminal.

Its state

Each workstream keeps a state doc: its goal, the next cut, open items and what already failed. It is the workstream's record, and every agent session in it starts with it. dvoid workstream state render reads it and dvoid workstream state patch changes it. A workstream from before the state doc still has a .workstream/SEED.md; dvoid workstream state import carries it in once.

Keep it current

dvoid workstream update --check reads, without changing anything, how each repo's base has moved and its latest release tag on origin (dvoid release status; before cutting a release, dvoid release check with the tag, which never overwrites one).

dvoid workstream update makes each worktree rejoin its base, detached, and drops branches proven merged. It refuses uncommitted changes and work that has not landed, and it never merges a pull request for you.

dvoid workstream rm removes the worktrees, keeps the branches and archives the workstream's sidecar. --force discards uncommitted changes, never commits that nothing else reaches.

Launch a harness

Quick agents in the console launches a harness from the estate root. Under Workstreams, pick the project and workstream, then Open ▸ for its harnesses and openers.

From a terminal, dvoid claude, dvoid codex, dvoid hermes and dvoid pi launch from the estate root, and dvoid workstream claude, dvoid workstream codex, dvoid workstream hermes and dvoid workstream pi launch in a workstream. Each command's --help lists its configurations. When the harness exits you are back where you started.

Pi and the Hermes fleet profile run on the model fleet with your own key; Claude Code and Codex use their own vendor accounts. Some Hermes dashboard features need its gateway running.

A workstream holding a repo your org marks secret runs only dvoid workstream pi; the other harnesses are refused there. That is a launcher default and a block, not isolation.

Next

On this page