Diagnose and fix NanoClaw container runtime issues via log, heartbeat, and mount inspection.
npx skills add https://github.com/Bartunek/nanoclaw --skill debug-bartunek
Please help me install this Agent Skill. Skill: debug Source: https://github.com/Bartunek/nanoclaw/tree/main/.claude/skills/debug Command: npx skills add https://github.com/Bartunek/nanoclaw --skill debug-bartunek
Debugging NanoClaw's containerized agent runtime can be difficult due to the complexity of host/container interactions, scattered logs, and per-session state stored in session DBs. This Skill centralizes the diagnosis workflow, guiding you through log inspection, heartbeat checks, and mount verification to identify root causes quickly.
Begin by inspecting the failing session's logs, heartbeat, and mounts, then follow the guided steps to diagnose and remediate the container issue.
High-intent search queries and answers about installing and using this skill.
To diagnose a container that fails to start, inspect the failing session's logs, heartbeat files, and mount paths to identify host errors or misconfigurations. Reviewing per-session state in the session DBs helps pinpoint the root cause of the spawn failure.
A container session stalls due to host/container interaction issues, authentication errors, or mount misconfigurations affecting isolation. Fix the stalled session by following guided restart workflows and environment checks with clear guardrails to safely restore operation.
Inspect session DBs and heartbeat files by safely reviewing inbound/outbound DBs and processingAck signals to understand message flow and container health. This centralized diagnostic workflow reveals per-session state and misconfigurations affecting the runtime.
The best way to troubleshoot authentication errors in a containerized agent runtime is to verify environment checks and inspect logs. Centralized diagnostics guide you through log inspection and session-state visibility to resolve auth-related failures.
Verify mount paths during container diagnostics when a session stalls or a container exits unexpectedly. Mount verification identifies misconfigurations affecting per-session isolation and helps determine whether the root issue is a configuration problem.
You can safely restart a stuck container session by following prescribed remediation workflows and environment checks with clear guardrails. These steps ensure per-session isolation is maintained while restoring the container's operation.
wientjesDiagnose NanoClaw container agent authentication, mount, and log failures.
dezverevStart the AnimalKernel.Web dev server and verify UI with Cursor's browser.
tharunramagiriDiagnose containerized agent failures by inspecting session databases and host logs.
leonj1Diagnose NanoClaw container runtime issues via logs, env vars, and mounts.
