debug

Diagnose containerized AI agent issues via log analysis and configuration verification.

19|4|Updated Feb 24, 2026

Search Tags:#debugging #troubleshooting #logs #agent #docker #container

Ready to run

npx skills add https://github.com/lorenzovenice/nanoclaw-venice --skill debug-lorenzovenice

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/lorenzovenice/nanoclaw-venice/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/lorenzovenice/nanoclaw-venice --skill debug-lorenzovenice

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose and resolve problems with the containerized agent execution system, including container failures, authentication errors, and understanding system architecture.

Core Features & Use Cases

Log Analysis: Pinpoints locations for main app logs, container run logs, and session logs.
Configuration Verification: Guides users on checking environment variables, mount points, and permissions within the container.
Common Issue Resolution: Provides specific fixes for common errors like "Claude Code process exited with code 1" and session resumption failures.
Use Case: If your agent is not responding and you suspect a configuration issue, use this Skill to systematically check logs, environment variables, and mount paths to identify the root cause.

Quick Start

Run the quick diagnostic script to check for common issues with your container setup.

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 AI agent that is not responding?▼

To debug a containerized AI agent, systematically check the main app logs, container run logs, and session logs to pinpoint the root cause. Verify environment variables, mount points, and permissions within the container configuration.

Why does my container agent fail with an exit code 1 error?▼

A container agent exits with code 1 due to configuration issues or authentication errors. Use troubleshooting procedures to verify environment variable passing, check mount paths, and resolve common process failures.

Where can I find the logs for troubleshooting Docker container agent issues?▼

Logs for Docker container agent troubleshooting are located in three main areas: main application logs, container run logs, and session logs. Analyzing these log files reveals authentication failures and configuration errors.

How do I fix session resumption failures in a containerized agent environment?▼

Fix session resumption failures by verifying container configurations and checking session logs for specific errors. Troubleshooting includes validating environment variables and reviewing manual testing procedures to restore agent sessions.

What is the best way to troubleshoot MCP server failures in a Docker container?▼

The best way to troubleshoot MCP server failures involves checking container logs and verifying SDK options. Diagnose configuration issues, environment variable passing, and mount problems to resolve server failures.

Can I use this troubleshooting approach for container permission and mount errors?▼

Yes, this troubleshooting approach resolves container permission and mount errors by guiding configuration verification. It systematically checks mount paths, environment variables, and permission settings to identify and fix common agent issues.