CentralCommand Documentation

Getting Started

CentralCommand works in three steps: connect your tools, define workflows, and let operators handle the rest. You stay in control through approval gates and real-time visibility.

# Via CLI
cc tools add --name truncus --type truncus --config '{"apiKey":"..."}'
cc tools add --name tenscore --type tenscore

# Or via API
curl -X POST https://centralcommand.cc/api/tools \
  -H "Authorization: Bearer cc_live_..." \
  -H "Content-Type: application/json" \
  -d '{"name":"truncus","adapterType":"truncus"}'

# Via dashboard
Dashboard → Workflows → New Workflow

# Via CLI
cc workflow create --name "revenue-guardian" \
  --schedule "*/5 * * * *" \
  --steps '[{"id":"check","tool":"tenscore.get_health_score"}]'

Core Concepts

CentralCommand operates on a simple chain: Signal → Operator → Workflow → Outcome → Impact. Every execution follows this path.

Workflows

Workflows are the execution units of CentralCommand. Each workflow contains one or more steps that run sequentially.

{
  "name": "revenue-guardian",
  "description": "Monitor payment health and recover failed charges",
  "schedule": "*/5 * * * *",
  "steps": [
    {
      "id": "check-health",
      "tool": "tenscore.get_health_score",
      "inputs": { "projectId": "your-project-id" }
    },
    {
      "id": "send-alert",
      "tool": "truncus.send_email",
      "inputs": {
        "to": "ops@company.com",
        "subject": "Health alert",
        "body": "Score: ${check-health.score}"
      },
      "condition": "${check-health.score} < 70"
    }
  ]
}

Operators

Operators are the business domain layer. Each operator owns workflows related to a specific function. CentralCommand automatically maps workflows to operators based on naming conventions.

Name your workflows with these keywords to automatically assign them to operators. For example, revenue-guardian-check maps to Revenue Guardian.

Signals & Triggers

Signals are what start your system. Every workflow begins with a signal.

Approval Gates

Approval gates are how you maintain human control over autonomous operations. Any workflow step can require approval before execution.

When a step with requires_approval: true is reached, the run pauses. You can approve or reject via:

• Dashboard → Approvals page
• Run detail page → Approve / Reject buttons
• Telegram bot → inline approval buttons

Every approval is logged with who approved and when — full audit trail.

API Reference

All API endpoints require authentication via cc_live_ API keys. Pass the key as a Bearer token.

curl https://centralcommand.cc/api/runs \
  -H "Authorization: Bearer cc_live_your_key_here"

CLI

The CentralCommand CLI (@centralcommand/cli) provides 21+ commands for managing your control plane from the terminal.

# Install
npm install -g @centralcommand/cli

# Authenticate
cc auth login --key cc_live_...

# Common commands
cc runs list                    # List recent runs
cc runs create --workflow <id>  # Trigger a workflow
cc workflows list               # List workflows
cc tools list                   # List integrations
cc tools health                 # Check integration health

Integrations

CentralCommand connects to your services through typed adapters. Each adapter provides specific tools that workflows can use.

Plans & Billing

CentralCommand offers four tiers. All plans include the full dashboard, audit trails, and contract signing.

Annual billing saves 17%. All paid plans include a free trial period. Manage billing.

Security

CentralCommand is designed for production use with enterprise-grade security.

• HMAC-SHA256 contract signing — every workflow execution is cryptographically signed
• API key hashing — keys are SHA-256 hashed before storage, never persisted in plain text
• Scope-based authorization — fine-grained access control per API key
• Immutable audit logs — every event, approval, and execution is permanently recorded
• Clerk authentication — dashboard secured via industry-standard auth
• Rate limiting — tier-based limits on concurrent runs, monthly runs, and tool invocations

Support

We're here to help you get the most out of CentralCommand.