debug

Diagnose container agent issues in FFT_nano via logs, env vars, mounts, and authentication.

3|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/0-CYBERDYNE-SYSTEMS-0/FFT_nano --skill debug-0-cyberdyne-systems-0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/0-CYBERDYNE-SYSTEMS-0/FFT_nano/tree/main/.claude/skills/debug
Command: npx skills add https://github.com/0-CYBERDYNE-SYSTEMS-0/FFT_nano --skill debug-0-cyberdyne-systems-0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps diagnose and fix container agent issues in FFT_nano by guiding users to inspect logs, environment variables, mounts, and authentication problems.

Core Features & Use Cases

  • Centralized debugging guidance for the FFT_nano container workflow: logs, env vars, mounts, and session handling.
  • Provides best practices to diagnose authentication problems, container-spawn logs, and IPC/file-mount issues.
  • Use case: When the container fails to start, run the debug skill to locate the root cause and apply fixes.

Quick Start

Enable verbose debugging by setting LOG_LEVEL=debug and ensure that the Claude sessions are mounted at /home/node/.claude. Check host logs at logs/fft_nano.log and logs/fft_nano.error.log, then review container-run logs under groups/{group}/logs/container-*.log. Verify session continuity by looking for repeated "Session initialized" entries across messages.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I debug FFT_nano container issues when the agent fails to start?

To debug FFT_nano container issues, set LOG_LEVEL=debug and check host logs at logs/fft_nano.log and logs/fft_nano.error.log, then review container-run logs under groups/{group}/logs/container-*.log to locate the root cause and apply fixes.

Why does my Claude Code session lose continuity inside a containerized workflow?

Claude Code session continuity drops when sessions are not properly mounted. Ensure you mount sessions at /home/node/.claude and verify continuity by checking for repeated "Session initialized" entries across messages.

What environment variables and mounts do I need to check for FFT_nano authentication problems?

For FFT_nano authentication problems, inspect environment variables and file mounts. Verify IPC/file-mount scenarios across multiple groups and ensure proper session mounting to /home/node/.claude for reliable resumption.

What is the best way to troubleshoot container agent issues with environment variables and logs?

The best way to troubleshoot container agent issues is centralized debugging: enable verbose logging with LOG_LEVEL=debug, inspect environment variables, verify mounts, and trace container-spawn logs to diagnose authentication failures.

How do I verify IPC and file-mount scenarios are working across multiple groups in FFT_nano?

Verify IPC and file-mount scenarios by checking container-run logs under groups/{group}/logs/container-*.log for errors, and ensure session mounting to /home/node/.claude is properly configured for reliable resumption across multiple groups.