Agent OrchestratorYour AI coding agent can change. Your task should continue reliably. Agent Orchestrator has a shared local workbench for VS Code and a standalone desktop window. Import a Codex or Claude Code conversation, choose a model and effort, and save prompts as scheduled automations. Both interfaces read the same local conversation and automation records. The project also contains a headless coding-task engine that can hand an interrupted task to another agent with its externally verifiable state intact:
The next agent gets a structured, versioned handoff package that clearly separates verified facts from the previous model's claims. The orchestrator then checks that the work continued: workspace verified, tree matched, turn completed, regressions, and validation. It does not pretend two models share memory, does not touch your provider credentials, and never pushes or merges anything.
Requirements
Install, build, test
Open the shared workbenchVS Code. Open the project you want to edit and click the Agent Orchestrator icon in the Activity Bar. The Chat view opens in the sidebar and picks up the latest conversation for the current project. In a multi-folder workspace it follows the active editor. Explicit edit requests can apply reviewed changes to the trusted open project. The automation permission remains separate. To test an unpackaged extension, launch it with F5 and open your project in the Extension Development Host. For a packaged build, run Extensions: Install from VSIX... in your regular VS Code window and select the local package. Desktop. Run In Desktop, start a conversation by choosing a local project folder. Open Routing · Auto to set a mode for a conversation in either host.
Focused lookups start at low effort. Architecture and cross-component analysis start at high effort in all modes. An inspection can escalate once based on the Scout's findings. Edits add a Writer, an independent Reviewer and a Commentator. Agent activity shows the selected route and each role's provider, model, effort and status. The local project search resolves named files and looks up symbols with ripgrep or a bounded fallback. It supplies file paths and line numbers for definitions, imports and references. For broader work it also identifies likely entry points. Direct API agents can use the same read-only search tool. Set API requests per run to customize the cap from 1 to 30. It counts generation requests across all roles, including requests after tool calls. CLI connections have their own provider quotas. Enable Allow edits once per conversation to apply approved changes automatically. Writers work in an isolated copy. Workbench applies the reviewed patch with a private Git index only after checking that the source files still match the baseline. Existing staged changes stay in the user's index. Folders without Git use a private repository stored by Workbench. Blocked changes stay in the isolated folder shown in the conversation. In VS Code, save open project files before applying edits. If an editor has unsaved changes when the reviewed patch is ready, Workbench keeps the patch for later. Project checks. Save up to six commands for a conversation, one per line. Workbench runs the
approved commands with your computer account in the isolated copy after review. Each command has
a five-minute limit. A failed check or a change to the reviewed candidate blocks automatic apply.
For a project with a lockfile, you can include a dependency setup command such as Continue saved edit. After a stopped or blocked edit, reopen the conversation in either host and continue from its isolated copy. Workbench checks that the source still matches the starting state. If the patch had already been applied when the previous host stopped, Workbench verifies the applied tree and restores the reply. Keep copy and start over leaves the files on disk and clears the pending edit from the conversation. Both hosts use To create an automation, open a conversation, enter a prompt and click Automate. Choose an interval and save it. Run now starts one run. Enabling a schedule authorizes provider usage at that interval while a desktop window or VS Code workbench panel is open. An automation can apply edits only if its creation explicitly authorized edits for the same folder and conversation. The automation keeps the routing mode, API cap and authorized project checks it was created with. Run history records outcomes and the final role's route. Closing both hosts stops scheduling. If macOS blocks a project folder, use System Settings → Privacy & Security → Files and Folders to check access for the app that started Workbench. Agent activity shows the plan, public progress updates, and actions that Codex or Claude Code report during a turn. Completed replies retain a short activity history locally. Activity is excluded from the context sent to the next model. Two hosts share execution locks, so one scheduled occurrence starts once. When an earlier run has an ambiguous outcome after a host stops, its schedule is paused for review. Pausing an automation stops future runs. An active reply can be stopped from its conversation in the host running it. The workflow uses Codex's model catalog and Claude Code model aliases. VS Code model profiles from User Settings can override the default tiers. On a reported quota limit, another available writer can continue in the same isolated working copy. Other writer failures preserve it for inspection. The desktop is currently a development launcher, with its macOS window tested locally. ConnectionsOpen Connections → Add connection in either Workbench. A CLI account has a separate local profile. Run its displayed official sign-in command in Terminal, then click Check sign-in. Use named accounts to select the appropriate personal or work account for a conversation. Each conversation picks one primary connection per provider, and can disable either provider. Choose API key to add an OpenAI Platform or Anthropic API connection. Set it as a primary connection or select it as API fallback. Confirm Allow billed API use before saving the conversation's routes. The fallback is used when the selected primary providers are unavailable. Automations pin the chosen connections to their original project and require separate API consent. Connection names and routes are shared between Desktop and VS Code. API keys are stored separately in the host's secure storage, so enter a key in each host that should use it. Direct API calls send the key in the provider's authentication header. API stages can list and read regular project text files and write small text files in the isolated editing workspace. CLI connections provide the full agent toolset subject to their policy. Reproduce a handoff in 10 seconds (no quota, no network)
This creates a throwaway git repo and starts a task on a deterministic mock "Claude":
The output shows every state transition, the handoff (latency, continuity checks, package path), the validation result, and the reliability metrics. To inspect the result:
The full failure suite (auth rejection, crash mid-handoff, duplicate events, both providers limited, user changes, conflicting edits, failing validation, user cancellation, and more):
Last run: 95/95 scenario runs passed, 0 duplicate executions, 0 invariant violations, 15/15 crash recoveries consistent, handoff latency p50 ≈ 0.5 s. All of this is with mock providers; see docs/RELIABILITY_BENCHMARK.md. Run the extension
Try it without real providers. In your user settings set:
Then create a task in a repo shaped like the demo ( Inspect an existing local sessionIn the command palette, run Agent Orchestrator: Open Local Session… and choose a Codex or
Claude Code This opens a read-only view of the visible conversation in file order, without starting an agent or creating a handoff. Tool output, attachments, internal reasoning and other provider state are excluded. Recognized secret patterns are redacted. The preview keeps up to 200 text messages from one uncompressed file and shortens unusually long messages. The on-disk formats can change with provider updates; a preview does not rehydrate a provider's native session or transfer it elsewhere. From a terminal, Continue the conversationWith a local session open in a trusted project folder, run Agent Orchestrator: Send Message in Local Session…. Choose Codex, Claude Code, or Auto. Auto keeps the last provider (or the imported session's provider on the first turn) if it is signed in and available. Otherwise it selects an eligible provider, preferring your configured provider. Each send starts one read-only turn in the selected project folder. Auto difficulty looks at the latest message. A short summary or translation uses Quick
( Set
The Imported conversations and completed replies are saved atomically under the extension's
Each turn receives a bounded slice of visible history. Provider CLIs also manage their own run history. The current conversation mode gives agents read-only access to the selected folder. Connect real providersThe orchestrator uses the official CLIs exactly as you installed and logged in to them. It never reads, copies, or stores credentials.
Reproduce a real handoff. This uses your quota, on a throwaway repository you trust:
How it works (one paragraph)The task follows an explicit state machine (
A crash at any point is recovered on the next start: orphaned agent processes are reaped, the workspace is checkpointed, pre-start phases are retried, and in-flight target starts wait for you. Nothing ever runs twice. Details: ARCHITECTURE · HANDOFF_PROTOCOL · SECURITY · RELIABILITY_BENCHMARK · REFERENCE_ANALYSIS · LICENSE_AUDIT · IMPLEMENTATION_PLAN Safety defaults
Project layout
LicenseMIT. No code was copied from the reference projects; see docs/LICENSE_AUDIT.md. "Claude", "Claude Code", "Codex" and "OpenAI" are trademarks of their owners. This project is not affiliated with or endorsed by Anthropic or OpenAI. |