NanoClaw Container Debug
Diagnostikuje NanoClaw's containerized agent runtime via its two SQLite session DBs a logs.
Otestováno · Funguje
Co umí
Prochází NanoClaw's host/container architecture (inbound.db / outbound.db message flow, mounts, OneCLI gateway secrets, heartbeat liveness) a lists four named failure modes s exact diagnostic commands. Spouští se na generic phrasing ('container fails', 'authentication problems', 'things aren't working') but the entire body — file paths, image names, CLI (`ncl`), DB schemas — is hardcoded to the nanocoai/nanoclaw repo, so it only helps if that's the actual codebase.
Testovací report
Předložil jsem mu simulated '401 + container exits immediately' failure a it traced straight to the real cause via its own playbook — OneCLI selective secret mode — s the exact one-line fix (`onecli agents set-secret-mode --id <agent-id> --mode all`); a generic Docker-debugging pass has no way to know that command exists. The catch: every path, DB schema, a CLI name is specific to this one repo, so it's only useful if your project actually is NanoClaw.
Testováno: 2026-07-14 · Claude Code 2.x (agent harness)
Instalace
git clone https://github.com/nanocoai/nanoclaw cd nanoclaw mkdir -p ~/.claude/skills cp -r .claude/skills/debug ~/.claude/skills/debug
Příkazy a ukázkové prompty
/debugDiagnostikuje NanoClaw's containerized agent runtime via its two SQLite session DBs a logs.
Skilly se spouštějí běžnými požadavky — žádné příkazy k zapamatování. Po instalaci ho aktivují prompty jako tyto (anglicky):
Debug why my NanoClaw container exits immediatelyDiagnose the 401 error in my NanoClaw setupFix the OneCLI secret mode breaking my container