danm72/mission-control/mission-control-setup

https://missioncontrol.ai/api/setup/{squad_id}

SQUAD_ID="<extracted_from_url>"
MARKER_FILE="$HOME/.openclaw/missions/$SQUAD_ID/setup-completed"
 
if [ -f "$MARKER_FILE" ]; then
  echo "Setup already completed for squad $SQUAD_ID"
  echo "Completed at: $(cat $MARKER_FILE)"
  # Ask user if they want to re-run
fi

SETUP_URL="<full_url_from_user>"
 
# Extract squad_id from URL path
# URL format: https://missioncontrol.ai/api/setup/{squad_id}
# Token may be in URL query param (legacy) or provided separately
SQUAD_ID=$(echo "$SETUP_URL" | sed -n 's|.*/api/setup/\([^?]*\).*|\1|p')
TOKEN=$(echo "$SETUP_URL" | sed -n 's|.*token=\([^&]*\).*|\1|p')

# Build the base URL (without query params)
BASE_URL="https://missioncontrol.ai/api/setup/$SQUAD_ID"
 
CONFIG_RESPONSE=$(curl -s -w "\n%{http_code}" \
  -H "x-setup-token: $TOKEN" \
  "$BASE_URL")
HTTP_CODE=$(echo "$CONFIG_RESPONSE" | tail -n1)
CONFIG_BODY=$(echo "$CONFIG_RESPONSE" | sed '$d')

# Expected response structure:
# {
#   "squad": { "id": "uuid", "name": "My Squad" },
#   "agents": [
#     { "name": "Lead", "soul_md": "...", "role": "coordinator" },
#     { "name": "Writer", "soul_md": "...", "role": "specialist" }
#   ],
#   "api_key": "mc_prefix_secret",
#   "heartbeat_interval": 300,
#   "heartbeat_stagger": 30,
#   "dashboard_url": "https://missioncontrol.ai/dashboard/abc"
# }

mkdir -p "$HOME/.openclaw/missions/$SQUAD_ID"
echo "$CONFIG_BODY" > "$HOME/.openclaw/missions/$SQUAD_ID/config.json"

Use the sessions_spawn tool with:
- name: <agent.name>
- working_directory: $HOME/.openclaw/sessions/<agent.name>

Creating agent sessions...
  [+] Lead - created
  [=] Writer - already exists, skipped
  [+] Social - created
 
3 agents processed (2 created, 1 skipped)

AGENT_DIR="$HOME/.openclaw/sessions/${AGENT_NAME}"
mkdir -p "$AGENT_DIR"
echo "$AGENT_SOUL_MD" > "$AGENT_DIR/SOUL.md"

Writing SOUL.md files...
  [+] Lead - wrote SOUL.md (1.2 KB)
  [+] Writer - wrote SOUL.md (0.9 KB)
  [+] Social - wrote SOUL.md (1.1 KB)
 
3 SOUL.md files written

SKILL_DIR="$HOME/.openclaw/skills/mission-control"
mkdir -p "$SKILL_DIR"

cat > "$SKILL_DIR/SKILL.md" << 'EOF'
# Mission Control Runtime Skill
 
Provides heartbeat and task management for Mission Control agents.
 
## Metadata
 
| Field | Value |
|-------|-------|
| name | mission-control |
| version | 1.0.0 |
 
## Commands
 
### heartbeat
 
Send a heartbeat to Mission Control. Run on a schedule via cron.
 

 
### fetch-tasks
 
Check for new tasks assigned to this agent.
 

 
### complete-task
 
Mark a task as completed.
 

EOF

# Example with 300s interval and 30s stagger for 3 agents:
# Lead:   every 300s, offset 0s   -> 0, 300, 600, ...
# Writer: every 300s, offset 30s  -> 30, 330, 630, ...
# Social: every 300s, offset 60s  -> 60, 360, 660, ...

CRON_FILE="$HOME/.openclaw/cron/jobs.json"
mkdir -p "$(dirname "$CRON_FILE")"
 
# Read existing jobs or create empty array
if [ -f "$CRON_FILE" ]; then
  EXISTING_JOBS=$(cat "$CRON_FILE")
else
  EXISTING_JOBS="[]"
fi

{
  "id": "{squad_id}-{agent_name}-heartbeat",
  "type": "heartbeat",
  "agent": "{agent_name}",
  "squad_id": "{squad_id}",
  "interval_seconds": 300,
  "offset_seconds": 0,
  "command": "mission-control heartbeat",
  "enabled": true
}

Configuring heartbeat crons...
  [+] Lead - every 5m, offset 0s
  [+] Writer - every 5m, offset 30s
  [+] Social - every 5m, offset 60s
 
Cron jobs written to ~/.openclaw/cron/jobs.json

for AGENT_NAME in "${AGENTS[@]}"; do
  RESPONSE=$(curl -s -o /dev/null -w "%{http_code}" \
    -X POST "https://missioncontrol.ai/api/agents/heartbeat" \
    -H "Authorization: Bearer $API_KEY" \
    -H "Content-Type: application/json" \
    -d "{\"agent\": \"$AGENT_NAME\", \"status\": \"setup_test\"}")
 
  if [ "$RESPONSE" = "200" ]; then
    echo "[OK] $AGENT_NAME - connected"
  else
    echo "[FAIL] $AGENT_NAME - HTTP $RESPONSE"
  fi
done

MARKER_FILE="$HOME/.openclaw/missions/$SQUAD_ID/setup-completed"
mkdir -p "$(dirname "$MARKER_FILE")"
date -u +"%Y-%m-%dT%H:%M:%SZ" > "$MARKER_FILE"

========================================
Mission Control Setup Complete
========================================
 
Squad: My Content Squad
Squad ID: abc123-def456-...
 
Agents Created:
  - Lead (coordinator)
  - Writer (specialist)
  - Social (specialist)
 
Heartbeat Schedule:
  - Lead: every 5 minutes
  - Writer: every 5 minutes (offset +30s)
  - Social: every 5 minutes (offset +60s)
 
Files Created:
  - ~/.openclaw/sessions/Lead/SOUL.md
  - ~/.openclaw/sessions/Writer/SOUL.md
  - ~/.openclaw/sessions/Social/SOUL.md
  - ~/.openclaw/skills/mission-control/SKILL.md
  - ~/.openclaw/cron/jobs.json
 
Dashboard: https://missioncontrol.ai/dashboard/abc123
 
Next Steps:
  1. Start your agents using your agent management tool
  2. Check the dashboard to see agents come online
  3. Create your first task from the dashboard
 
========================================

Error: Invalid setup URL format
 
Expected format:
  https://missioncontrol.ai/api/setup/{squad_id}
 
The setup token should be provided via the x-setup-token header.
Legacy URLs with ?token= query parameter are still supported but deprecated.
 
Received:
  {user_provided_url}
 
Please copy the complete setup URL from Mission Control.

Error: Setup link has expired
 
Setup links are valid for 24 hours. Please:
  1. Go to Mission Control dashboard
  2. Navigate to your squad settings
  3. Generate a new setup link
  4. Run setup again with the new link

Error: Could not connect to Mission Control
 
Please check:
  - Internet connection is working
  - Mission Control (missioncontrol.ai) is accessible
  - No firewall blocking outbound HTTPS
 
You can retry setup once the connection is restored.

Warning: Setup completed with issues
 
Successful:
  - Configuration fetched
  - Agent sessions created
  - SOUL.md files written
 
Failed:
  - Heartbeat verification for "Social" (HTTP 500)
 
The setup is complete. The verification failure is likely temporary.
Check the Mission Control dashboard in a few minutes.