Mission control
for coding agents.
Keep agent CLIs, local tools, and long-running terminal sessions visible in one macOS workspace. Run one agent or many Teams at once; the practical limit is your Mac, repo, and accounts.
$ kadro team run auth-rewrite
architect: plan split across api, ui, tests
builder-03: editing src/auth/session.ts
reviewer: waiting for worktree diff
scout mapped auth surface
architect assigned builder-03
MCP call: reviewer -> builder
notebook appended handoff
Projects stay separated.
Agent sessions stay visible.
Your window stays still.
Keep each active project in a color-coded workspace. Inside it, split any mix of agent CLIs, local scripts, test runners, and shell sessions into the layout the task needs.
Claude Code
Opus 4.7 · Claude Max
OpenAI Codex
gpt-5.5 xhigh · YOLO mode
Gemini CLI
signed in with Google
shell
alexandru@macbook team-sandbox %
one workspace · multiple panes · one window
- split
- horizontal or vertical, no new window
- focus
- follows the click
- renderer
- xterm.js with WebGL
- tui-replace
- full-screen agent CLIs render clean
Dispatch a Team.
Keep every handoff visible.
When a change needs parallel work, Teams gives agents roles, separate git worktrees, and a shared notebook. Run multiple Teams across workspaces; scale is bounded by local resources and tool accounts, not a four-agent product limit.
architect → scout → builder → reviewer
- 01
architect
turns the mission into an execution plan
- 02
scout
maps files, risks, and candidate paths
- 03
builder
implements changes in an isolated worktree
- 04
reviewer
checks diffs before work reaches main
mission · feat/refactor-auth
00:00 → 00:42
Review the work while it is happening.
The mission dashboard makes parallel work readable: agent status, timeline events, work area, cross-agent invocations, and a composer for steering the next step.
Bring the CLI stack you already trust.
Kadro gives it structure.
If it runs in a terminal, it can live in a Kadro pane: coding agents, shell commands, test runners, scripts, and local developer tools. Built-in launchers make common agents quick to start; raw terminal panes cover everything else.
Plus your shell — zsh, bash, fish, or whatever's on your $PATH. No registry to wait for: a Kadro pane is a real PTY.
The surfaces ADE actually ships.
The page copy stays grounded in installable product surfaces: panes, terminal tools, Teams, worktrees, notebook state, and review.
- platform
- macOS — signed, notarized, auto-update
- runtime
- Tauri 2 · React 19 · Vite · xterm.js (WebGL)
- cli support
- any terminal tool · launcher shortcuts
- pane modes
- split · resize · focus · close · tui-replace
- palette
- ⌘K with > actions · @ panes · # workspaces
- agent scale
- unlimited across workspaces; hardware/account limited
- team roles
- architect · scout · builder · reviewer
- team setup
- role presets plus custom roster editing
- isolation
- one git worktree per agent
- shared state
- append-only NDJSON notebook
- interop
- MCP bridge for cross-agent invocations
- browser
- side panel webview · find · downloads · zoom
- file drop
- POSIX-escaped path injected into focused PTY
- settings
- appearance · shell · launchers · keybindings
- license
- $5 / month · 14-day trial · no card required
Before you add another agent.
Short answers for developers who already know agents are useful, and now need the work to stay organized, reviewable, and under control.
Stop scattering agent sessions.
Start coordinating the work.
Keep everyday agent sessions and terminal tools visible in one workspace. Dispatch one Team or many; ADE's ceiling is the machine underneath it.
Universal binary · macOS 12+ · ~11 MB