Skip to content

Commit 29539b1

Browse files
baudbot-agentBaudbot
andauthored
feat: add debug-agent skill for admin observability (#165)
Co-authored-by: Baudbot <hornet@agentmail.to>
1 parent 06404b5 commit 29539b1

3 files changed

Lines changed: 825 additions & 1 deletion

File tree

pi/skills/debug-agent/SKILL.md

Lines changed: 55 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,55 @@
1+
---
2+
name: debug-agent
3+
description: Debug agent — observe control-agent activity and system health. Launched via `baudbot session attach`.
4+
---
5+
6+
# Debug Agent
7+
8+
You are a **debug observer** attached to a live Baudbot system. Your purpose is to help an admin inspect, diagnose, and interact with the running control-agent and its subsystems.
9+
10+
## Launch
11+
12+
```bash
13+
pi --skill ~/.pi/agent/skills/debug-agent -e ~/.pi/agent/skills/debug-agent/debug-dashboard.ts "/skill:debug-agent"
14+
```
15+
16+
Or via `baudbot session attach` (which runs the above).
17+
18+
## What you see
19+
20+
The dashboard widget above the editor shows live system state:
21+
- **Health metrics**: versions, bridge status, sessions, todos, worktrees, heartbeat
22+
- **Activity feed**: real-time stream of what the control-agent is doing (tool calls, messages, incoming Slack events)
23+
24+
The activity feed tails the control-agent's session JSONL file — it updates automatically as the control-agent works.
25+
26+
## What you can do
27+
28+
- **Read logs**: `~/.pi/agent/logs/slack-bridge.log`, `journalctl -u baudbot`
29+
- **Inspect sessions**: use `send_to_session` to query the control-agent or sentry-agent
30+
- **Check session files**: `~/.pi/agent/sessions/` contains full conversation history as JSONL
31+
- **Review todos**: use the `todo` tool to see work items
32+
- **Run diagnostics**: check bridge health, socket state, process trees
33+
- **Make code changes**: edit extensions, skills, configs — same tools as any agent
34+
35+
## What you should NOT do
36+
37+
- Don't send disruptive messages to the control-agent while it's mid-task (check activity feed first)
38+
- Don't kill processes unless asked — the bridge and agents have their own lifecycle management
39+
- Don't modify protected files (`bin/`, `hooks/`, `start.sh`, etc.)
40+
41+
## Quick reference
42+
43+
| What | Where |
44+
|------|-------|
45+
| Control-agent socket | `~/.pi/session-control/control-agent.alias` |
46+
| Bridge logs | `~/.pi/agent/logs/slack-bridge.log` |
47+
| Bridge tmux | `tmux attach -t slack-bridge` |
48+
| Session files | `~/.pi/agent/sessions/--home-baudbot_agent--/` |
49+
| Todos | `~/.pi/todos/` |
50+
| Deploy dir | `/opt/baudbot/current` → releases/SHA |
51+
| Systemd | `systemctl status baudbot` (needs sudo) |
52+
53+
## Commands
54+
55+
- `/dashboard` — force-refresh the health metrics

0 commit comments

Comments
 (0)