debug

Name: debug
Author: 0-CYBERDYNE-SYSTEMS-0

DevOps Community

Repo stars 0
Author updated Live
Author repo nano-core

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: DevOps
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 88 / 100 · community maintained
Author / version / license: @0-CYBERDYNE-SYSTEMS-0 · no license declared
Token usage: Lean
Setup complexity: Manual integration
External API key: Required · Anthropic
Operating systems: Docker
Runtime requirements: Node.js · Docker
Permissions: Read-only
Shell exec
Env read
Write / modify
Network behavior: External requests
Install commands: 26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview debug-0-cyberdyne-systems-0.preview

---
name: debug
description: Debug nano-core agent runtime issues (Docker default, host opt-in). Use when agent execution fai…
category: devops
runtime: Node.js / Docker
---

# debug output preview

## PART A: Task fit
- Use case: Debug nano-core agent runtime issues (Docker default, host opt-in). Use when agent execution fails, runtime checks fail, or onboarding/startup is blocked. This guide covers host-side diagnosis for current runtime modes: requires Anthropic API key; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Runtime Architecture / Key Log Locations / Quick Health Checks” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Debug nano-core agent runtime issues (Docker default, host opt-in). Use when agent execution fails, runtime checks fail, or onboarding/startup is blocked. This guide covers host-side diagnosis for current runtime modes: requires Anthropic API key; runs on Node.js. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Runtime Architecture / Key Log Locations / Quick Health Checks” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, run shell commands, read environment variables, write/modify files; may access external network resources; requires Anthropic API keys.

## Running Rules
- read files, run shell commands, read environment variables, write/modify files; may access external network resources; requires Anthropic API keys.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: debug
description: Debug nano-core agent runtime issues (Docker default, host opt-in). Use when agent execution fai…
category: devops
source: 0-CYBERDYNE-SYSTEMS-0/nano-core
---

# debug

## When to use
- Debug nano-core agent runtime issues (Docker default, host opt-in). Use when agent execution fails, runtime checks fai…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “Runtime Architecture / Key Log Locations / Quick Health Checks” and keep inference separate from source facts.
- read files, run shell commands, read environment variables, write/modify files; may access external network resources; requires Anthropic API keys.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "debug" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Runtime Architecture / Key Log Locations / Quick Health Checks
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> Node.js / Docker | read files, run shell commands, read environment variables, write/modify files | may access external network resources
  guardrails -> requires Anthropic API keys + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Debug nano-core agent runtime issues (Docker default, host opt-in). Use when agent execution fails, runtime checks fail, or onbo…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Runtime Architecture”, “Key Log Locations”, “Quick Health Checks”, “1) App build/runtime sanity”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name debug directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Runtime Architecture / Key Log Locations / Quick Health Checks” before expanding.

Boundaries And Review

Dependencies: Prepare Anthropic API keys before running a full task.
Permissions: Declared permissions include read / shell-exec / env-read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

nano-core Runtime Debugging

This guide covers host-side diagnosis for current runtime modes:

Docker (default)
Host runtime (advanced, explicit opt-in)

Runtime Architecture

Host process (src/index.ts)
  -> runtime selection (src/container-runtime.ts)
  -> agent execution (src/container-runner.ts)
     - Docker mode: docker run nano-core-agent:latest
     - Host mode: node container/agent-runner/dist/index.js

Key Log Locations

Log	Location	Purpose
App log	`logs/nano-core.log`	Router, scheduler, runtime orchestration
App error log	`logs/nano-core.error.log`	Host process failures
Runtime run log	`groups/<folder>/logs/runtime-*.log`	Per-run stdout/stderr, mounts, env diagnostics

Quick Health Checks

1) App build/runtime sanity

npm run typecheck
npm run build

2) Runtime mode resolution

node -e "import('./dist/container-runtime.js').then(m=>console.log(m.getContainerRuntime()))"

3) Docker availability (default)

docker --version
docker info >/dev/null && echo "Docker OK" || echo "Docker NOT running"

4) Host mode gating (advanced)

grep -E '^(CONTAINER_RUNTIME|FFT_NANO_ALLOW_HOST_RUNTIME|FFT_NANO_ALLOW_HOST_RUNTIME_IN_PROD)=' .env || true

Host mode requires:

CONTAINER_RUNTIME=host
FFT_NANO_ALLOW_HOST_RUNTIME=1

Production host mode additionally requires:

FFT_NANO_ALLOW_HOST_RUNTIME_IN_PROD=1

Common Failure Modes

"Invalid CONTAINER_RUNTIME"

Cause: .env contains an unsupported value.

Fix:

sed -i.bak 's/^CONTAINER_RUNTIME=.*/CONTAINER_RUNTIME=auto/' .env

"No supported runtime found"

Cause: Docker unavailable and host mode not explicitly allowed.

Fix options:

Start Docker Desktop / Docker daemon.
Or explicitly enable host mode in .env:

CONTAINER_RUNTIME=host
FFT_NANO_ALLOW_HOST_RUNTIME=1

Runtime exits with code 1

Check newest runtime log:

ls -t groups/*/logs/runtime-*.log | head -1 | xargs -I{} sh -lc 'echo "== {} =="; tail -120 "{}"'

Then validate credentials:

grep -E '^(CLAUDE_CODE_OAUTH_TOKEN|ANTHROPIC_API_KEY|PI_API|PI_MODEL|ZAI_API_KEY)=' .env

Session resumption problems

Verify per-group session mount path exists:

ls -la data/pi/main/.pi 2>/dev/null || true

Ensure runtime logs show expected mounted session directory and no permission errors.

Manual Runtime Smoke Tests

Docker mode smoke

echo '{}' | docker run -i --entrypoint /bin/echo nano-core-agent:latest "Container OK"

Host mode smoke

npm --prefix container/agent-runner run build
CONTAINER_RUNTIME=host FFT_NANO_ALLOW_HOST_RUNTIME=1 FFT_NANO_DRY_RUN=1 npm run dev

Service-level Checks (launchd)

launchctl list | grep nano-core || true
launchctl kickstart -k gui/$(id -u)/com.nano-core
sleep 2
tail -80 logs/nano-core.log

One-Pass Diagnostics Script

echo "1) Node/build"
node --version
npm run -s build >/dev/null && echo "build OK" || echo "build FAIL"

echo "\n2) Docker"
docker info >/dev/null 2>&1 && echo "docker OK" || echo "docker NOT ready"

echo "\n3) Runtime policy"
grep -E '^(CONTAINER_RUNTIME|FFT_NANO_ALLOW_HOST_RUNTIME|FFT_NANO_ALLOW_HOST_RUNTIME_IN_PROD)=' .env || echo "no runtime env overrides"

echo "\n4) Latest runtime logs"
ls -t groups/*/logs/runtime-*.log 2>/dev/null | head -3 || echo "no runtime logs yet"

Escalation Data to Capture

If issue persists, capture and share:

logs/nano-core.log tail (last 120 lines)
Latest groups/<folder>/logs/runtime-*.log
Output of docker info (or host mode env flags)
Current .env runtime keys (redact secrets)

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add 0-CYBERDYNE-SYSTEMS-0/nano-core/skills/setup/debug -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

88 / 100

Community

未声明 license/许可。
未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: github
0-CYBERDYNE-SYSTEMS-0/nano-core
中文

More by @0-CYBERDYNE-SYSTEMS-0

Category & tags

Category DevOps