skills.rest
erguotou520
erguotou520COMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug

Diagnose NanoClaw containerized agent execution failures via logs and mounts.

Updated Mar 10, 2026
Search Tags:#debugging#authentication#logs#containers#sessions#mounts
One-click install
npx skills add https://github.com/erguotou520/myclaw --skill debug-erguotou520
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/erguotou520/myclaw/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/erguotou520/myclaw --skill debug-erguotou520

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you diagnose why NanoClaw's containerized agent system is failing, from authentication and mount problems to session-resumption bugs and MCP server crashes.

Core Features & Use Cases

  • Log-driven troubleshooting: Find the right host, container, and session logs quickly.
  • Environment and mount checks: Verify authentication variables, workspace mounts, and file ownership inside the container.
  • Session persistence debugging: Confirm Claude session state is stored in the correct HOME path for per-group isolation.
  • Manual validation: Run targeted container commands to reproduce issues and isolate failures.
  • Use case: When Claude Code exits with code 1, use this Skill to trace the problem from the logs to the container setup and apply the correct fix.

Quick Start

Ask me to debug a NanoClaw container issue and I will inspect the likely failure point, check logs and mounts, and suggest the next fix.

Frequently Asked Questions about debug

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

FAQPage Schema
Why does Claude Code exit with code 1 in a NanoClaw container?▼

Claude Code exits with code 1 in NanoClaw when containerized agent execution fails due to authentication errors, mount misconfigurations, permission problems, or MCP server startup failures. Inspecting host logs and per-group container logs traces the specific failure point.

How do I debug NanoClaw container authentication and mount issues?▼

Debug NanoClaw container authentication and mount issues by verifying environment variables, checking workspace mount paths, and confirming file ownership inside the container. Run targeted container commands to reproduce issues and isolate failures across host and per-group container logs.

How do I fix NanoClaw session resumption bugs in per-group containers?▼

Fix NanoClaw session resumption bugs by confirming Claude session state is stored in the correct HOME path for per-group isolation. Verifying the HOME-based session storage ensures reliable container debugging and proper per-group session persistence.

What logs do I need to check to diagnose NanoClaw container failures?▼

Check host logs and per-group container logs to diagnose NanoClaw container failures. Log-driven troubleshooting helps find the right session logs, verify environment variables, inspect IPC file flow, and check non-root execution conditions for reliable container debugging.

Do I need non-root execution to run NanoClaw containerized agents?▼

Non-root execution is required to run NanoClaw containerized agents reliably. Verifying non-root execution conditions along with environment variables, workspace paths, and IPC file flow ensures the containerized agent execution system functions correctly.

NanoClaw container MCP server startup is failing, what should I check?▼

When NanoClaw container MCP server startup fails, check the host logs and per-group container logs for startup errors. Verifying environment variables, workspace mounts, and IPC file flow helps isolate the MCP server startup failure for reliable container debugging.

Related Skills

Explore More Software Engineering Skills→
zhaosj0315zhaosj0315

debug

Diagnose and fix containerized NanoClaw agent issues via logs and environment checks.

Community
Advanced
DingyangLyuDingyangLyu
85

debug

Diagnoses Docker/AJSHA client container and agent-run failures including authentication, mounts, permissions, sessions, and MCP/SDK errors.

Community
Advanced
theowenyoungtheowenyoung

debug

Inspect logs, env configuration, mounts, and session handling to debug NanoClaw container agent issues.

Community
Intermediate
wientjeswientjes

debug

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

Community
Advanced