Kadro
01docs

Kadro ADE documentation

Install Kadro ADE, run Claude Code, Codex, Gemini, and shell sessions in splittable terminal panes, then coordinate multi-agent Teams across isolated git worktrees with shared mission state.

02Start here

Documentation for a macOS coding agent workspace.

Kadro ADE is built for developers who want agent CLIs, local scripts, test runners, web references, and multi-agent review loops in one place. These docs cover the actual product surface in the ADE source today: workspaces, panes, providers, Teams, the command palette, browser sidebar, release flow, and roadmap.

docs / start

Install Kadro ADE on macOS

Download the signed macOS build, drag Kadro.app into Applications, and let the Tauri updater handle future releases on launch and hourly while running.

Start
docs / workspaces

Create an agent workspace

Use layout blueprints or a custom grid, mix Claude, Codex, Gemini, and terminal panes, and keep up to 16 sessions visible in one workspace.

Learn
docs / teams

Coordinate multi-agent Teams

Assemble architect, builder, reviewer, and scout roles across isolated git worktrees, a durable NDJSON notebook, and the Kadro MCP bridge.

Explore
docs / review

Review work before it drifts

Use the mission dashboard, timeline, per-agent PTY attach, read-only worktree diffs, and operator controls for nudge, reset, stop, and restart.

Review
docs / control

Move fast with Cmd+K

Find actions, panes, and workspaces from one command palette. Prefix with > for actions, @ for panes, and # for workspaces.

Shortcuts
docs / releases

Track what changed

Read public release notes, current source-stream notes, and roadmap items without treating in-development work as shipped.

Changelog
03Install

Get Kadro ADE running on macOS.

Kadro ADE ships as a macOS desktop app. The documented install flow is intentionally normal: download the DMG, move the app to Applications, launch it locally, and let the updater handle the rest.

Download for macOS
  1. 1Download the latest Kadro macOS DMG from the release channel or the website download route.
  2. 2Open the DMG, drag Kadro.app into Applications, and launch it from Applications or Spotlight.
  3. 3Install the agent CLIs you plan to use: Claude Code, Codex CLI, or Gemini CLI. Raw shell panes work with any local command on your PATH.
  4. 4Open Settings to confirm provider status. Kadro checks binary presence, version output, and known auth state for supported providers.
  5. 5Keep Kadro running normally. Updates are checked on launch and once an hour; when one is available, use Install & restart from the update banner.
04Workspaces

Run agent CLIs and terminal work without losing sight of them.

A Kadro workspace is a visible operating surface for local development. Create a workspace from a blueprint or custom layout, choose a project directory, mix agent and terminal sessions, and keep the work in front of you instead of buried in separate terminal windows.

  • Single-window navigation with color-coded workspace tabs.
  • Blueprint or custom workspace creation with 1 to 16 panes.
  • Horizontal and vertical splits, directional focus, fullscreen pane mode, duplicate, rename, close, copy cwd, reveal cwd in Finder, and clear scrollback actions.
  • xterm.js with WebGL rendering plus fit, search, unicode11, and web-links behavior.
  • tui-replace rendering for full-screen agent CLIs so alternate-screen tools remain usable.
  • Drag-and-drop file paths into a focused PTY as shell-escaped prompt-ready tokens.
ProviderIDSetup and behavior

Claude Code

npm i -g @anthropic-ai/claude-code

claude

Creatable agent pane with provider status, version probe, auth detection, and a shell fallback when the CLI exits.

Codex CLI

npm i -g @openai/codex

codex

Creatable agent pane for OpenAI Codex workflows, with PATH detection and Codex auth checks in Settings.

Gemini CLI

npm i -g @google/gemini-cli

gemini

Creatable agent pane for Gemini sessions, launched through your default shell with tui-replace rendering.

Shell

Use your default shell

shell

Internal raw terminal provider for local commands, test runners, dev servers, scripts, and repo maintenance.

05Teams

Coordinate multi-agent coding Teams across git worktrees.

Teams give parallel agent work a structure. The wizard asks for a mission brief, team name, repository, provider/model defaults, and a roster. Kadro then gives each agent a role and worktree so implementation, review, and investigation can happen in parallel without sharing one mutable checkout.

Read the worktrees article

Quick Build: 3 agents, with one architect directing two builders.

Strike Team: 5 agents, adding scout and reviewer coverage.

Task Force: 7 agents, with dual architect oversight and a larger build lane.

War Room: 11 agents, built for heavier parallel implementation and review gates.

