debug

Diagnose NauggieClaw container failures by analyzing logs, mounts, and MCP errors.

1|2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/jboothomas/nauggieclaw --skill debug-jboothomas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/jboothomas/nauggieclaw/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/jboothomas/nauggieclaw --skill debug-jboothomas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Containerized Auggie agents can fail silently when mounts, authentication, or MCP servers are misconfigured, leaving NauggieClaw unable to process messages or resume sessions. This skill guides you through the logs, environment variables, mounts, permissions, and session persistence rules so you can restore reliable agent runs.

Core Features & Use Cases

  • Step through the host and container logs to see why container runs exit, checking authentication errors, permission denials, and MCP failures.
  • Confirm that environment variables and session directories mount into the node user home, and that Docker sees the proper volumes for groups, IPC, and projects.
  • Use the quick diagnostic checks to validate authentication files, ensure the container runtime is running, observe recent container logs, and verify session ID reuse for each group.

Quick Start

Ask the debug skill to inspect the failing container logs, authenticate environment mounts, and session directories for the current NauggieClaw run.

Frequently Asked Questions about debug

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

FAQPage Schema
Why does my NauggieClaw container exit silently during setup?

NauggieClaw container runs fail when environment variables and session directories do not mount into the node user home directory. Verify that Docker sees the proper volumes for groups, IPC, and projects so the Auggie agent can access the required authentication files.

How do I debug authentication failures in a Docker-based Auggie agent?

Debug authentication failures by accessing the logs/nauggieclaw.log file and the session directory to verify authentication tokens. Confirm that environment variables mount correctly into the node user home and check that the container runtime is actively running.

How do I fix session persistence errors in NauggieClaw containers?

Fix session persistence errors by verifying session ID reuse for each group and checking the group folder logs. Ensure that Docker volumes for the session directory and group mounts are properly configured so the Auggie agent can resume sessions.

What files do I need to diagnose NauggieClaw container issues?

Diagnosing NauggieClaw container issues requires access to logs/nauggieclaw.log, group folder logs, env mounts, container-runner.ts configuration, and the session directory. These files verify authentication tokens, home mount targets, and MCP error reports.

Does NauggieClaw container debugging require checking MCP error reports?

Yes, NauggieClaw container debugging requires checking MCP error reports alongside host and container logs. Misconfigured MCP servers cause containerized Auggie agents to fail silently, preventing reliable message processing and session resumption.