debug

Diagnose NanoClaw container agent failures using logs, session databases, and mount inspection.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill debug-rosedwayane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/.claude/skills/debug
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill debug-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a containerized NanoClaw agent stops replying, fails to spawn, or silently drops messages, there is no in-container log to inspect after exit. This Skill provides a systematic debugging workflow covering host logs, session databases, mounts, and authentication so you can pinpoint where the message flow broke. ## Core Features & Use Cases - Message flow tracing: Query inbound.db and outbound.db session databases to determine whether a message reached the container, whether the agent replied, and whether delivery succeeded. - Common issue playbooks: Step-by-step diagnosis for duplicate service instances, container exit failures, OneCLI authentication errors, MCP server failures, mount problems, and stale heartbeat detection. - Operational commands: Restart session containers, rebuild the agent image, clear sessions, and run a quick diagnostic script that checks Docker, the gateway, the central DB, and duplicate processes. - Use Case: Your Telegram bot suddenly stops replying. Use this Skill to discover a second stale NanoClaw service instance is racing the delivery poll and marking messages delivered without sending them, then stop the duplicate and restore replies. ## Quick Start Ask the agent to debug why the NanoClaw container is not replying to messages and have it check the host error log and session databases.

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 that produces no reply?

Check logs/nanoclaw.log for the container exit code and streamed stderr at debug level, then query the session's inbound.db and outbound.db. If messages_in has the message but messages_out is empty, the container died mid-run; check processing_ack and the heartbeat file mtime.

Why does NanoClaw log "No adapter for channel type" warnings?

This happens when two NanoClaw service instances run simultaneously and the stale one has no channel adapters registered. Its delivery poll marks messages delivered without sending them. Find duplicates with ps aux, then stop and disable the stale systemd service.

How do I enable debug logging in NanoClaw?

Set LOG_LEVEL=debug when running pnpm run dev, or add it to the launchd plist or systemd unit environment. Debug level shows full mount configurations, the container spawn command, and streamed container stderr lines.

Why does the NanoClaw agent get 401 authentication errors?

Secrets are injected per request by the OneCLI gateway, not via environment variables. A 401 usually means the agent is in selective secret mode and the secret was never assigned; run onecli agents list to check secretMode and set it to all if needed.

How do I restart a NanoClaw session container?

Run ncl groups restart --id <group-id> to restart all containers for an agent group. Add --rebuild to rebuild the image first after Dockerfile changes, or --message to wake the container immediately with a prompt.

Can I inspect what a NanoClaw container sees at runtime?

Yes, run docker run --rm -it --entrypoint /bin/bash nanoclaw-agent:latest for an interactive shell. Verify /workspace, /workspace/agent, /home/node/.claude, and /app mounts exist and are owned by the node user.