See what your agents are actually doing.
DASH is the desktop app that installs, runs and explains the agents you plan with OrchestrateMCP. It runs on your machine, holds the credentials your agents are not given, and shows you every step before it asks for an approval.
Status: in development, and there is no installer yet. The source is public and it builds and runs today — the release, signing and update path are not built.
Goal to running agent
Three steps, and DASH owns the last one
OrchestrateMCP decides what should be built. Your LLM builds it. DASH is where it runs, and where you find out what it did.
Plan it with MCP
Describe the goal in plain English. OrchestrateMCP returns a build brief and a manifest that names the permissions, the approval gates, and the steps it cannot vouch for.
Build it with your LLM
Your coding agent implements the brief in Claude Code, Cursor or ChatGPT. The manifest travels with it and stays the declaration of what the agent may reach.
Run it in DASH
DASH imports the manifest, starts the agent under its own runner, and shows every step, source, artifact and approval it produces.
The manifest is the join. MCP writes it, your agent ships with it, and DASH enforces what it declares — so the permissions you approved are the permissions that were planned. OrchestrateKit MCP
What DASH is
Boundaries, not adjectives
Each of these is a decision with a consequence somewhere else in the app. None of them is a setting you can turn off by accident.
DASH is not the runtime
A separate Agent Runner process owns execution, with its own database, audit trail and credential. It validates every command DASH sends it. DASH observes and requests; closing the window does not stop your agents.
Nothing listens on a port
The runner is reached over a Windows named pipe or a Unix socket. There is no address a process on another machine could dial, so the boundary is a fact about the transport rather than a rule someone has to follow.
Agents never hold your tokens
A permission broker keeps provider credentials on DASH's side and exposes typed, allowlisted operations instead. DASH builds the request and presents the token; the agent gets the answer and never the key.
Some operations simply do not exist
The Gmail capability can search, read a message, and save a draft. There is no send operation to call — not disabled, not gated, absent — so an agent that asks to send one is refused because the verb has no implementation.
Every run is inspectable
Inputs, steps, the sources a run read, the artifacts it produced, the gates it waited at and the verdict it earned. Grounding is judged separately from compliance, because a missing citation is not the same failure as an unapproved action.
It records its own absence
When DASH was closed, or a request never reached it, that is stored as a lapse with no decision attached rather than back-filled as an approval. An attempt nobody adjudicated is a different kind of fact from a decision DASH made.
Evidence
What has been proven, and what has not
The installed app runs an automated shell proof on every change. These are the numbers it reported on the current main branch — and the list beside them is what those numbers do not cover.
Proven on Windows
- Installed first run on Windows: import, consent, start, and a graceful stop
- A sample agent that reads live news and cites every item it reports
- Runner-hosted telemetry, stored artifacts, and a verdict on the run detail page
- The broker refusing both send attempts against a provider that would have served them
Not proven, and not claimed
- There is no installer. No signed build, no store listing, no auto-update.
- The Gmail boundary is proven against a loopback provider, not Google's API.
- Nobody has stood at a real Google consent screen yet. A runbook is not a run.
- macOS and Linux are unproven. The shell proof runs on Windows.
The O's
Every agent gets a face
Eleven characters share one body, so a fleet reads as a fleet at a glance. The costume is how you recognise an agent across cards, approvals and runs — it is never how DASH decides what that agent is allowed to do.
- ninja
- nerd
- cowboy
- wizard
- knight
- king
- chef
- viking
- medic
- explorer
- robot
There is no download yet
When there is a signed installer it will be linked here, and this sentence will be gone. Until then the honest way in is the repository: it builds, it runs, and the proof that it runs is in the same checkout.
git clone https://github.com/orchestratemcp/orchestratedash
cd orchestratedash
pnpm install
pnpm dev # the UI in a browser tab
pnpm shell # the same UI in the installable shellWindows is the proven platform. Node and pnpm are the only prerequisites.