agent-teams-ai

Watch demo on the site or here:

demo_new_15s.webm

Old videos:

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 and use installed claude/codex/opencode and you can configure from the UI.

Table of contents

• Installation
• Table of contents
• What is this
• Comparison
• Quick start
• FAQ
• Development
  • Developer architecture docs
  • Terminal Platform integration
• Tech stack
  • Debug teammate runtimes
  • Build for distribution
  • Scripts
• Ideas
• Contributing
• Security
• License

What is this

An orchestration layer for AI agent teams across Claude, Codex, and OpenCode.

• Claude + Codex + OpenCode orchestration — start with a free model with no auth immediately, or auto-detect available Claude/Codex/OpenCode 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

• 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 — start with the free model with no auth, then connect paid/account providers only when you need them

• Multi-language support - choose the app language and preferred agent communication language. Current UI languages: Arabic, Bengali, Chinese, English, French, German, Hindi, Indonesian, Japanese, Korean, Portuguese, Russian, Spanish, Urdu.

• 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

Comparison

Agent Teams product evidence checked in local source on July 9, 2026: organizations feature, token usage budgets, scheduled run budget cap. Competitor fact sources checked on July 9, 2026: detailed research notes, Gastown README, Gastown provider guide, Gastown scheduler, Gastown dashboard source, Gastown release, Paperclip README, Paperclip adapters, Paperclip heartbeat protocol, , , , , , , , , , , , , , , , , , .

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

Use the desktop app as the primary product. The browser/web path is not needed for normal use and does not provide the full desktop runtime, IPC, terminal, provider auth, or team lifecycle behavior.

FAQ

Development

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

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.

Prerequisites: Node.js 24.16.0 LTS, pnpm 10+

On macOS, official Node.js 24 prebuilt binaries require macOS 13.5+.

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.

Use pnpm dev:mcp when you want an MCP browser/debugging tool to attach to the current Electron renderer through the local Chrome DevTools Protocol endpoint on 127.0.0.1:9222.

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

Ideas

• 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 single createTask
• 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.

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: quantjumppro@gmail.com

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.

GitHub Dependabot monitors dependencies for known vulnerabilities, so security updates are surfaced quickly and applied in time.

License

AGPL-3.0

MCP integration — supports the built-in mcp-server (see mcp-server folder) for integrating external tools and extensible agent plugins out of the box