skills.rest
leonj1
leonj1COMMUNITY
Explore all skills by this author →
WebsiteGitHub

debug

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

Updated Feb 2, 2026
Search Tags:#devops#debugging#troubleshooting#logs#CLI#container#session
One-click install
npx skills add https://github.com/leonj1/nanoclaw --skill debug-leonj1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/leonj1/nanoclaw/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/leonj1/nanoclaw --skill debug-leonj1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers diagnose and fix issues in the NanoClaw container runtime.

Core Features & Use Cases

  • Guided debugging: Provides structured checks for logs, env vars, mounts, and session state to speed up resolution.
  • Operational best practices: Marry host and container perspectives to minimize downtime and confusion during failures.
  • Use Case: When the Claude Code process exits unexpectedly, apply the diagnostic steps to identify root causes and remediation paths.

Quick Start

Verify that authentication is configured and sessions mount correctly. Then run a quick diagnostic:

  • Ensure .env has CLAUDE_CODE_OAUTH_TOKEN or ANTHROPIC_API_KEY.
  • Create and verify data/env, data/ipc, and data/sessions mounts.
  • Inspect logs in logs/nanoclaw.log and container-specific logs under groups//logs/container-.log.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I troubleshoot a container runtime when the process exits unexpectedly?▼

Troubleshooting unexpected container exits requires inspecting logs in logs/nanoclaw.log and groups/*/logs/container-*.log. Apply a structured diagnostic workflow checking environment variables, mount configurations, and session state to identify the root cause.

Why does my container authentication fail during session startup?▼

Container authentication fails when the .env file lacks credentials. Ensure .env contains either CLAUDE_CODE_OAUTH_TOKEN or ANTHROPIC_API_KEY to resolve the authentication failure during startup.

How do I verify mount configurations for container sessions?▼

Verifying mount configurations requires creating and validating the data/env, data/ipc, and data/sessions mount paths. Ensuring these directories mount correctly is critical for reliable container session resumption.

What is the correct session path for resuming a container agent?▼

The correct session path for resuming a container agent is /home/node/.claude/. Diagnostic workflows enforce checks for this path to ensure session state is properly maintained and resumed.

Does the container runtime require a non-root user to function properly?▼

Yes, the container runtime requires a non-root user. The debugging workflow enforces checks to ensure the container user is non-root, minimizing downtime and aligning with operational best practices.

What is the best way to debug CLI container agent issues for reliability?▼

The best way to debug CLI container agent issues is combining host and container perspectives. Run structured diagnostics covering logs, environment variables, mounts, and session state to minimize confusion during failures.

Related Skills

Explore More Software Engineering Skills→
LIMITLESS-LONGEVITYLIMITLESS-LONGEVITY

use-native-credential-proxy

Replace the OneCLI gateway with a local .env-based credential proxy for container API requests.

Official
Intermediate
Arno37Arno37

debug

Diagnose container agent issues across local and CI deployments.

Community
Intermediate
0-CYBERDYNE-SYSTEMS-00-CYBERDYNE-SYSTEMS-0
3

debug

Diagnose container agent issues in FFT_nano via logs, env vars, mounts, and authentication.

Community
Advanced
heuuLZPheuuLZP
2

debug

Diagnoses NanoClaw container agent issues via logs, environment, and permissions.

Community
Advanced