debug

Diagnose containerized NanoClaw Claude Code runtime failures via mounts, env files, and logs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/hellosimplerick/nanoclaw-smoke --skill debug-hellosimplerick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/hellosimplerick/nanoclaw-smoke/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/hellosimplerick/nanoclaw-smoke --skill debug-hellosimplerick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides focused diagnostics and remediation steps for containerized NanoClaw Claude agents that fail to start, lose session state, or exhibit authentication and mount-related errors, enabling faster resolution of runtime failures.

Core Features & Use Cases

  • Log and session inspection: Locate and interpret host and per-run container logs to identify authentication failures, MCP errors, and session initialization problems.
  • Mounts and permissions checks: Verify environment file mounting, session directory targets, and container user ownership to resolve broken session resumption and permission-denied errors.
  • Rebuild and runtime tests: Rebuild the container image, run isolated test queries, and use a quick diagnostic script to validate authentication tokens, container status, and IPC file visibility.
  • Use Case: When a Claude Code process exits with code 1 or creates new session IDs every run, use these checks to find whether the issue is missing auth tokens, incorrect .claude mount path, or MCP startup failures.

Quick Start

Check the container logs, verify that .env is mounted and contains authentication tokens, confirm /home/node/.claude is mounted for sessions, and run the quick diagnostic script to identify the failing component.

Frequently Asked Questions about debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Claude Code container exit with code 1 and create new session IDs every run?

Claude Code container exits with code 1 when session state is lost due to missing auth tokens, incorrect .claude mount paths, or permission-denied errors on mounted session directories. Verify .env mounts and container user ownership to resolve it.

How do I debug NanoClaw container agent failures and MCP startup errors?

Debug NanoClaw agent failures by inspecting host and per-run container logs for MCP errors, verifying environment variables, and running a diagnostic script to validate auth tokens, container status, and IPC file visibility.

How do I verify Docker mounts and permissions for Claude Code session directories?

Verify Docker mounts by confirming .env is mounted with auth tokens, checking /home/node/.claude is mounted for sessions, and validating container user ownership to resolve broken session resumption and permission-denied errors.

Can I test containerized agent authentication tokens without a full production deployment?

Test authentication tokens in local development by rebuilding the container image, running isolated test queries, and executing a quick diagnostic script to validate tokens, container status, and IPC file visibility.

What causes WhatsApp agent flow IPC failures in spawned Docker containers?

WhatsApp agent flow IPC failures occur when inter-process communication files are not visible inside spawned Docker containers. Run the diagnostic script to check IPC file visibility, container status, and environment configuration.