observe

/observe

Agents Observe dashboard and server management.

Usage

• /observe — Open the dashboard URL
• /observe status — Show server health and config details
• /observe start — Start the server
• /observe stop — Stop the server
• /observe restart — Restart the server
• /observe logs — Show recent Docker container logs
• /observe debug — Diagnose server issues (health, docker logs, mcp.log, cli.log)

Instructions

The subcommand is in $ARGUMENTS. If empty, default to showing the dashboard URL.

/observe (no args)

1. Run:

   node ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/observe_cli.mjs health
   

2. If exit code 0: show the dashboard URL from the output.
3. If exit code 1: tell the user the server is not running and suggest /observe start or /observe status.

/observe status

1. Run:

   node ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/observe_cli.mjs health
   

2. Show the full output to the user (includes version, runtime, ports, log paths).
3. If the output contains "Version mismatch", tell the user and offer /observe restart.
4. If exit code 1, show the output and suggest /observe start.

/observe start

1. Run:

   node ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/observe_cli.mjs start
   

2. Show the output to the user. If successful, include the dashboard URL.

/observe stop

1. Run:

   node ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/observe_cli.mjs stop
   

2. Confirm to the user that the server has been stopped.

/observe restart

1. Run:

   node ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/observe_cli.mjs restart
   

2. Show the output to the user. If successful, include the dashboard URL.

/observe logs

1. Run:

   node ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/observe_cli.mjs logs -n 50
   

2. Show the output to the user. Do NOT use -f (follow) — it would hang.

/observe debug

Run these checks in sequence. Read each output before running the next — use what you learn to diagnose the issue.

1. Server health:

   node ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/observe_cli.mjs health
   

2. Docker container logs (last 20 lines):

   node ${CLAUDE_PLUGIN_ROOT}/hooks/scripts/observe_cli.mjs logs -n 20
   

3. MCP log (last 20 lines). The path depends on where the plugin stores data. Check these locations:

   tail -n 20 ~/.claude/plugins/data/agents-observe/logs/mcp.log 2>/dev/null || \
   tail -n 20 ~/.claude/plugins/data/agents-observe-inline/logs/mcp.log 2>/dev/null || \
   tail -n 20 ~/.agents-observe/logs/mcp.log 2>/dev/null || \
   echo "mcp.log not found"
   

4. CLI log (last 20 lines):

   tail -n 20 ~/.claude/plugins/data/agents-observe/logs/cli.log 2>/dev/null || \
   tail -n 20 ~/.claude/plugins/data/agents-observe-inline/logs/cli.log 2>/dev/null || \
   tail -n 20 ~/.agents-observe/logs/cli.log 2>/dev/null || \
   echo "cli.log not found"
   

5. Analyze the results and tell the user:

   • Is the server running? What version?
   • Are there errors in the docker logs? (look for crash loops, port conflicts, DB errors)
   • Are there errors in mcp.log? (look for startServer failures, image pull errors)
   • Are there errors in cli.log? (look for ECONNREFUSED, hook delivery failures)
   • Suggest specific fixes based on what you find.