debug

Diagnose NanoClaw container agent authentication, mount, and log failures.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps operators and developers quickly diagnose and resolve containerized agent failures in NanoClaw, including authentication errors, missing environment variables, incorrect mounts, permission issues, MCP server failures, and session resumption problems.

Core Features & Use Cases

  • Log discovery: Identifies where to find main app logs, container run logs, and Claude session histories to root-cause errors.
  • Environment and auth validation: Checks .env configuration, verifies authentication tokens, and confirms which variables are propagated into the container.
  • Mounts and permissions troubleshooting: Explains expected mount targets, ownership requirements for the node user, and how to validate readonly vs read-write mounts.
  • Session persistence and MCP checks: Guides verifying session mount paths, session continuity, and MCP server initialization failures.
  • Diagnostic workflows: Provides manual tests, interactive container checks, rebuild steps, and a quick diagnostic script to automate common checks.
  • Use case: Recover a failing agent that exits with code 1 by confirming auth tokens, verifying /home/node/.claude mounts, inspecting container stderr, and restarting the container image.

Quick Start

Run the debug guide to check authentication, mounts, container logs, and session resumption for the failing agent.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug NanoClaw container authentication and environment variable errors?

Debug NanoClaw container authentication by checking .env configuration, verifying authentication tokens, and confirming which environment variables propagate into the container. Validate HOME and session paths to resolve token errors.

Why does my NanoClaw agent container exit with code 1 during startup?

Agent containers exit with code 1 due to incorrect mount targets, MCP server initialization failures, or missing session persistence. Inspect container stderr, verify /home/node/.claude mounts, and validate node user ownership to root-cause the crash.

How do I find and read container logs to troubleshoot NanoClaw agent failures?

Find NanoClaw agent logs by locating main app logs, container run logs, and Claude session histories. Inspecting these sources root-causes configuration errors and identifies where containerized agent execution failed.

How do I validate Docker mounts and permissions for a NanoClaw agent container?

Validate Docker mounts by confirming expected mount targets and checking ownership requirements for the node user. Verify readonly versus read-write mounts to ensure the containerized agent has correct file access for session persistence.

What steps diagnose MCP server initialization failures in NanoClaw containers?

Diagnose MCP server initialization failures by inspecting container logs, verifying session mount paths, and checking session continuity. Run interactive container checks and execute the diagnostic script to automate common configuration validations.

When should I rebuild a NanoClaw container image to fix agent execution issues?

Rebuild the NanoClaw container image when auth tokens, environment variables, and mount configurations are verified correct but the agent still fails. Perform image inspection and rebuild steps to ensure configuration changes apply properly.