Agents & fleet
Launch agents from profiles, watch every agent and sub-agent on one timeline, and plan work with the orchestrator.
Every project ADE opens is also set up with BMAD, the ADE methodology and Claude Code sub-agents for its roles and stack. See Project setup.
Agent picker
Press ⌘⇧A to pick an agent. When you choose one, ADE asks where to run it: this terminal (C) or a new tab in the same folder (N). If the current terminal is already running something, New tab is preselected.
A pane running any program, not only Claude Code, is never offered as this terminal, and closing it asks first. A tmux or screen pane always counts as busy, and so do the prompts of wrappers that stay in the foreground (sudo -s, poetry shell, xonsh).
- 47 profiles across Backend, Frontend, DevOps, Testing, Web3, Architects and General: API Builder, Database Engineer, Senior Go Engineer, Senior Rust Engineer, Smart Contract Auditor, Web3 DevOps Engineer, Debugger, Code Reviewer, Docs Writer and more. Each pairs a role: what it is accountable for, the files it owns and the boundaries it works inside, with a domain that narrows it to one technical focus. ADE composes the pair into a role definition, writes it to a file and starts the provider against that file, so a long definition never has to survive shell quoting. See Smart contracts for the Web3 engineers and Architects below.
- Roles: the last pill filters the list down to the core roles on their own, with no domain. Product Manager, Product Owner and Scrum Master live only here, since no profile pairs with them.
- Describe a task in the search box and the picker suggests the best match.
- Provider: switch between Claude Code, Codex, DeepSeek and Ollama with Tab. Claude Code, DeepSeek and Ollama each accept a composed role; Codex is shown unavailable, because it has no verified way to take one and a guessed flag would fail silently at launch. Set the one the picker starts on in Settings → AI API → Default agent provider.
- Senior Go Engineer writes idiomatic Go with table-driven tests and runs
go vetandgo test -race. Senior Rust Engineer models the domain with types, avoids strayunwraps and runscargo fmt,cargo clippyandcargo test. Both are also added to Go and Rust projects as sub-agents. - Continuous mode runs the agent without permission prompts (Claude Code’s
--dangerously-skip-permissions). ADE asks you to confirm first; use it only in projects you trust.

DeepSeek
DeepSeek publishes an Anthropic-compatible endpoint, so ADE’s DeepSeek provider is the claude CLI pointed at it rather than a separate tool. That is why it takes a composed role like Claude Code does: the mechanism is --append-system-prompt-file, the same verified flag.
Launching it runs:
ANTHROPIC_BASE_URL=https://api.deepseek.com/anthropic \
ANTHROPIC_AUTH_TOKEN="$DEEPSEEK_API_KEY" \
ANTHROPIC_MODEL=deepseek-v4-pro \
ANTHROPIC_DEFAULT_OPUS_MODEL=deepseek-v4-pro \
ANTHROPIC_DEFAULT_SONNET_MODEL=deepseek-v4-pro \
ANTHROPIC_DEFAULT_HAIKU_MODEL=deepseek-v4-pro \
CLAUDE_CODE_SUBAGENT_MODEL=deepseek-v4-pro \
CLAUDE_CODE_EFFORT_LEVEL=max \
claude --append-system-prompt-file <role>
The model identifier carries no context-window suffix. DeepSeek’s docs render it in bold, and the escape sequence reads as a trailing [1m] when the page is copied; pasted through, that is an identifier the API does not know.
- The key comes from the vault. Store
DEEPSEEK_API_KEYin Secrets and it reaches the terminal as an environment variable. The value never appears in the command, your shell history or the process list. - Cost is real. DeepSeek publishes list prices, so its spend is costed like Claude’s rather than left out. The figures are DeepSeek’s standard (peak) rate; off-peak is half, over 01:00–04:00 and 06:00–10:00 UTC on weekdays. Usage is aggregated per model with no timestamp, so ADE cannot tell which rate applied and uses the standard one. Your real bill may be up to half what ADE shows. See Tokens & cost.
- Every tier is redirected, which is what keeps the figure honest.
claudeasks for an opus, sonnet or haiku model by name depending on the task. Any tier left unmapped is still served by DeepSeek but recorded under its Claude name, and would then be priced at Anthropic’s rates. ADE maps all of them; if you configure a terminal by hand, map them all too.
Architects
The Architects category holds brainstorming partners for AI automation and Web3 design. They don’t write code unless you ask. Each one:
- asks up to five sharp questions about your goals, constraints, scale, budget and risk tolerance;
- proposes two or three genuinely different approaches and compares them in a table (complexity, cost, risk, time to ship, what breaks first);
- recommends one, draws it as a Mermaid diagram, and challenges your assumptions;
- records each agreed decision as an ADR in
docs/adr/NNNN-short-title.md. Click the path it prints to read the decision, diagram included, in the preview panel.

