Self-hosted mission control for Claude Code & Codex — drive a team of always-on background agents from Telegram/lark/...
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Not hard to test, not trivial to unwind. Worth trying if it closes a sharp gap.
GitHub health unknown. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
Multiple
Model
Claude
Fastest way to find out if ccteam belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
# Visit: https://github.com/firstintent/ccteamRun this first. You will know quickly if the workflow earns a permanent slot.
# No automated removal — visit https://github.com/firstintent/ccteamNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ ccteam/ ← installs here └─ settings.json
Self-hosted mission control for Claude Code & Codex — drive a team of always-on background agents from Telegram/lark/web. 自托管的7*24后台智能体团队，Telegram/飞书/网页端控制远程Claude Code/Codex.
Source: GitHub repository
Source check: No source check recorded
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.