This skill should be used when the user asks to "check bridgey status", "show bridgey agents", "is bridgey running", "bridgey health", "show connected agents", runs "/bridgey:status", or wants to see the state of the bridgey daemon and connected agents.

bridgey Status

Display the health and status of the bridgey daemon and all connected agents.

Status Check Procedure

1. Check Daemon Health

Use the status MCP tool to get daemon health and agent list. If the daemon is unreachable, inform the user and suggest:

Check if config exists: cat ~/.bridgey/bridgey.config.json
Run /bridgey:setup if no config
Manually start: node ${CLAUDE_PLUGIN_ROOT}/dist/daemon.js start --config ~/.bridgey/bridgey.config.json (if dist/daemon.js is missing, run npm run build from plugins/bridgey/ first)

2. Display Status Dashboard

Present a formatted status overview:

🌉 bridgey status
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Daemon:  ● running (uptime: 2h 34m)
Name:    cloud-coder
Port:    8092
Bind:    localhost

Agents (3 connected):
  ● luna-dev       localhost:8093  local   healthy
  ● cloud-coder    cloud:8092     remote  healthy
  ○ mesa-runner    mesa:8092      remote  offline

Recent Activity (last 5):
  → cloud-coder  "review this PR"           2m ago
  ← luna-dev     "what's the test status?"   15m ago

3. Use Color Indicators

● green/active — agent is healthy and reachable
○ gray/inactive — agent is offline or unreachable
⚠ yellow/warning — agent responded with errors recently

4. Include Troubleshooting

If any agents are offline, suggest:

Check if the remote agent's daemon is running
Verify network connectivity (curl http://agent-url/health)
Check bearer token is correct
For local agents: check if the CC instance is still running
For container agents: verify bind is 0.0.0.0 and source IP is in trusted_networks

If agents return 400 on send:

The /send endpoint requires {agent, message} — the agent field names the target and is required
Verify agent name matches a registered agent (list_agents)

If agents return 401/403:

Bearer token mismatch — verify token matches the remote agent's config
Source IP not in trusted_networks — add the appropriate CIDR range
Docker containers: add 172.16.0.0/12 and 10.0.0.0/8 to trusted_networks
Tailscale: add 100.64.0.0/10 to trusted_networks

If agents return 429:

Rate limited (10 req/min per source IP by default)
Wait and retry, or adjust rate limit config if needed

Quick Status

For a quick one-liner check, run:

curl -s http://localhost:8092/health | jq .

For container deployments, use the Tailscale IP or Docker host:

curl -s http://<tailscale-ip>:8092/health | jq .