agent-teams-ai

Boss, watch the video

Check also:

• universal-agent-plugins - Multi-agent CLI to install, update, repair, and remove Agent Plugins 1.0 and Agent Skills across Codex/ChatGPT, Claude, Cursor, Gemini, Copilot, Qoder, Pi, OpenCode, and more. 1,500+ plugins. SDK for universal plugins (hooks, detect, install/manage)
• review-router-ai - Free, open source CodeRabbit. Powerfull AI code review that runs inside your CI/CD (privacy) using your Claude/Codex/other subscription accounts (pool)/API. Free/self-hosted deployment. Ready github integration. Built using OpenCodeReview. Claude/Codex/OpenRouter/Grok/Kimi/Glm/MiniMax/MiMo...
• agent-notifications - 🔔 Cross-platform smart notifications for Claude/Codex/OpenCode/Cursor/Gemini/Qoder/Pi. Desktop alerts, sounds, click-to-focus, and webhooks. macOS, Linux, and Windows.

Screenshots (watch on our site):

Installation

No prerequisites - the app can detect installed Claude Code, Codex, and OpenCode runtimes. You can also connect Cursor, SuperGrok, GitHub Copilot, Z.AI, MiniMax, and Kiro from the UI.

Table of contents

• Installation
• Table of contents
• What is this
• Comparison
• Quick start
• FAQ
• Roadmap (new)
• Vision
• Development
• Tech stack
  • Terminal Platform integration
  • Debug teammate runtimes
  • Build for distribution
  • Scripts
• Contributing
• Partnerships
• Security
• License

❤️ Sponsors

What is this

An orchestration layer for AI agent teams across Codex/Claude/OpenCode/Cursor/Grok/GitHub/Kiro/Z.AI/Xiaomi/MiniMax/Kimi...(300+ models, 200+ LLM providers, free models no auth)

