Install the "debug" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/debug into .claude/skills/debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add sbusso/claudeclaw --skill debug -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "debug" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/debug into .agents/skills/debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add sbusso/claudeclaw --skill debug -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "debug" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/debug into .cursor/skills/debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add sbusso/claudeclaw --skill debug -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "debug" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/debug into .gemini/skills/debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
GitHub CLI
$ gh skill install sbusso/claudeclaw debug
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add sbusso/claudeclaw --skill debug -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "debug" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/debug into .github/skills/debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add sbusso/claudeclaw --skill debug -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "debug" agent skill from https://github.com/sbusso/claudeclaw/tree/main/skills/debug into .opencode/skills/debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
debug
GitHub stars
194
Used in
1 other repo
Token cost
~3.3k tokens
SKILL.md length
667 words
Files
1
Skills in repo
23
Repo updated
First seen
Licence
MIT
At a glance
Debug container agent issues. An agent skill from sbusso/claudeclaw.
Works in 6 steps: "Claude Code process exited with code 1" → Environment Variables Not Passing → Mount Issues → …
Things arent working
SKILL.md covers Architecture Overview, Log Locations, Enabling Debug Logging and Common Issues, plus 8 more sections
Calls docker, npm and claude; needs CLAUDE_CODE_OAUTH_TOKEN and ANTHROPIC_API_KEY
What it does
Debug is an agent skill from sbusso/claudeclaw. Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. Covers logs, environment variables, mounts, and common issues.
Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Secrets management, Debugging and Authentication. The repository describes itself as: Use Claude to orchestrate agents like OpenClaw. The licence is MIT.
When your agent uses it
Things arent working
Container fails
Authentication problems
Understand how the container system works
Example prompts
“/debug”
Requirements
Node.js
Docker
A credential in CLAUDE_CODE_OAUTH_TOKEN
A credential in ANTHROPIC_API_KEY
Workflow steps
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 1395af4. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
docker
npm
claude
sqlite3
node
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use docker, npm and npx, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
CLAUDE_CODE_OAUTH_TOKEN
ANTHROPIC_API_KEY
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Debug loads about 3.3k tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 667 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~55
When it runs· the whole SKILL.md, loaded when a task matches
~3.3k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
NoteMentions a .env fileSKILL.md:70
**Fix:** Ensure `.env` file exists with either OAuth token or API key:
NoteMentions a .env fileSKILL.md:72
cat .env # Should show one of:
NoteMentions a .env fileSKILL.md:87
OAUTH_TOKEN`, `ANTHROPIC_API_KEY`) from `.env` and mounts them for sourcing inside the container. Other env vars are not
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/debug/SKILL.md (or your agent's skills folder).
name
debug
description
Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. Covers logs, environment variables, mounts, and common issues.
ClaudeClaw Container & Sandbox Debugging
This guide covers debugging the agent execution system (container and sandbox runtimes).
Important: The container runs as user node with HOME=/home/node. Session files must be mounted to /home/node/.claude/ (not /root/.claude/) for session resumption to work.
Log Locations
Log
Location
Content
Main app logs
logs/claudeclaw.log
Host-side WhatsApp, routing, container spawning
Main app errors
logs/claudeclaw.error.log
Host-side errors
Container run logs
groups/{folder}/logs/container-*.log
Per-run: input, mounts, stderr, stdout
Claude sessions
~/.claude/projects/
Claude Code session history
Enabling Debug Logging
Set LOG_LEVEL=debug for verbose output:
bash
# For development
LOG_LEVEL=debug npm run dev
# For launchd service (macOS), add to plist EnvironmentVariables:
<key>LOG_LEVEL</key>
<string>debug</string>
# For systemd service (Linux), add to unit [Service] section:
# Environment=LOG_LEVEL=debug
Debug level shows:
Full mount configurations
Container command arguments
Real-time container stderr
Common Issues
1. "Claude Code process exited with code 1"
Check the container log file in groups/{folder}/logs/container-*.log
Common causes:
Missing Authentication
Invalid API key · Please run /login
Fix: Ensure .env file exists with either OAuth token or API key:
bash
cat .env # Should show one of:
# CLAUDE_CODE_OAUTH_TOKEN=sk-ant-oat01-... (subscription)
# ANTHROPIC_API_KEY=sk-ant-api03-... (pay-per-use)
Root User Restriction
--dangerously-skip-permissions cannot be used with root/sudo privileges
Fix: Container must run as non-root user. Check Dockerfile has USER node.
2. Environment Variables Not Passing
Runtime note: Environment variables passed via -e may be lost when using -i (interactive/piped stdin).
Workaround: The system extracts only authentication variables (CLAUDE_CODE_OAUTH_TOKEN, ANTHROPIC_API_KEY) from .env and mounts them for sourcing inside the container. Other env vars are not exposed.
Important:allowDangerouslySkipPermissions: true is required when using permissionMode: 'bypassPermissions'. Without it, Claude Code exits with code 1.
Rebuilding After Changes
bash
# Rebuild main app
npm run build
# Rebuild container (use --no-cache for clean rebuild)
./src/runtimes/docker/build.sh
# Or force full rebuild
docker builder prune -af
./src/runtimes/docker/build.sh
Checking Container Image
bash
# List images
docker images
# Check what's in the image
docker run --rm --entrypoint /bin/bash claudeclaw-agent:latest -c '
echo "=== Node version ==="
node --version
echo "=== Claude Code version ==="
claude --version
echo "=== Installed packages ==="
ls /app/node_modules/
'
Show full SKILL.md (283 more words)Show less
Session Persistence
Claude sessions are stored per-group in data/sessions/{group}/.claude/ for security isolation. Each group has its own session directory, preventing cross-group access to conversation history.
Critical: The mount path must match the container user's HOME directory:
Container user: node
Container HOME: /home/node
Mount target: /home/node/.claude/ (NOT /root/.claude/)
To clear sessions:
bash
# Clear all sessions for all groups
rm -rf data/sessions/
# Clear sessions for a specific group
rm -rf data/sessions/{groupFolder}/.claude/
# Also clear the session ID from ClaudeClaw's tracking (stored in SQLite)
sqlite3 store/messages.db "DELETE FROM sessions WHERE group_folder = '{groupFolder}'"
To verify session resumption is working, check the logs for the same session ID across messages:
bash
grep "Session initialized" logs/claudeclaw.log | tail -5
# Should show the SAME session ID for consecutive messages in the same group
IPC Debugging
The container communicates back to the host via files in /workspace/ipc/:
bash
# Check pending messages
ls -la data/ipc/messages/
# Check pending task operations
ls -la data/ipc/tasks/
# Read a specific IPC file
cat data/ipc/messages/*.json
# Check available groups (main channel only)
cat data/ipc/main/available_groups.json
# Check current tasks snapshot
cat data/ipc/{groupFolder}/current_tasks.json
EPERM on all operations: The srt settings JSON file requires ALL fields including empty arrays (allowRead: []). Omit any field and the entire settings file silently fails validation — zero error messages.
Agent runner won't start (tsx/EPERM): Sandbox blocks Unix sockets needed by tsx. Fix: pre-compile with cd agent/runner && npx tsc, run with plain node.
Agent can't find paths: Check that CLAUDECLAW_*_DIR env vars are set in sandbox-runner.ts. The agent runner falls back to /workspace/* if env vars are missing.
Stale sessions after runtime switch: Switching a group between container and sandbox leaves stale session IDs. Fix: sqlite3 store/messages.db "DELETE FROM sessions"
Network blocked: Verify allowedDomains in the generated settings file includes api.anthropic.com. Check data/sandbox-settings/ for the last generated settings file.
Credential issues: Sandbox passes real credentials via env vars (not through the credential proxy). Ensure ANTHROPIC_API_KEY or CLAUDE_CODE_OAUTH_TOKEN is in .env.
Quick Diagnostic Script
Run this to check common issues:
bash
echo "=== Checking ClaudeClaw Agent Setup ==="
echo -e "\n1. Authentication configured?"
[ -f .env ] && (grep -q "CLAUDE_CODE_OAUTH_TOKEN=sk-" .env || grep -q "ANTHROPIC_API_KEY=sk-" .env) && echo "OK" || echo "MISSING - add CLAUDE_CODE_OAUTH_TOKEN or ANTHROPIC_API_KEY to .env"
echo -e "\n2. Env file copied for container?"
[ -f data/env/env ] && echo "OK" || echo "MISSING - will be created on first run"
echo -e "\n3. Container runtime running?"
docker info &>/dev/null && echo "OK" || echo "NOT RUNNING - start Docker Desktop (macOS) or sudo systemctl start docker (Linux)"
echo -e "\n4. Container image exists?"
echo '{}' | docker run -i --entrypoint /bin/echo claudeclaw-agent:latest "OK" 2>/dev/null || echo "MISSING - run ./src/runtimes/docker/build.sh"
echo -e "\n5. Session mount path correct?"
grep -q "/home/node/.claude" src/orchestrator/container-runner.ts 2>/dev/null && echo "OK" || echo "WRONG - should mount to /home/node/.claude/, not /root/.claude/"
echo -e "\n6. Groups directory?"
ls -la groups/ 2>/dev/null || echo "MISSING - run setup"
echo -e "\n7. Recent container logs?"
ls -t groups/*/logs/container-*.log 2>/dev/null | head -3 || echo "No container logs yet"
echo -e "\n8. Session continuity working?"
SESSIONS=$(grep "Session initialized" logs/claudeclaw.log 2>/dev/null | tail -5 | awk '{print $NF}' | sort -u | wc -l)
[ "$SESSIONS" -le 2 ] && echo "OK (recent sessions reusing IDs)" || echo "CHECK - multiple different session IDs, may indicate resumption issues"
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sbusso/claudeclaw, which our catalogue first saw on October 7, 2026.
Debug next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Covers Daytona CLI setup, sandbox debugging, keeping a sandbox alive and which credentials the CLI uses, for when Daytona itself is the problem rather than the tests.
Debug container agent issues. An agent skill from sbusso/claudeclaw. Debug is an agent skill from sbusso/claudeclaw. Debug container agent issues.
When should I use Debug?
Debug fits situations like: things arent working; container fails; authentication problems; understand how the container system works.
How do I install Debug in Claude Code?
Run `npx skills add sbusso/claudeclaw --skill debug -a claude-code`. Or copy the skill folder (skills/debug in sbusso/claudeclaw) into .claude/skills/debug in your project. Claude Code loads it when a task matches its description.
How do I install Debug in Codex?
Run `npx skills add sbusso/claudeclaw --skill debug -a codex`. Or copy the skill folder (skills/debug in sbusso/claudeclaw) into .agents/skills/debug in your project. Codex loads it when a task matches its description.
Can I use Debug in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sbusso/claudeclaw --skill debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debug, .gemini/skills/debug, .github/skills/debug and .opencode/skills/debug in your project.
What does Debug need to run?
Going by SKILL.md and its folder, Debug needs the command-line tools its instructions call (docker, npm, claude, sqlite3, node and npx) and credentials named CLAUDE_CODE_OAUTH_TOKEN and ANTHROPIC_API_KEY. Our summary lists: Node.js; Docker; A credential in CLAUDE_CODE_OAUTH_TOKEN; A credential in ANTHROPIC_API_KEY.
Does Debug access the network?
SKILL.md contains no URLs. Its commands use docker, npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Debug safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file; runs commands with sudo), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Debug use?
Debug is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Debug use?
About 3.3k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Debug?
Skills that share tags, products or a category with Debug: Scanning For Hardcoded Secrets (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Daytona Sandbox Operations (different-ai/openwork, 24k stars), Using Medusa Cloud (medusajs/medusa-agent-skills, 227 stars) and Common Security Standards (HoangNguyen0403/agent-skills-standard, 571 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Debug?
sbusso (a GitHub user) maintains it in sbusso/claudeclaw, which has 194 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on August 12, 2026.
Source: sbusso/claudeclaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.