Claude Agent Teams Ui
You're the CTO, agents are your team. They handle tasks themselves, message each other, review each other's code. You just look at the kanban board and drink coffee.
Ask AI about Claude Agent Teams Ui
Powered by Claude Β· Grounded in docs
I know everything about Claude Agent Teams Ui. Ask me about installation, configuration, usage, or troubleshooting.
0/500
Reviews
Documentation
Β
Β
Β
Β
Β
Β
Β
Β
Agent Teams
You're the CTO, agents are your team. They handle tasks themselves, message each other, review each other. You just look at the kanban board and drink coffee.
Β
Free desktop app for AI agent teams. Auto-detects Claude/Codex/OpenCode (75+ LLM providers). Use the provider access you already have - subscriptions or API keys. Not just coding agents.
|
https://github.com/user-attachments/assets/9cae73cd-7f42-46e5-a8fb-ad6d41737ff8 |
https://github.com/user-attachments/assets/35e27989-726d-4059-8662-bae610e46b42 |
Installation
No prerequisites - the app can detect supported runtimes/providers and guide setup from the UI.
If you want the FRESHEST version, clone the repo and run it from the dev branch.
|
May trigger SmartScreen β click "More info" β "Run anyway" |
Β
Β
|
Table of contents
- Installation
- Table of contents
- What is this
- Developer architecture docs
- Comparison
- Quick start
- FAQ
- Development
- Tech stack
- Roadmap
- Contributing
- Security
- License
What is this
An orchestration layer for AI agent teams across Claude and Codex.
- Claude + Codex orchestration β auto-detect available Claude/Codex runtimes and use the provider access you already have - subscriptions or API keys
- Assemble your team β create agent teams with different roles that work autonomously in parallel
- Agents talk to each other β they communicate, create and manage their own tasks, review, leave comments
- Cross-team communication β agents can fully communicate across different teams; you can configure or prompt them to collaborate and message each other between teams
- Sit back and watch β tasks change status on the kanban board while agents handle everything on their own
- Review changes like in Cursor β see what code each task changed, then approve, reject, or comment
- Built-in review workflow β easily see how agents review each other's tasks to make sure everything went exactly as planned
- Task-specific logs and messages β clearly see agent/runtime logs (tools), actions and messages in isolation for each individual task, making it easy to trace what happened for any assignment
- Live process section β see which agents are running processes and open URLs directly in the browser
- Stay in control β send a direct message to any agent, drop a comment on a task, or pick a quick action right on the kanban card whenever you want to clarify something or add new work
- Flexible autonomy β let agents run fully autonomous, or review and approve each action one by one (you'll get a notification) β configure the level of control that fits your security needs
- Solo mode β one-member team: a single agent that creates its own tasks and shows live progress. Saves tokens; can expand to a full team anytime
More features
-
Task creation with attachments β send a message to the team lead with any attached images. The lead will automatically create a fully described task and attach your files directly to the task for complete context.
-
Auto-resume after rate limits β when the lead hits a Claude rate limit and the reset time is known, the app can automatically nudge the lead to continue once the cooldown has passed
-
Deep session analysis β detailed breakdown of what happened in each agent session: bash commands, reasoning, subprocesses
-
Smart task-to-log/changes matching β automatically links session logs/changes to specific tasks
-
Advanced context monitoring system β comprehensive breakdown of what consumes tokens at every step: user messages, Claude.md instructions, tool outputs, thinking text, and team coordination. Token usage, percentage of context window, and session cost are displayed for each category, with detailed views by category or size.
-
Recent tasks across projects β browse the latest completed tasks from all your projects in one place
-
Zero-setup onboarding β built-in runtime detection and provider authentication
-
Built-in code editor β edit project files with Git support without leaving the app
-
Branch strategy β choose via prompt: single branch or git worktree per agent
-
Team member stats β global performance statistics per member
-
Attach code context β reference files or snippets in messages, like in Cursor. You can also mention tasks using
#task-id, or refer to another team with@team-namein your messages. -
Notification system β configurable alerts when tasks complete, agents need your response, new comments arrive, or errors occur
-
MCP integration β supports the built-in
mcp-server(see mcp-server folder) for integrating external tools and extensible agent plugins out of the box -
Post-compact context recovery β when the active runtime compacts its context, the app restores the key team-management instructions so kanban/task-board coordination stays consistent and important operational context is not lost
-
Task context is preserved β thanks to task descriptions, comments, and attachments, all essential information about each task remains available for ongoing work and future reference
-
Workflow history β see the full timeline of each task: when and how its status changed, which agents were involved, and every action that led to the current state
Developer architecture docs
For feature architecture and implementation guidance:
- Canonical standard - docs/FEATURE_ARCHITECTURE_STANDARD.md
- Repo working instructions - CLAUDE.md
- Feature root guidance - src/features/README.md
- Reference implementation -
src/features/recent-projects
Comparison
| Feature | Agent Teams | Gastown | Paperclip | Cursor | Claude Code CLI |
|---|---|---|---|---|---|
| Cross-team communication | β Native cross-team messages | β οΈ Cross-rig coordination | β οΈ Company-scoped org work | N/A | β |
| Agent-to-agent messaging | β Native real-time mailbox | β Mailboxes + handoffs | β οΈ Comments + @mentions | β | β Team mailbox, no UI |
| Linked tasks | β Cross-refs + dependencies | β οΈ Beads deps + convoys | β Goals, parents, blockers | β | β Shared task list |
| Session analysis | β Task logs + token tracking | β οΈ Session recall, feed, OTEL | β οΈ Run transcripts + cost audit | β | β οΈ Usage command, no UI |
| Task attachments | β Auto-attach, agents read & attach files | β Not task-level | β Docs, attachments, work products | β οΈ Chat session only | β οΈ Chat images only |
| Hunk-level review | β Accept / reject individual hunks | β | β Bring your own review | β | β |
| Built-in code editor | β With Git support | β | β Control plane, not editor | β Full IDE | β |
| Full autonomy | β Agents create, assign, review tasks end-to-end | β Mayor, convoys, recovery | β Heartbeats + governance | β οΈ Background agents, not teams | β Experimental CLI teams |
| Task dependencies (blocked by) | β Guaranteed ordering | β DAG waves via Beads | β Blockers + execution locks | β | β Team task deps, no UI |
| Review workflow | β Agents review each other + human review UI | β οΈ Refinery merge queue | β Approvals + governance | β οΈ PR/BugBot only | β Team review, no UI |
| Zero setup | β Guided runtime setup | β Go/Git/Dolt/Beads/tmux | β οΈ npx + embedded Postgres | β | β οΈ CLI + env flag |
| Kanban board | β 5 columns, real-time | β Dashboard, not Kanban | β 7 columns, drag-and-drop | β | β |
| Execution log viewer | β Tool calls, reasoning, timeline | β οΈ Feed, OTEL, dashboard | β Run transcripts + ledger | β οΈ Agent chat + terminal | β |
| Live processes | β View, stop, open URLs in browser | β οΈ Agent health dashboard | β οΈ Manual services + previews | β οΈ Native terminal only | β |
| Per-task code review | β Accept / reject / comment | β οΈ Merge queue, no diff UI | β οΈ PR/work products, no inline diff | β BugBot on PRs | β |
| Flexible autonomy | β Per-action approvals + notifications | β Gates, escalation, recovery | β Board approvals, pause, terminate | β οΈ BG agents auto-run commands | β Permissions + hooks |
| Git worktree isolation | β Optional | β Core primitive | β Worktrees / branches | β οΈ Background branches/VMs | β οΈ Manual worktrees |
| Multi-agent backend | β Claude, Codex + OpenCode teammates | β Claude, Codex, Gemini, Copilot + more | β BYO agents: Claude, Codex, Cursor/OpenCode, HTTP | β οΈ Multi-model agents, no team backend | β οΈ Claude-only experimental teams |
| Org chart / governance | β οΈ Roles + approvals, no org chart | β οΈ Roles + escalation | β Org chart + board governance | β οΈ Team admin only | β |
| Budget controls | β οΈ Cost/token visibility, no hard caps | β οΈ Cost tiers + digest, no hard caps | β Per-agent budgets + hard stops | β οΈ Usage + BG spend limits | β οΈ /cost + workspace limits |
| Price | Free OSS UI, provider access needed | Free OSS, runtime plans needed | Free OSS, self-hosted + infra | Free + paid usage | Claude plan or API usage |
Fact sources checked on May 5, 2026: detailed research notes, Gastown README, Gastown provider guide, Gastown scheduler, Paperclip README, Paperclip adapters, Paperclip budgets, Paperclip runtime services, Paperclip Kanban source, Cursor Background Agents, Cursor Diffs & Review, Cursor Bugbot, Cursor pricing, Claude Code agent teams, Claude Code subagents, Claude Code workflows, Claude Code costs, Claude pricing.
Quick start
- Download the app for your platform (see Installation)
- Launch β On first run, the setup wizard will detect the runtime and guide provider authentication
- Create a team β Pick a project, define roles, write a provisioning prompt
- Watch β Agents spawn, create tasks, and work. You see it all on the kanban board
FAQ
Do I need to install a runtime before using this app?
No. The app guides runtime detection/setup and provider authentication from the UI - just launch and follow the setup wizard.
Does it read or upload my code?
The app is not a cloud code-sync service. It reads local runtime/session data to power the UI, and your project stays on your machine unless you choose a provider/runtime path that sends data to that provider. In `multimodel` mode, startup may also perform runtime access and capability checks before launch.
Can agents communicate with each other?
Yes. Agents send direct messages, create shared tasks, and leave comments - all coordinated by the app's own orchestration layer.
Is it free?
Yes, free and open source. The app has no paid tier of its own. To run agents, you only need access to a supported provider/runtime, such as Anthropic or Codex.
Can I review code changes before they're applied?
Yes. Every task shows a full diff view where you can accept, reject, or comment on individual code hunks β similar to Cursor's review flow.
What happens if an agent gets stuck?
Send a direct message to course-correct, or stop and restart from the process dashboard. If an agent needs your input, you'll get a notification and the task will show a distinct badge on the board.
Does it support multiple projects and teams?
Yes. Run multiple teams in one project or across different projects, even simultaneously. To avoid Git conflicts, ask agents to use git worktree in your provisioning prompt.
Development
Tech stack
Electron 40, React 19, TypeScript 5, Tailwind CSS 3, Zustand 4. Data from ~/.claude/ (session logs, todos, tasks). The desktop app works with local runtime/session state, while some runtime modes may also use provider or startup capability services when required.
Build from source
Prerequisites: Node.js 20+, pnpm 10+
git clone https://github.com/777genius/claude_agent_teams_ui.git
cd claude_agent_teams_ui
pnpm install
pnpm dev
The app auto-discovers Claude Code projects from ~/.claude/.
Build for distribution
pnpm dist:mac:arm64 # macOS Apple Silicon (.dmg)
pnpm dist:mac:x64 # macOS Intel (.dmg)
pnpm dist:win # Windows (.exe)
pnpm dist:linux # Linux (AppImage/.deb/.rpm/.pacman)
pnpm dist # macOS + Windows + Linux
Scripts
| Command | Description |
|---|---|
pnpm dev | Development with hot reload |
pnpm build | Production build |
pnpm typecheck | TypeScript type checking |
pnpm lint | Lint (no auto-fix) |
pnpm lint:fix | Lint and auto-fix |
pnpm format | Format code with Prettier |
pnpm test | Run all tests |
pnpm test:watch | Watch mode |
pnpm test:coverage | Coverage report |
pnpm test:coverage:critical | Critical path coverage |
pnpm check | Full quality gate (types + lint + test + build) |
pnpm fix | Lint fix + format |
pnpm quality | Full check + format check + knip |
Roadmap
- Planning mode to organize agent plans before execution
- Visual workflow editor (@xyflow/react) for building and orchestrating agent pipelines with drag & drop
- Remote agent execution via SSH: launch and manage agent teams on remote machines over SSH (stream-json protocol over SSH channel, SFTP-based file monitoring for tasks/inboxes/config)
- CLI runtime: Run not only on a local PC but in any headless/console environment (web UI), e.g. VPS, remote server, etc.
- 2 modes: current (agent teams), and a new mode: regular subagents (no communication between them)
- Curate what context each agent sees (files, docs, MCP servers, skills)
- Slash commands
- Outgoing message queue β queue user messages while the lead (or agent) is busy; clear agent-busy status in the UI; flush to stdin or relay from inbox when idle (durable queue on disk for the lead inbox path)
-
createTasksBatchβ IPC/service API to create many team tasks in one call (playbooks, markdown checklist import, scripts); complements singlecreateTask - Command palette β extend Cmd/Ctrl+K beyond project/session search to runnable actions (quick commands, navigation shortcuts, team/task operations) in a keyboard-first flow
- Custom kanban columns
- Run terminal commands
- Monitor agents processes/stats
- Reusable agents with SOUL.md
- Π‘ommunicate via messenger
- SDK to programmatically launch agents
Contributing
See CONTRIBUTING.md for development guidelines. Please read our Code of Conduct.
Security
IPC and standalone HTTP handlers validate IDs, paths, and payload shape at the boundary. Project editing and write operations are constrained to the selected project root, while read-only discovery also accesses local Claude data under ~/.claude/ and app-owned state paths when required. Path traversal and sensitive config/credential targets are blocked. See SECURITY.md for details.