• Assemble your team — create agent teams (using 1 prompt) with different roles that work autonomously in parallel
• Sit back and watch — tasks change status on the kanban board while agents handle everything on their own
• 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
• Built-in review workflow — easily see how agents review each other's tasks to make sure everything went exactly as planned
• Token analytics and budgets — see input, output, cache, and reasoning usage across teams, agents, tasks, projects, models, runtimes, sessions, commands, and runs. Spot expensive work, track trends and forecasts, set monthly token or estimated-cost budgets, and get alerts at 80% and 100%
• Organizations and global overview — group teams into departments, squads, or any nested structure. Track every organization on one live map with team and agent status, task progress, dependencies, delegation, and cross-team communication
• Stay in control — send a direct message to any agent (DM or group chat), 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 supported tool actions one by one (you'll get a notification) — configure the level of control that fits your security needs
• 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
• Integrated terminal workspace — run commands in a visual PTY scoped to each team and project, with local shell tabs, persistent history, autocomplete, and terminal settings
• 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
• Multi-provider orchestration — start with a free model with no auth, auto-detect available Claude Code, Codex, and OpenCode runtimes, or connect Cursor, SuperGrok, GitHub Copilot, Z.AI, MiniMax, Kiro and more, using the subscriptions or API keys you already have
• Review changes like in Cursor — see what code each task changed, then approve, reject, or comment

• Live process section — see registered background services, stop them, and open their URLs directly in the browser

• Per-agent CPU/RAM history — see how many local resources each live teammate uses over time

• 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 each agent session: agent output, tool calls, bash commands, and subprocesses

• Smart task-to-log/changes matching — automatically links session logs/changes to specific tasks

• Advanced context monitoring system — see what consumes context: user messages, project instructions, tool outputs, available thinking summaries, and team coordination. View token usage, context-window share, and estimated cost by category.

• Recent tasks across projects — browse the latest completed tasks from all your projects in one place

• Zero-setup onboarding — start with the free model with no auth, then connect paid/account providers only when you need them

• 29 interface languages - choose the app language and preferred agent communication language. Includes English, Chinese, Spanish, Hindi, Portuguese, French, Arabic, German, Japanese, Korean, Russian, Ukrainian, and 17 more.

• Built-in code editor — edit project files with Git support without leaving the app

• Branch strategy - choose per teammate at launch: use the main checkout or run selected agents in their own git worktree. You can still spell out branch rules in the provisioning prompt.

• 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-name in 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

Comparison

Feature	Agent Teams	Gas Town	Paperclip	Cursor	Claude Code CLI	OpenRig
Supported desktop platforms	macOS · Windows · Linux (native desktop app)	macOS · Windows · Linux (CLI binaries)	No native desktop app (self-hosted control plane)	macOS · Windows · Linux (desktop IDE)	macOS · Windows · Linux (CLI)	macOS · Linux; Windows via WSL2 (not native)
Live team collaboration	✅ █████████░ 9/10 · Agents plan, delegate, work, and review together	✅ ████████░░ 8/10 · Persistent teams with coordination and recovery	⚠️ ███████░░░ 7/10 · Scheduled agents + MCP task collaboration, less live peer teamwork	⚠️ ██████░░░░ 6/10 · Parallel agents + subagents, no peer team	⚠️ ███████░░░ 7/10 · Experimental teams + cross-session messaging; recovery limits	✅ ████████░░ 8/10 · Persistent roles, delegation, owned-work queues, and review handoffs
Human control and approvals	✅ Per-action approvals, roles, and notifications	✅ Gates, roles, escalation, recovery	✅ Board approvals, roles, pause, stop	⚠️ Command controls and admin policies	✅ Permissions + hooks	✅ Runner permission requests, audited policies, typing guard, and stop controls
Visual team progress	✅ Teammates, tasks, blockers, handoffs, activity, logs	⚠️ Agent tree + feed panels	⚠️ Org chart and run status, not a task/log map	⚠️ Agents Window, no shared peer-team map	⚠️ Terminal team panel, no graphical UI	✅ TUI topology graph, seat state, missions, and activity feed
Team workspace	✅ Tasks, code, terminal, review, and teammates in one app	⚠️ Mail/feed/dashboard across tools	⚠️ Board + task chats, less live teammate view	⚠️ Agents Window, no peer team workspace	❌ No desktop UI	⚠️ TUI, tmux, task-following terminal views; optional maintenance web UI
Easy setup	✅ Start free, no signup or API key	❌ Manual CLI stack	⚠️ npx onboarding + browser app	⚠️ App install + account	⚠️ CLI + env flag	⚠️ Node + tmux + provider login; guided setup on macOS/Linux
Agent readiness and recovery	✅ Clear ready/stuck status with launch diagnostics	✅ Working/stalled/failed health with recovery controls	⚠️ Run status and orphan recovery	⚠️ Agent status in Agents Window	⚠️ Statuses in terminal, no graphical UI	✅ Readiness checks, snapshots, and explicit per-seat restore outcomes
Kanban board	✅ 5 columns, real-time	❌ Dashboard, not Kanban	✅ 7 columns, drag-and-drop	❌	❌	❌ Owned-work queue and mission views; no Kanban board
Code review	✅ Agent review plus accept, reject, and comment in the app	⚠️ Merge queue, no diff UI	⚠️ Review gates + experimental GitHub review bot; no in-app hunk review	✅ Local Agent Review + PR Bugbot	⚠️ Agent review, no review UI	⚠️ Reviewer rigs and proof approvals; no task-level hunk review UI
Cross-team communication	✅ Direct agent messages and shared task links across teams	⚠️ Mailboxes + handoffs	⚠️ Comments + @mentions	N/A	⚠️ Cross-session messaging, no shared cross-team task graph	✅ Cross-rig messages, broadcasts, chatrooms, and queue handoffs
Linked tasks	✅ Tasks can link to and block each other	✅ Task deps + grouped work	✅ Goals, parent tasks, blockers	❌	✅ Shared task list	✅ Queue blockers, workflow dependencies, and transactional handoffs
Agent activity and history	✅ Messages, tool calls, timeline, token use, and cost	⚠️ Session recall, feed, metrics	⚠️ Run transcripts + audited cost ledger (estimates possible)	⚠️ Agent chat + terminal	⚠️ CLI transcripts + background logs	✅ Activity feed, transcripts, queue audit, and runtime-dependent telemetry
Organizations & global overview	✅ Nested groups, live team/task status, relations, cross-team activity	⚠️ Coordination hierarchy, no editable org map	✅ Org chart + board governance	⚠️ Team admin, no live org map	❌	⚠️ Org/group policies + topology; no editable company org map
Mixed AI teammates	✅ Claude Code, Codex, OpenCode, Cursor, SuperGrok, GitHub Copilot, Z.AI, MiniMax, and Kiro in one team	✅ Many providers, terminal-first	✅ Own runtimes + MCP clients; experimental Runner adapters	⚠️ Multi-model parent + subagents, no peer team	⚠️ Claude-only experimental teams	✅ Claude, Codex, Pi, Oh My Pi + experimental hosted MCP members
Budget controls	✅ Budget alerts + hard caps for scheduled runs	⚠️ Cost tiers + digest, no hard caps	✅ Per-agent budgets + hard stops	⚠️ Usage + cloud spend limits	⚠️ Usage/org limits + print-mode hard cap	⚠️ Token-burn/provider-window monitoring; no documented spend cap
Separate agent workspaces	✅ Optional workspace per teammate	✅ Core primitive	✅ Worktrees / branches	✅ Agents Window worktrees	✅ Built-in for sessions and subagents	⚠️ Per-seat working directories; externally managed Git worktrees
Terminal	✅ Built-in visual terminal for team and local commands	⚠️ Terminal-based workflow, no built-in terminal	⚠️ Runs commands, no interactive terminal	✅ Built-in IDE terminal	⚠️ Runs in your terminal	✅ tmux + herdr/cmux integration; optional maintenance web terminal
Built-in code editor	✅ With Git support	❌	❌ Control plane, not editor	✅ Full IDE	❌	⚠️ Basic file editor in optional maintenance web UI
Task attachments	✅ Auto-attach, agents read & attach files	❌ Not task-level	✅ Docs, attachments, work products	⚠️ Prompt context, not task attachments	⚠️ Prompt files/images, not task attachments	⚠️ Queue evidence refs, proof media, and Slack file attachments
Price	Free OSS UI + free model with no auth, paid providers optional	Free OSS, runtime plans needed	Free OSS, self-hosted + infra	Free + paid usage	Claude plan or API usage	Free OSS; Apache-2.0; provider usage and hosting costs apply

Live collaboration scores are qualitative editorial assessments of documented communication, task ownership and dependencies, completion, and review capabilities; they are not benchmark results.

Research refreshed November 6, 2026 using published releases and official docs: Agent Teams v2.18.6 (November 5), Gas Town v1.2.1, Paperclip v2026.1023.0, Claude Code v2.1.318, and OpenRig v0.7.8 (November 5). Desktop platform coverage is about native app/CLI support only; web and mobile are excluded. Experimental capabilities are explicitly qualified. Scores are editorial, not live benchmarks. Updated evidence.

• Agent Teams: collaboration controller, organizations feature, terminal workspace, token usage budgets, scheduled run budget cap
• Gas Town: README, provider guide, scheduler, dashboard source, v1.2.1 release
• Paperclip: stable v2026.1023.0 release, README, adapters, heartbeat protocol, org chart, OrgChart source, budgets, runtime services, Kanban source, work products, v2026.824.1 release (historical)
• Cursor: desktop downloads, terminal, Cloud Agents, Agents Window, subagents, Agent Review, Bugbot, worktrees, models and pricing, team pricing
• Claude Code CLI: supported platforms, CLI, agent teams, cross-session messaging, worktrees, subagents, dynamic workflows, costs, Claude pricing, v2.1.246 release
• OpenRig: stable v0.7.8 release, platform requirements, historical v0.6.5 README, OpenRig coordination and queue, OpenRig snapshot and restore, OpenRig workspace model, OpenRig basic web editor; row-by-row evidence
• Historical fact ledger (June–August 2026): comparison research notes

---

Quick start

1. Download the app for your platform (see Installation)
2. Launch the desktop app - start with the free model with no auth, or let the setup wizard detect runtimes and guide provider authentication
3. Create a team — Pick a project, define roles, write a provisioning prompt
4. Watch — Agents spawn, create tasks, and work. You see it all on the kanban board

The desktop app is the main product. The web version is currently in development.

---

FAQ

For the general audience, that might be enough. But people often need to build many/large/complex projects, and that's where bigger teams of agents become necessary, each with their own roles and responsibilities.

And when you have a lot of teammates, you need a good way to organize and manage them. That's exactly where Agent Teams comes in. You can see everything clearly in a visual interface, understand what's happening across your teams, and easily interact with individual agents.

Sure, you can set up something similar with regular Claude, but keeping track of everything without a proper frontend is difficult, and we are targeting precisely this multi-agent use case.

For us, it's not just about running multi-agent systems. It's about having full visibility into who's doing what, keeping everything organized, and making it easy to interact with your agents.

---

Roadmap (new)

• Launching 24/7 autonomous teams in the cloud (in progress)
• Automatic account switching (in progress)
• Navigating very complex long tasks without losing context (in progress)
• Multiple AI runtimes and provider-backed coding agents (more in progress)
• A secure universal plugin system regardless of the type of agents (in progress)
• Efficiency and controllability under load with 50-100+ agents in parallel (in progress)

Vision

Agent Teams AI is moving toward a simple interface for highly autonomous work. From a phone, users should be able to see only the high-level tasks that matter and give the lead agent instructions by voice. The lead should route each request to the right project and team, while agents break it down, work in parallel, communicate, review, resolve blockers, and prepare the final result with minimal supervision.

Technical subtasks and coordination should remain available as a secondary layer, while the main view surfaces only the decisions, blockers, and outcomes that genuinely need attention. Agents should first try to solve problems together and involve the user only when human input is truly required.

This vision is not tied to a specific SDLC or workflow. Users should be free to organize teams however they prefer and continue using their existing plugins, skills, MCP servers, rules, and agent settings.

Development

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

Tech stack

Electron 40, React 19, TypeScript 5, Tailwind CSS 3, Zustand 4. The desktop app reads local project, app, and runtime/session data. Claude Code data under ~/.claude/ is one supported local source, while some runtime modes may also use provider or startup capability services when required.

Prerequisites: Node.js 26.12.1 Current (recommended for source builds) or Node.js 24.22.1 LTS, pnpm 11.22.0

On macOS, official Node.js 24 prebuilt binaries require macOS 13.5+. Node.js 26 does not bundle Corepack; install the pinned pnpm version separately if pnpm is unavailable.

git clone https://github.com/777genius/agent-teams-ai.git
cd agent-teams-ai
pnpm install
pnpm dev

pnpm dev starts the desktop Electron app. Do not start a browser/web dev server for normal development; that path is limited and is not the supported way to run agent teams locally.

To run the desktop app against a local orchestrator checkout during development, point it at the source launcher:

CLAUDE_AGENT_TEAMS_ORCHESTRATOR_CLI_PATH=/absolute/path/to/agent_teams_orchestrator/cli-source \
  pnpm dev

This runs the current orchestrator sources directly through Bun and avoids rebuilding the complete runtime bundle on every app start. Do not use CLAUDE_DEV_RUNTIME_ROOT for the normal source development loop: that override runs bun run build:dev before Electron starts and can make the app appear stuck at bun run ./scripts/build.ts --dev. Use it only when intentionally validating the generated development bundle.

Use pnpm dev:mcp for automated interactive or visual UI verification. It exposes the current Electron renderer through the local Chrome DevTools Protocol endpoint on 127.0.0.1:9222, avoiding window-selection ambiguity when packaged or other Electron apps are also open.

The desktop app auto-discovers Claude Code projects from ~/.claude/.

Terminal Platform integration

Fresh clones install Terminal Platform SDK packages from vendor/terminal-platform, so pnpm install --frozen-lockfile does not require a sibling ../terminal-platform checkout. Those artifacts are pinned in vendor/terminal-platform/manifest.json and can be refreshed from a local Terminal Platform checkout with:

CLAUDE_TERMINAL_PLATFORM_ROOT=/path/to/terminal-platform pnpm terminal-platform:pack

For local Terminal Platform development, build Terminal Platform first, then run this app with the same environment variable:

CLAUDE_TERMINAL_PLATFORM_ROOT=/path/to/terminal-platform pnpm dev:mcp

When the variable is set, the Electron build aliases Terminal Platform SDK imports to that local checkout and the terminal runtime loads terminal-platform-node from the local native artifact.

Debug teammate runtimes

Development launches use the app-managed process backend for teammates by default. To inspect teammates in tmux panes while debugging, start the desktop app with:

CLAUDE_TEAM_TEAMMATE_MODE=tmux pnpm dev

The same override is available per launch from custom CLI args with --teammate-mode tmux. Use this as an operator/debug mode; the default process backend provides stronger app-owned lifecycle, diagnostics, and cleanup for normal team launches.

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            # Current platform

Distribution scripts run the production build and stage the bundled multimodel runtime from runtime.lock.json before packaging. Use pnpm clean:runtime to remove staged runtime files after local packaging.

Scripts

Command	Description
pnpm dev	Desktop app development with hot reload
pnpm dev:mcp	Desktop app development with hot reload and local CDP debugging on port 9222
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

---

---

Contributing

See CONTRIBUTING.md for development guidelines. Please read our Code of Conduct.

By opening a pull request you agree to the Contributor License Agreement v2. You keep copyright.

Partnerships

We are open to partnerships and collaboration opportunities. If you see a way to create value together, we are ready to discuss mutually beneficial terms.

Contact: [email protected]

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.

The standalone HTTP dashboard is intended for local or trusted-network use and does not include built-in authentication for public deployment. Do not expose it directly to the internet without an authenticated reverse proxy.

GitHub Dependabot helps surface dependencies with known vulnerabilities and available security updates.

License

AGPL-3.0

Opening a pull request agrees to CLA v2. That does not replace AGPL-3.0 on the public repository. It lets the project owner sublicense that work under additional terms (for example a commercial license) while keeping the AGPL-3.0 grant from the submission date.