debug

Name: debug
Availability: InStock
Author: gavrielc

Diagnose NanoClaw container issues via logs, env vars, and mounts.

30.5k|12.9k|Updated Jan 31, 2026

Search Tags:#logs #debug #diagnostics #container #environment-variables #session-persistence #mounts

Ready to run

npx skills add https://github.com/gavrielc/nanoclaw --skill debug-gavrielc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/gavrielc/nanoclaw/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/gavrielc/nanoclaw --skill debug-gavrielc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers quickly diagnose and fix issues in the NanoClaw container agent by providing structured debugging guidance, best practices, and actionable checklists.

Core Features & Use Cases

Centralized debugging guidance for logs, env vars, mounts, and session handling.
Step-by-step troubleshooting workflows for common container startup and authentication problems.
Quick-reference diagnostics that map host/container behaviors to actionable fixes.

Quick Start

Follow these steps to begin diagnosing issues:

Inspect container logs at logs/nanoclaw.log and per-run logs under groups/{group}/logs/container-*.log.
Verify environment variables are present in data/env/env and mounted to /workspace/env-dir/env inside the container.
Confirm session persistence paths and ensure mounts point to /home/node/.claude/ for Claude sessions.
Run the quick diagnostic checks to validate setup and identify root causes.

Frequently Asked Questions about debug

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

FAQPage Schema

How do I debug container agent startup and authentication failures?▼

Debug container agent failures by inspecting NanoClaw logs at logs/nanoclaw.log and per-run logs under groups/{group}/logs/container-*.log to trace startup and authentication errors. Follow structured troubleshooting workflows to map behaviors to actionable fixes.

Why are my environment variables missing inside the container?▼

Missing environment variables occur when variables are not present in data/env/env or mounted to /workspace/env-dir/env inside the container. Verify environment variables are correctly configured and mounted to resolve session handling issues.

What's the best way to diagnose container session persistence and mount issues?▼

Diagnose container session persistence by confirming mounts point to /home/node/.claude/ for Claude sessions. Verify session persistence paths and mount configurations to ensure the container agent maintains state across runs.

Does this debugging guidance work with Apple Container and Claude Agent SDK?▼

Debugging guidance covers session handling and diagnostics across both Apple Container and Claude Agent SDK contexts. It provides documented paths and configuration checks to help engineers resolve failures quickly in these environments.

What are common container agent issues with mounts and session handling?▼

Common container agent issues include misconfigured mounts pointing away from /home/node/.claude/, missing session persistence paths, and environment variables not mounted to /workspace/env-dir/env. Run quick diagnostic checks to validate setup and identify root causes.