| Architect | Brainstorm about |
|---|---|
| AI Agent Architect | Whether you need an agent at all, single vs multi-agent, orchestration patterns, tools and MCP servers, memory, human-in-the-loop, guardrails, evals, cost and latency |
| RAG & Knowledge Architect | Ingestion, chunking, embeddings, hybrid search and reranking, permissions, freshness, measuring retrieval and answer quality |
| Workflow Automation Architect | Mapping the process, rules vs AI, n8n/Zapier vs Temporal vs your own queues, idempotency and retries, approvals, observability |
| LLMOps Architect | Model selection and routing, prompt versioning, evals, tracing, caching, fallbacks, cost budgets, PII and safety |
| AI Automation Strategist | Which processes to automate first, ROI and payback, build vs buy, pilots with success metrics, rollout and change management |
| DeFi Protocol Architect | Mechanism invariants, oracles, liquidations and bad debt, risk parameters, flash-loan and MEV attack surfaces, governance |
| Tokenomics Designer | Whether you need a token, utility and value accrual, supply, emissions and vesting, staking, governance capture, airdrop sybils |
| Smart Contract Systems Architect | Splitting contracts into modules, upgradeability (immutable, UUPS, transparent, diamond), roles, pausing, storage layout, audit readiness |
| Web3 Infrastructure Architect | Indexers and subgraphs, RPC redundancy and reorgs, account abstraction, key management, relayers and off-chain workers |
| Cross-chain & L2 Architect | Choosing chains and rollups, bridges and messaging protocols and their trust assumptions, finality, liquidity fragmentation |
| AI x Web3 Architect | Agents that hold wallets: smart accounts, session keys and spend limits, intents, agent payments, prompt-injection risk to funds, kill switches |
Describe the problem in the picker’s search box (“tokenomics for a governance token with vesting”, “RAG over our support docs”) and the matching architect is suggested.
Fleet view
Claude Code agents spawn sub-agents (Explore, Plan, code reviewers) that normally run out of sight. ADE reads Claude Code’s transcripts and shows each one as it starts and finishes.
- ⌘. opens the fleet panel for the active terminal. Switch to All terminals to see every terminal at once.
- Fleet: All terminals in the command palette opens the same view as a full tab.
- The timeline shows swimlanes. In the fleet tab you choose the last 5 minutes, 15 minutes, hour or all time; the panel always shows the last 15 minutes. Click an agent to jump to its pane.
- Each lane is filled in its role’s color: the color ADE writes into new agent files in
.claude/agents/, so a profile’s lane matches its profile file. Agent files written before this have nocolor:line yet. Sub-agents that are not ADE roles (Explore, Plan) are grey. A running lane has a pulsing end and a cancelled one is hatched; a lane’s tooltip, and its name for a screen reader, give its role and status.
Grouping
Across all terminals, the same lanes can be bucketed three ways. The data is identical in each; only the bucket changes.
| Group by | One group per | Useful for |
|---|---|---|
| Project (default) | folder the agents ran in | what a piece of work cost, when it spans several terminals |
| Role | role that ran them | which roles are busy, and where the spend goes |
| Terminal | terminal tab they started in | finding the window something is running in |
A project’s work outlives the terminal it started in, which is why Project is the default: closing a tab doesn’t scatter its history. Go to tab is offered only under Terminal, since that is the only grouping whose key is a tab.
- Seeing nothing? Agents are filed under the folder Claude Code was started in, so a terminal sitting somewhere else has none of its own; the empty timeline names the folder it is watching. Older runs need the tab’s all range; anything past 15 minutes is outside the panel’s window.
- Cost is real: Claude agents’ token usage comes from Claude Code’s transcripts and is priced at API list prices (see Tokens & cost). If two agents run in the same folder at the same time, their usage can’t be told apart and is left out. Codex and Ollama sessions show no cost.
- A group whose lanes carry no cost shows a dash, not
$0.00. A role that only ever runs as a sub-agent spends inside its parent’s session, and claiming it cost nothing would be a false statement about money.

