Frequently Asked Questions
IDE vs. IOE
Dispatch isn't just another editor; it's an Integrated Overview Environment (IOE). Here is how it differs from the traditional development workflow:
| Feature | Traditional IDE | Agentic IOE (Dispatch) |
|---|---|---|
| User Role | Individual Contributor (Typist) | Engineering Manager (Director) |
| Primary Unit | The File / The Line | The Goal / The Spec |
| Feedback Loop | Linter / Compiler | Verify Agent / Spec-DD |
| Visual State | Static Text | Living "Floor" / Streaming Reasoning |
| Success Metric | "It builds." | "It satisfies the Spec & Security Contract." |
General
What agents does Dispatch support?
Currently, Dispatch has first-class adapters for Claude Code, OpenAI Codex and Gemini CLI. It can also detect and orchestrate custom CLI-based agents via the Adapters settings.
Does my code leave my machine?
No. Dispatch is local-first. It orchestrates the CLIs already installed on your system. Your source code and agent transcripts are stored in a local SQLite database at ~/.dispatch/dispatch.db.
Can I still write code manually?
Absolutely. Dispatch is designed to augment your workflow, not replace your ability to intervene. You can jump into any file at any time. Dispatch will detect your manual changes and update the "Floor" state accordingly.
How is this different from Cursor or Windsurf?
Cursor and Windsurf are AI-native editors: they excel at helping you write code line-by-line. Dispatch is an Orchestration Layer. It doesn't want to be your only editor; it wants to be the cockpit where you direct multiple specialized agents (like Claude Code and Codex) through a formal pipeline with gated reviews.
What is "Spec-DD"?
Spec-Driven Development (Spec-DD) is the core workflow of Dispatch. Instead of asking an agent to "fix a bug," you ask it to "write a spec for this bug fix." Once you approve the spec, the agent implements it. This ensures the agent's "mental model" matches your expectations before a single line of code is changed.
What is the "Floor"?
The Floor is the visual heart of Dispatch. It's a live monitoring view where every active agent run is visualized as a swimlane. You can see what the agent is thinking, what tools it's calling and where it is in the pipeline (Spec, Implement, Verify, Review) in real-time.
Do I need all three agents installed?
No. Dispatch works with any combination of Claude Code, Gemini CLI and Codex. If you only have Claude installed, Dispatch will route all tasks to Claude automatically. The auto-model system detects which agents are available and selects the best one from what you have. You can always add more agents later from Settings.
What is Auto Model?
Auto Model is Dispatch's intelligent routing system. Instead of manually choosing which agent handles each task, Dispatch analyzes your intent and selects the best agent and model automatically. Research queries route to Gemini (native web search), code generation to Claude or Codex, security audits to Claude Opus. You can override this at any time by switching to Manual mode in the Mission bar.
What is a Mission?
Missions are quick, one-shot agent tasks. Ask a question, get an answer. Research a topic, audit code, generate a plan. Unlike Goals (which go through the full pipeline), Missions are ephemeral and fast. Results can be promoted to Goals or turned into step-by-step Plans for execution.
What are Plans?
Plans are structured step-by-step action items extracted from Mission results. When you run a Mission in Plan mode, the agent structures its response as numbered steps. Each step can be promoted to a Goal and auto-executed through the pipeline. Plans bridge the gap between quick questions and full project work.
Can Dispatch run agents on remote machines?
Yes. Dispatch supports remote agent execution via SSH. Add remote hosts in Settings, and Dispatch can discover and run agents installed on those machines. All communication is encrypted via SSH, and Dispatch uses your existing SSH keys (never stores private keys). Remote projects use the same worktree isolation model as local projects.
How does the Sandbox work?
The Sandbox provides project-level isolation for agent work. All modifications happen in a mirrored copy (git worktree) of your project. The real project is never directly modified. When work is complete, you review the changes and explicitly apply them. If something goes wrong, simply discard the sandbox.
Can I run multiple missions at once?
Yes. Dispatch supports multi-mission tabs. Each tab runs independently with its own adapter, mode and context. You can switch between active missions without interrupting them. The agent pool manages concurrency limits automatically.
How do I test my Dispatch integration?
Dispatch ships with a ReplayAdapter for deterministic testing. Record a real agent session to a JSON fixture file, then replay it in your test suite without hitting any LLM. This lets you test the full orchestration pipeline (DB writes, WebSocket events, output parsing) cheaply and reliably in CI.
What is the Elastic License?
Dispatch is source-available under the Elastic License v2 (ELv2). You can use, modify and self-host Dispatch freely. The only restriction is you cannot offer Dispatch as a managed service to third parties. This protects the project while keeping the source fully available.
Does Dispatch support Windows?
Not yet. Dispatch currently supports macOS (12+) and Linux (x86_64/ARM64). Windows support is on the roadmap.