archon-claude-integration-fix

Configure timeout variables to resolve Claude Code workspace trust deadlocks in Archon workflows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/shichiyou/hermes-agent-001 --skill archon-claude-integration-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archon-claude-integration-fix
Source: https://github.com/shichiyou/hermes-agent-001/tree/main/.devcontainer/hermes-backup/skills/.archive/archon-claude-integration-fix
Command: npx skills add https://github.com/shichiyou/hermes-agent-001 --skill archon-claude-integration-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Resolve Claude Code workspace trust deadlocks affecting Archon workflows.

Core Features & Use Cases

  • Timeout hardening: guidance and variables to prevent first-event timeout during nested Claude Code sessions.
  • Safe workflow isolation: recommendations to run Archon outside Claude Code and isolate environments to avoid deadlocks.
  • Troubleshooting guidance: structured steps to verify workspace readiness and diagnose timeouts.

Quick Start

Run Archon outside Claude Code (e.g., via archon serve) and set ARCHON_CLAUDE_FIRST_EVENT_TIMEOUT_MS=120000 before starting the workflow.

Frequently Asked Questions about archon-claude-integration-fix

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

FAQPage Schema
Why does Claude Code workspace trust deadlock when running Archon workflows?

Claude Code workspace trust deadlocks occur when nested Claude Code processes or slow container environments cause first_event_timeout and query-aborted errors during Archon workflows. Setting ARCHON_CLAUDE_FIRST_EVENT_TIMEOUT_MS extends the wait period to prevent these failures.

How do I fix first_event_timeout and query-aborted errors in Archon?

Fix Archon first_event_timeout and query-aborted errors by setting ARCHON_CLAUDE_FIRST_EVENT_TIMEOUT_MS to 120000 milliseconds, running Archon workflows outside Claude Code via archon serve, and verifying workspace directories exist to prevent silent spawn failures.

Can I run Archon workflows from inside a Claude Code session?

Running Archon workflows from inside Claude Code is not recommended due to nested process deadlocks. You should isolate environments by running archon serve from outside Claude Code to ensure safe workflow isolation and prevent workspace trust issues.

Do I need to set environment variables to prevent Archon workflow timeouts?

Yes, you need to set ARCHON_CLAUDE_FIRST_EVENT_TIMEOUT_MS to increase the timeout threshold for slow environments. Optionally set ARCHON_SUPPRESS_NESTED_CLAUDE_WARNING to suppress warnings when nested Claude Code processes are detected during Archon workflows.

What's the best way to troubleshoot silent spawn failures in Archon?

Troubleshoot Archon silent spawn failures by ensuring workspace directories exist before starting workflows, verifying workspace readiness through structured steps, and running archon serve outside Claude Code to isolate the environment and avoid deadlocks.

When should I not use nested Claude Code processes with Archon?

Avoid nested Claude Code processes with Archon in slow container or IDE sessions where first_event_timeout errors occur. Run Archon workflows externally via archon serve instead, and set ARCHON_SUPPRESS_NESTED_CLAUDE_WARNING if nested warnings disrupt your workflow.