skills.rest
Runchuan-BU
Runchuan-BUCOMMUNITY
Explore all skills by this author →
GitHub

debug

Diagnose containerized BioClaw agent execution issues by analyzing logs, mounts, and environment variables.

401|53|Updated Feb 26, 2026
Search Tags:#devops#authentication#logs#claude#debug#containers#mounts
One-click install
npx skills add https://github.com/Runchuan-BU/BioClaw --skill debug-runchuan-bu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/Runchuan-BU/BioClaw/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/Runchuan-BU/BioClaw --skill debug-runchuan-bu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and operators quickly identify and resolve failures in the containerized BioClaw agent runtime, including authentication errors, session resumption failures, mount and permission issues, and MCP or SDK startup problems. It centralizes guidance on where to find logs, how environment variables are passed into containers, and the expected mount and ownership layout for reliable session persistence.

Core Features & Use Cases

  • Log location mapping and guidance for host-side and per-run container logs, including bioclaw.log and groups/{folder}/logs/container-*.log.
  • Authentication and environment validation for CLAUDE_CODE_OAUTH_TOKEN and ANTHROPIC_API_KEY and verification methods to ensure credentials reach the container.
  • Mount and permission diagnostics focused on the container user node, expected HOME path /home/node/.claude for sessions, workspace mounts, and Apple Container mount quirks.
  • Troubleshooting steps for MCP server failures, Claude Code exit codes, session resumption checks, IPC file inspection, and rebuild/test workflows.
  • Use case: when the agent exits with code 1 during session resumption, follow the sequence of checking env files, mount targets, container ownership, and container logs to restore service.

Quick Start

Run the quick diagnostic script to check authentication, env propagation, mount targets, container image availability, and session continuity.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug a containerized agent that exits with code 1 during session resumption?▼

To debug container agent exit code 1 during session resumption, sequentially check environment files, verify mount targets, inspect container file ownership, and review container logs to restore service.

Where do I find container logs for troubleshooting BioClaw agent runtime failures?▼

Container logs for troubleshooting BioClaw agent runtime failures are located in host-side bioclaw.log and per-run container logs at groups/{folder}/logs/container-*.log.

How do I validate authentication environment variables passed into a container?▼

Validate container authentication by checking that CLAUDE_CODE_OAUTH_TOKEN and ANTHROPIC_API_KEY environment variables are correctly passed into the container and verifying credential propagation.

Why does my Claude Agent SDK session fail to resume inside an Apple Container?▼

Claude Agent SDK session resumption fails inside an Apple Container due to incorrect mount targets, improper file ownership for the container user node, or missing session data at the expected HOME path /home/node/.claude.

What do I need to inspect when an MCP server fails to start in a containerized environment?▼

When an MCP server fails to start in a containerized environment, inspect IPC files, verify environment variable propagation, check container-runner.ts configuration, and review startup logs.

Can I run a quick diagnostic script to check container agent mounts and authentication?▼

Yes, you can run a quick diagnostic script to check authentication, environment variable propagation, mount targets, container image availability, and session continuity for the agent runtime.

Related Skills

Explore More Software Engineering Skills→
jboothomasjboothomas
1

debug

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

Community
Advanced
LIMITLESS-LONGEVITYLIMITLESS-LONGEVITY

debug

Diagnose NanoClaw container failures involving mounts, environment variables, and MCP initialization.

Official
Advanced
erguotou520erguotou520

debug

Diagnose NanoClaw containerized agent execution failures via logs and mounts.

Community
Intermediate
DingyangLyuDingyangLyu
85

debug

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

Community
Advanced