debug

Diagnose NanoClaw container agent issues by inspecting logs, environment variables, and mounts.

7|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/gunabot/nanoclaw --skill debug-gunabot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/gunabot/nanoclaw/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/gunabot/nanoclaw --skill debug-gunabot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging a malfunctioning NanoClaw container agent can be time-consuming and error-prone. This Skill provides a concise, repeatable workflow to identify misconfigurations and runtime issues that prevent the agent from starting, running, or resuming sessions.

Core Features & Use Cases

  • Guided debugging workflow: Clear steps to inspect logs, environment variables, mounts, and session persistence.
  • Diagnostics references: Point-in-time locations for logs, IPC artifacts, and mount checks to rapidly locate root causes.
  • Use Case: When the agent fails to start or cannot resume a previous session, follow the guide to verify the .env, volumes, and home directory settings.

Quick Start

Use this skill to diagnose container agent issues by inspecting logs at logs/nanoclaw.log, verifying environment setup in data/env/env, checking mounts in /workspace, and confirming session persistence under /home/node/.claude/.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug a NanoClaw container agent that fails to start?▼

To debug a NanoClaw container agent startup failure, inspect the logs at logs/nanoclaw.log, verify environment setup in data/env/env, and check mounts in /workspace to identify misconfigurations or runtime issues preventing initialization.

Why does my container agent fail to resume previous sessions?▼

Container agent session resume failures often stem from incorrect persistence settings. Verify that session persistence under /home/node/.claude/ is properly configured and that volume mounts are correctly attached to access previous session data.

What is the best way to check container agent environment variables and mounts?▼

The best way to check container agent environment variables and mounts is to verify the .env file in data/env/env and inspect volume mounts in /workspace to ensure authentication credentials and directory paths are correctly configured.

Where are NanoClaw container logs and IPC artifacts located for troubleshooting?▼

NanoClaw container logs and IPC artifacts for troubleshooting are located at logs/nanoclaw.log and within session directories under /home/node/.claude/, providing point-in-time diagnostics to rapidly locate root causes.

Can I use this debugging workflow for general container configuration issues?▼

Yes, this debugging workflow covers general container configuration issues including authentication problems, environment variable misconfigurations, and mount failures, providing concrete steps and checks to resolve common runtime problems.

What should I check when container agent authentication stops working?▼

When container agent authentication stops working, check the environment setup in data/env/env for correct credentials, verify the .env file configurations, and inspect logs/nanoclaw.log for authentication-related error messages.