Hive Mind: 17 agents, with four architects, eight builders, two scouts, and three reviewers.

Teams currently use Claude and Codex in the creation wizard.
Each agent receives a role, model/provider defaults, a mission brief, and an isolated git worktree.
The backend creates worktrees under Kadro-managed repo paths, ensures the worktree directory is ignored, and can summarize commits and changed files against the base branch.
The shared notebook is append-only NDJSON at the team worktree root, giving the dashboard durable mission, decision, finding, lifecycle, and handoff events.
The MCP bridge exposes team orchestration tools including ListTeam, InvokeAgent, WaitForAssignment, MissionComplete, AppendNote, ReadNotebook, WaitForSignal, and queue-task operations.
06Review

Keep the mission reviewable while agents are working.

The Team dashboard is not just a launch screen. It is the cockpit for live and completed missions: agent roster, timeline, current work, Talk, per-agent terminals, and worktree diffs all sit close enough for the operator to intervene before the final merge.

Agent cards show role, provider, status, and worktree information.
Mission timeline and notebook views preserve decisions, findings, lifecycle events, and handoffs.
Worktree diffs are read-only against the base branch using git log and numstat data.
Operator controls include stop, delete, nudge, reset, restart, and per-agent PTY attach.
07Control plane

One command catalog for actions, panes, workspaces, and shortcuts.

Command palette

Cmd+K searches commands, active-workspace panes, and workspaces with fuzzy scoring. Use >, @, and # prefixes when you already know the type of target.

Keybindings

The command catalog resolves default shortcuts and user overrides. On macOS, mod maps to Cmd; on other platforms, it maps to Ctrl.

Settings

Appearance, shell, providers, and keybindings live in one Settings surface. Provider rows show missing CLIs, install commands, versions, and auth state where available.

Browser sidebar

The workspace browser sidebar supports toggle, reload, hard refresh, zoom, find-in-page, download tracking, and new-window request handling.

08Roadmap

Shipped, in development, and planned.

This roadmap is based on the current ADE codebase and planning notes. Shipped means represented in the source today. In development and planned items should stay off release copy until they are versioned in the changelog.

Shipped· source
  • Native macOS desktop app built with Tauri, React, Vite, TypeScript, and xterm.js.
  • Signed macOS release flow with updater artifacts and optional Developer ID notarization gates.
  • Workspace launcher with blueprints, custom grids, project directory selection, session mix, and 1-16 pane support.
  • Provider registry for Claude, Codex, Gemini, and Shell with install hints, docs links, version probes, and auth checks.
  • Command palette with action, pane, and workspace prefix modes.
  • Advanced pane management: split, duplicate, fullscreen, rename, swap or move by drag, copy cwd, reveal cwd, clear scrollback, and close.
  • Browser sidebar with native webview events, find, zoom, downloads, reload, hard refresh, and new-window handling.
  • Teams: formation presets, four built-in roles, per-agent git worktrees, shared NDJSON notebook, MCP bridge, queue-task protocol, operator controls, PTY attach, and read-only diffs.
In development· active
  • Auto-extracted pane labels from the first prompt sent to an agent, with cwd basename as fallback.
  • Wheel-passthrough for tui-replace panes so scroll reaches the underlying TUI.
  • Pane header menu actions kept in sync with commands, shortcuts, and the palette.
  • Per-workspace partitioned persistence with versioned migrations.
  • Orphan PTY reaper at boot and tighter PTY ownership cleanup.
Planned
  • Kadro Marketer as a separate app, currently scoped toward an X Post Studio workflow.
  • Custom non-built-in team roles.
  • Cross-window pane transfer infrastructure without committed UI.
09FAQ
What is Kadro ADE?

Kadro ADE is a native macOS agentic development environment for running terminal tools and AI coding agents in visible, splittable workspaces.

Which agent CLIs does Kadro ADE support?

The current provider registry supports Claude Code, Codex CLI, Gemini CLI, and raw shell panes. Settings can detect installed binaries, versions, and known auth state for supported providers.

How do Kadro Teams isolate agent work?

A Team assigns agents to roles, gives each agent its own git worktree, writes durable mission state to an append-only NDJSON notebook, and coordinates agent-to-agent work through the Kadro MCP bridge.

Does Kadro ADE replace my terminal?

No. Kadro ADE wraps real PTYs. Raw shell panes remain available for normal terminal work, while agent panes launch supported CLIs through your shell.

Build with Kadro ADE.

Install the macOS app, create your first agent workspace, and keep every session visible.

Download for macOSRead changelog →