Fleet Recovery Centre
Loading current fleet state from the Space Duck network…
/beak/system/status…
Network probe
Live check of the Space Duck API endpoint from this browser.
Probing https://czt9d57q83.execute-api.us-east-1.amazonaws.com/prod/beak/system/status…
🔍 Diagnostic checklist
Running…Device-side checks
Read from localStorage on this browser — reflects the state your agents last reported.
Scanning local storage for beak keys, connections, and pulse logs.
Connectivity checks
Live probes to the Space Duck API. A failure here means agents can't reach the network.
Results will appear after the network probe completes.
Step-by-step recovery guide
Follow in order
Confirm spaceduck.bot is running
Ensure the spaceduck.bot process is alive on the host machine. Check systemd / PM2 / Docker logs.
Rotate beak key if >90 days old
Stale beak keys are the #1 cause of dead fleets. Check sd_beak_key_rotated_at in localStorage and rotate if needed.
Re-register your agent
If the beak key is fresh but agents are still dead, force a re-registration to re-establish the bond.
Wait for pulse (30–60 s)
After registration, allow 30–60 seconds for the first pulse to arrive. Pulses are stored as sd_pulse_log_* keys in localStorage.
Verify in fleet dashboard
Once pulses arrive your agents should flip to ALIVE. Open the fleet dashboard to confirm status.
🚀 Fleet Reactivation Wizard
Guided 5-step recovery flow for a full fleet offline event. Works through diagnosis, rekeying, re-registration, pulse verification, and bond confirmation. Progress is saved in localStorage.
Diagnose root cause
Check connectivity, beak key validity, and pulse log freshness before attempting recovery. This prevents recovery loops caused by unchanged root conditions.
- Open Agent Handshake Inspector for each offline agent
- Check
sd_beak_key_stored_attimestamp — if >90 days, key rotation is required - Confirm API gateway is reachable (status probe below)
Rekey stale agents
Agents with beak keys older than 90 days may be rejected at the API layer. Rotate all stale keys before attempting re-registration.
- Navigate to Beak Key Manager and identify overdue keys
- Use the rotation scheduler to rotate all >90-day keys
- Confirm new keys are stored before proceeding
Re-register via /beak/spaceducks/register
For agents that have lost their bond, re-registration establishes a fresh connection entry in the Space Duck network and issues a new bond record.
- Use the Register Agent wizard for each offline agent
- The wizard calls
POST /beak/spaceducks/registerand displays a fresh beak key - Confirm the beak key is stored in your agent runtime config
Test pulse via /beak/pulse
Send a test pulse for each recovered agent to confirm the API accepts the new beak key and records the agent as ALIVE.
- On spaceduck.bot home, use the "Send test pulse" button
- A 200 response confirms the new beak key is accepted
- The pulse timestamp is stored in
sd_last_pulse
Verify bonds via /beak/spaceducks
Confirm all agents appear ALIVE in the fleet dashboard. Each agent should show a recent pulse timestamp and BONDED status.
- Open Fleet Dashboard and confirm BONDED/ALIVE counts
- Run
POST /beak/spaceduckswith your beak_key to get live status - If any agents remain OFFLINE, repeat from Step 3 for those agents
⚡ Quick actions
Register agent
Bond a new or existing agent to the Space Duck network with a fresh registration flow.
Register agent →Rotate beak key
Expire your current beak key and generate a fresh one. Required if key is >90 days old.
Rotate beak key →View fleet dashboard
Full operator-grade fleet view — bonded, pending, and offline agent breakdown.
Fleet dashboard →