CLI Quick Start
Get started with CCCC using the command line.
Step 1: Navigate to Your Project
bash
cd /path/to/your/projectStep 2: Create a Working Group
bash
cccc attach .This binds the current directory as a "scope" and creates a working group.
Step 3: Configure MCP for Your Runtime
bash
cccc setup --runtime claude # or codex, droid, opencode, copilotThis configures the MCP (Model Context Protocol) so agents can interact with CCCC.
Step 4: Add Your First Agent
bash
cccc actor add assistant --runtime claudeThe first enabled actor automatically becomes the "foreman" (coordinator).
Step 5: Start the Agent
bash
cccc group startOr start a specific agent:
bash
cccc actor start assistantStep 6: Send a Message
bash
cccc send "Hello! Please introduce yourself."Step 7: View Responses
Watch the ledger in real-time:
bash
cccc tail -fOr check inbox:
bash
cccc inboxAdding More Agents
Add a second agent:
bash
cccc actor add reviewer --runtime codex
cccc actor start reviewerSend to specific agents:
bash
cccc send "@assistant Please implement the feature"
cccc send "@reviewer Please review the code"
cccc send "@all Status update please"Reply to Messages
bash
# Find the event ID from cccc tail
cccc reply evt_abc123 "Thanks, that looks good!"Common Commands
Group Management
bash
cccc groups # List all groups
cccc use <group_id> # Switch group
cccc group info # Show current group
cccc group start # Start all agents
cccc group stop # Stop all agentsActor Management
bash
cccc actor list # List actors
cccc actor add <id> --runtime <r> # Add actor
cccc actor start <id> # Start actor
cccc actor stop <id> # Stop actor
cccc actor restart <id> # Restart actor
cccc actor remove <id> # Remove actorMessaging
bash
cccc send "message" # Broadcast
cccc send "msg" --to @all # Explicit broadcast
cccc send "msg" --to assistant # To specific actor
cccc reply <event_id> "response" # Reply to message
cccc inbox # View unread
cccc tail -n 50 # Recent events
cccc tail -f # Follow eventsDaemon Control
bash
cccc daemon status # Check status
cccc daemon start # Start daemon
cccc daemon stop # Stop daemon
cccc daemon logs -f # Follow logsStart Web UI (Optional)
While using CLI, you can also open the Web UI:
bash
cccc # Starts daemon + Web UIOr just the Web UI (if daemon is already running):
bash
cccc webAccess at http://127.0.0.1:8848/
Environment Variables
| Variable | Default | Description |
|---|---|---|
CCCC_HOME | ~/.cccc | Runtime directory |
CCCC_WEB_PORT | 8848 | Web UI port |
CCCC_LOG_LEVEL | INFO | Log verbosity |
Example Workflow
bash
# Setup
cd ~/projects/my-app
cccc attach .
cccc setup --runtime claude
cccc actor add dev --runtime claude
# Work
cccc group start
cccc send "Please implement user authentication"
# Monitor
cccc tail -f
# Interact
cccc reply evt_123 "Use JWT tokens please"
cccc send "@dev What's the progress?"
# Cleanup
cccc group stopTroubleshooting
Daemon not starting?
bash
cccc daemon status
cccc daemon stop # Stop any stuck instance
cccc daemon startAgent not responding?
bash
# Check agent status
cccc actor list
# Restart the agent
cccc actor restart <actor_id>
# Check MCP setup
cccc setup --runtime <name>Can't find my group?
bash
# List all groups
cccc groups
# Re-attach if needed
cd /path/to/project
cccc attach .Next Steps
- Workflows - Learn collaboration patterns
- CLI Reference - Complete command reference
- IM Bridge - Set up mobile access