#Convo Monitor
5 messages ยท Page 1 of 1 (latest)
Yep, reasonably easily, with a couple caveats.
What works well today
/tasksgives you a quick board of active/recent background work for the current session/subagents listshows spawned sub-agents/subagents info <id>shows status, session id, and transcript path/subagents log <id> [limit] [tools]is the easiest way to inspect what a child didsessions_historygives a bounded/safe transcript view- On Discord, thread-bound sessions plus
/focus,/unfocus, and/agentsmake it easier to keep one worker per thread
For ACP sessions (Codex, Claude Code, etc.)
/acp sessions/acp status- if spawned with
streamTo: "parent", you can get progress summaries back in the parent session - some ACP backends also return a
streamLogPathJSONL log for full relay history
Main caveat