Orchestrator
Press ⌘⇧O to open an Orchestrator tab and talk through a project (type in the scratchpad). It breaks the work into tasks, each with an agent profile, a priority and its dependencies.
- Dispatch one task, or Dispatch All ready tasks. Each runs in its own terminal with
claude, the task, and a generatedSPEC.md. - The orchestrator uses the Anthropic API, DeepSeek, or a local Ollama model — pick one in Settings → AI API. DeepSeek reuses the
DEEPSEEK_API_KEYin Secrets, so it needs no second key.
Stage board
BMAD-METHOD is installed as part of project setup. A project is on BMAD v6 by default: the bundled, pinned skills go into .claude/skills/, a small _bmad/ tree holds the config and ADE’s runtime, tickets and planning documents land in _bmad-output/, and ADE’s own verification gates live in .ade/gates/, one file per ticket, named by the ticket’s ref as the ticket tree prints it (for example 1.6a.yml). BMAD v4 is a choice made at setup for a new project, which puts the classic .bmad-core/ and its /BMad:tasks: slash commands for Claude Code in the project instead (v4 gates stay in docs/qa/gates/). A project that already has .bmad-core/ stays on v4 and is never converted. Nothing is downloaded and existing files are never overwritten. On v4, BMAD’s own ten personas are not installed: eight of them are the same jobs as the roles below, and a project carrying two architects and two QAs carries two definitions of Done. On v6, BMAD’s five persona skills (analyst, architect, developer, product manager and UX designer) arrive with the rest of its skills in .claude/skills/; the roles below are still the team.
The stage board (View: Toggle stage board, ⌘⇧Y ) is a panel beside your terminals for the project of the active pane. It refreshes as agents write files.
On a v6 project it is a map of BMAD v6’s four phases: Analysis, Planning, Implementation and Validation. v6 runs its skills in any order, so there is no current stage. Each phase lists the documents its skills wrote in the active initiative (brainstorms, briefs, PRDs, UX, architecture, specs and so on), each with the status its own file states, and “none yet” for a kind with none. Click a document to open it. Implementation holds the tickets, grouped by epic, and the quick-flow plans; Validation holds a count of QA gate results and each epic’s retrospective. Work done with no initiative active, and the backlog, are listed below the phases.
On a v4 project it shows where the project is in BMAD’s five stages, which plan documents exist, and every story, and you move the project’s stage with Next and Back. Next appears only once the current stage’s documents are on disk. A project that has never had its stage set follows its files until you click Track stage.
On both, a story or ticket that says it is done without a passing QA gate shows as claimed, and a waiver always shows its reason. You can Approve a draft and Dispatch an approved story, or a ticket in the active initiative, to a developer agent in a new tab. Backlog tickets are listed read-only; click one to open it.
The personas themselves are roles in the agent picker (filter to Roles and you have all nineteen) Analyst, Product Manager, Designer, Architect, Product Owner, Scrum Master, Developer, QA, DevOps, Adversarial Reviewer, Security Engineer, SRE, Release Manager, Engineering Manager, Support Engineer, Solutions Engineer, Brainstorming Architect, Technical Writer and Advisor, each with the accountability and owned files of its role. Launching one from there asks which provider to use and whether to run it in this terminal or a new tab, which the old persona buttons could not do. Product Owner and Scrum Master are reachable only this way, since no agent profile pairs with them.
Browser tab
Choose Open Browser Tab in the command palette to keep a local dev server (by default http://localhost:3000) open in ADE, next to the agent building it.