AgentDesk

AI team orchestrator for Claude Code. Run collaborative agent sessions from your terminal and watch them live on agentdesk.live.

AgentDesk spawns a team of AI agents inside Claude Code that collaborate on your tasks. The default team includes 7 built-in agents, and you can add custom agents to fit your workflow.

Built-in Agents

| Agent | Role | |-------|------| | Jane | Product Lead — facilitates, clarifies requirements, coordinates the team | | Dennis | Senior Developer — implements the solution | | Sam | Architecture Auditor — code structure, separation of concerns | | Bart | QA Engineer — edge cases, risks, acceptance criteria, screenshots | | Vera | Test Engineer — unit tests, regression coverage | | Luna | UX/UI Designer — visual consistency, accessibility, interaction patterns | | Mark | Content Writer — copy, tone, user-facing text |

You can also add custom agents (e.g., a Security Engineer or DevOps specialist) via project settings.

Getting Started

1. Install

npm i -g @kendoo.agentdesk/agentdesk

Requires Claude Code and Node.js 18+.

2. Sign in

agentdesk login

Opens your browser to agentdesk.live where you sign up or log in (email/password or Google). Your API key is saved automatically.

3. Set up your project

agentdesk init

This detects your project, asks which task tracker you use (Linear, Jira, GitHub Issues, or none), and saves the config.

4. Run a team session

Work on an existing task:

agentdesk team KEN-517

Or just describe what you want — a task is created automatically:

agentdesk team -d "Fix the checkout total calculation"
agentdesk team -d "Add Google OAuth to the login page"

Watch the session live at agentdesk.live. Each session gets a deep link you can share.

Commands

agentdesk login                        Sign in to AgentDesk
agentdesk logout                       Sign out and remove credentials
agentdesk init                         Set up project and configure tracker
agentdesk team <TASK-ID>               Run a team session on an existing task
agentdesk team -d "..."                Describe what you want — task created automatically
agentdesk daemon                       Start daemon for remote sessions
agentdesk update                       Update to the latest version

Options

| Flag | Description | |------|-------------| | --description, -d | Task description or requirements | | --cwd | Working directory (defaults to current) |

Configuration

Settings can be managed in two ways:

1. Web UI — go to agentdesk.live, select a project, and click the gear icon to configure tracker, team composition, custom agents, commands, and instructions.
2. Local file — .agentdesk.json in your project root. Local settings override server settings.

The CLI fetches settings from the server at runtime. If the server is unreachable, it falls back to .agentdesk.json.

Task trackers

| Tracker | Config | |---------|--------| | Linear | Workspace slug (e.g., kendoo) | | Jira | Base URL (e.g., https://company.atlassian.net) + project key | | GitHub Issues | Repository (e.g., owner/repo) | | None | No config needed — pass -d "description" when running a session |

Custom agents

Add custom agents via your project settings at agentdesk.live:

1. Select your project and click the gear icon
2. Under Project Agents, click "Add agent" and fill in the name, role, when, and how
3. Under Team Composition, toggle the new agent on
4. Save

Custom agents participate in all phases alongside built-in agents — brainstorm, planning, execution, and review.

You can also define them in .agentdesk.json as a local override if preferred.

AgentDesk also auto-discovers agents from .claude/agents/, .claude/commands/, .mcp.json, GitHub Actions workflows, Dependabot, and Renovate configs.

How It Works

All agents collaborate in a single Claude process — each with distinct roles, ground rules, and areas of expertise.

1. You run agentdesk team TASK-ID in your project directory
2. AgentDesk detects your project type, reads CLAUDE.md, and discovers existing agents
3. The orchestrator manages 5 phases: Intake > Brainstorm > Planning > Execution > Review
4. Agents discuss, disagree, and build on each other's ideas within a shared context
5. The session streams live to agentdesk.live where you can watch and send messages to the team
6. Token usage is tracked and displayed per session

Daemon (Remote Sessions)

The daemon lets you trigger team sessions from the web dashboard instead of the terminal.

agentdesk daemon

Once running, a "Run Team" button appears on agentdesk.live. Select a project, describe the task, and the daemon spawns a Claude session on your machine. Output streams back to the dashboard in real-time.

Security

• Outbound only — no ports opened on your machine
• Project allowlist — only runs on projects registered via agentdesk init
• No arbitrary commands — only spawns Claude with a fixed set of allowed tools
• Metadata-only logs — session logs in ~/.agentdesk/logs/ contain timestamps and file paths, never sensitive data
• Fail closed — unknown projects or exceeded session limits are rejected

How it works

1. The daemon connects to the server via WebSocket
2. You click "Run Team" in the dashboard
3. The server relays the request to your daemon
4. The daemon spawns claude in the project directory
5. Output streams through the server to the dashboard
6. If the connection drops, output is buffered locally and replayed on reconnect

Dashboard Features

• Live sessions — watch agents collaborate in real-time
• Session deep links — share a direct URL to any session
• Project settings — configure tracker, team, custom agents, and instructions per project
• Account settings — manage your API key and profile
• Agent roster — see each agent's role, participation rate, tag breakdown, and phase involvement
• Token tracking — input/output token counts per session
• Auto-reconnect — CLI reconnects automatically if the connection drops

Requirements

• Claude Code installed and configured
• Node.js 18+
• An AgentDesk account at agentdesk.live