ccteam CLI
A CLI connects installed coding agents into a team, dispatches work between sessions and collects results across machines.
- 641 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Sessions run commands and change files on selected machines; console or bot access controls that work.
Install
- Works in
Manual install
curl -sSL https://raw.githubusercontent.com/firstintent/ccteam/main/install.sh | shInstalls ccteam CLI. Read the installer before running it, then check the selected agent connection.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Sessions run commands and change files on selected machines; console or bot access controls that work.
This is third-party code. Review the repository files before installing.
What it does
ccteam manages different coding-agent sessions through a shared daemon and API. One session can start a worker, dispatch a task and read its result. The user sees delegation relationships and execution state. A browser console and optional messaging channels provide control. A remote machine uses its own installed and authenticated CLI. ccteam coordinates interaction; task execution still depends on the chosen agent and model.
Who it is for. For developers coordinating work among several coding agents they already use.
Good fit when
- Delegate an independent task to another agent.
- Inspect several sessions from a shared console.
- Use a worker on another authorized project machine.
- Retrieve a background result later without guessing whether it completed.
Not a fit when
- No supported agent is installed and authenticated.
- Session control cannot be exposed through the chosen messaging channel.
- You expect a budget limit to reverse commands already executed.
Example request
List available ccteam workers and propose a test-task allocation without creating sessions yet.Limitations
Install and authenticate at least one supported CLI first; a discovered executable alone does not mean an agent is ready. Sessions read and change projects with the selected machine user’s permissions, so begin with a test directory. Console and bot access controls remote execution and must be limited to authorized users. Daily budgets stop new jobs rather than undoing previous edits; inspect active sessions and their results when a cap is reached.
How to disable. Stop sessions through the console and stop the ccteam service. Disable connected bots separately; code changes and saved results remain.
FAQ
Do agents need a shared provider key?
No. Each machine uses its corresponding CLI login. ccteam does not replace provider setup.
Can I connect my own session through MCP?
Yes. Documentation covers client enrollment and tools for creating, reading and stopping descendant sessions.
How is interrupted work recorded?
As a separate interrupted outcome, not a success or empty response.
Can an agent stop any session?
No. MCP enforces descendant and permission boundaries; broader operator control belongs to the console.
Is Telegram required?
No. Local web, CLI and API interfaces work independently of optional messaging channels.
Discussion
No questions or reviews yet.
Related
CLI toolsSquad creates coding-agent teams with roles and shared repository memory for distributing tasks and retaining decisions.
A CLI agent that works with project files and shell commands, lets you choose a model provider and connects external MCP tools.
A terminal workspace where several CLI agents like Codex, Claude and Gemini exchange messages and work on one task under human oversight
A CLI links a machine to IM.codes for remote coding-agent sessions, shared memory and communication between agents
A tmux-based TUI that runs Claude Code, Codex and other agents in one list: status, quick prompts, worktrees and diff review
A bridge between local CLI agents: Codex, Cursor or Claude Code delegate work to Antigravity, Grok, Kimi and seven more.
README in short
The CLI, web console and DeepSeek Harness integration share one daemon. Status views distinguish a session’s own information from broader operator data.