# Start the daemon (run in the background with automatic port allocation)
codebuddy daemon start

# Specify a port
codebuddy daemon start --port 8080

# Specify a bind address (allow remote access)
codebuddy daemon start --host 0.0.0.0

# Specify a permission mode (defaults to delegate mode)
codebuddy daemon start --permission-mode default

# Pass other standard parameters (model, mcp-config, and others are inherited automatically)
codebuddy daemon start --model claude-sonnet-4-20250514 --mcp-config ./.mcp.json

codebuddy daemon status
# {"status":"running","pid":12345,"endpoint":"http://127.0.0.1:51862","startedAt":1775498920401}

codebuddy daemon stop
codebuddy daemon restart

# Run tasks in the background
codebuddy --bg "Implement the login page"

# Specify a name (for easier lookup)
codebuddy --bg --name feature-login "Implement the login page"

# List all active workers
codebuddy ps

# View background session logs
codebuddy logs feature-login

# Continuously follow logs (similar to tail -f)
codebuddy logs feature-login -f

# Attach to a background session
codebuddy attach feature-login

# Terminate a background session
codebuddy kill feature-login

# List all workers
curl http://127.0.0.1:8080/api/v1/workers

# Start the Daemon
curl -X POST http://127.0.0.1:8080/api/v1/daemon/start \\
  -H "Content-Type: application/json" \\
  -d '{"port": 9090}'

# View Worker logs (telemetry logs)
curl "http://127.0.0.1:8080/api/v1/workers/12345/logs?type=telemetry&tail=100"

# Terminate a Worker
curl -X DELETE http://127.0.0.1:8080/api/v1/workers/12345

~/.codebuddy/sessions/
├── 12345.json          # Local process (PID as the filename)
├── 67890.json          # Another local process
└── manual-abc123.json  # Manually added remote Worker

{
  "pid": 12345,
  "sessionId": "interactive-12345",
  "cwd": "/home/user/project",
  "startedAt": 1775498920401,
  "kind": "interactive",
  "url": "http://127.0.0.1:8080",
  "mode": "local",
  "version": "2.78.1",
  "hostname": "my-machine"
}

# Register as a system service and start the daemon immediately
codebuddy daemon install

# Specify the port and permission mode
codebuddy daemon install --port 8080 --permission-mode bypassPermissions

# Remove the system service registration
codebuddy daemon uninstall

{
  "status": "running",
  "pid": 42567,
  "endpoint": "http://127.0.0.1:9527",
  "systemService": {
    "installed": true,
    "backend": "launchd",
    "configPath": "/Users/xxx/Library/LaunchAgents/com.codebuddy.daemon.plist"
  }
}

# Native management on macOS
launchctl list | grep codebuddy
launchctl stop com.codebuddy.daemon
launchctl start com.codebuddy.daemon

# Native management on Linux
systemctl --user status codebuddy-daemon
systemctl --user stop codebuddy-daemon
systemctl --user start codebuddy-daemon

# Native management on Windows
schtasks /query /tn "CodeBuddy Daemon"

codebuddy daemon start --port 8080
# Open http://127.0.0.1:8080 in a browser to start using it
# The service keeps running after the terminal is closed

# Starting in CI
codebuddy daemon start --port 9090

# Calling from other CI steps (the body must be in Gateway Protocol format and include id/type)
curl -X POST http://127.0.0.1:9090/api/v1/runs \\
  -H "Content-Type: application/json" \\
  -H "X-CodeBuddy-Request: 1" \\
  -d '{"id": "run-1", "type": "message", "payload": {"text": "Review the code changes in this PR"}}'
# Response: {"data": {"runId": "uuid-xxx", "status": "accepted"}}

codebuddy daemon start --host 0.0.0.0 --port 8080
# Colleagues can access http://192.168.1.100:8080

codebuddy --bg --name "refactor-auth" "Refactor the authentication module"
codebuddy --bg --name "add-tests" "Add unit tests for the utils directory"
codebuddy --bg --name "fix-types" "Fix all TypeScript type errors"

# Check progress
codebuddy ps
codebuddy logs refactor-auth

codebuddy daemon start
# Connect WeChat/WeCom channels with the remote control feature