debug

# NanoClaw Container Debugging This guide covers debugging the containerized agent execution system. ## Architecture Overview The host is a single Node process that orchestrates per-session agent containers. The two session DBs are the **sole** IO surface between host and container — there is no IPC, no file watcher, and no stdin piping. ``` Host (Node) Container (Bun, Linux VM) ────────────────────────────────────────────────────────────────────── src/container-runner.ts container/agent-runner/src/ │ │ │ spawns one container per session │ polls inbound.db for work, │ with the session folder mounted │ calls the agent provider, │ at /workspace │ writes replies to outbound.db │ │ ├── data/v2-sessions/<group>/<session>/ ──> /workspace │ ├── inbound.db (host writes, container reads RO) │ ├── outbound.db (container writes, host reads) │ └── .heartbeat (container touches → /workspace/.heartbeat) ├── groups/<folder> ─────────────────────> /workspace/agent (cwd) ├── <group>/.claude-shared ──────────────> /home/node/.claude └── agent-runner src + skills ───────────> /app/src, /app/skills ``` **Message flow:** host writes a row to `inbound.db` (`messages_in`) and wakes the container; the container's poll loop picks it up, runs the agent, and ...