Holon

English|中文

Holon runs AI agents in a sandboxed runtime with a persistent agent_home model.

Current product split:

• holon run: stable execution kernel (sandbox + skills + agent contract).
• holon solve: higher-level GitHub workflow wrapper on top of run.
• holon serve: long-running proactive agent runtime (experimental).

Agent Home Model

agent_home is the long-lived identity and state root for an agent instance:

• the persona contract (AGENTS.md) plus CLAUDE.md as a compatibility pointer
• runtime state and caches
• job outputs and other runtime-managed artifacts (which may be associated with per-job workspaces)
• optional runtime configuration

Holon runtime and skills should use contract variables and system-recommended directories, not hardcoded Holon-internal paths.

Agents

Holon currently ships with a Claude Code agent bundle by default. You can also run other agent bundles (including custom ones) via --agent / HOLON_AGENT and select update behavior via --agent-channel / HOLON_AGENT_CHANNEL.

Modes

holon run (Stable)

• One-shot execution in a sandbox.
• Best for local tasks and CI-safe skill execution.
• Skills are enabled via CLI/config and run against a managed runtime contract.

holon solve (Stable wrapper)

• GitHub-oriented flow built on top of holon run.
• Automates context collection and publish steps for issue/PR workflows.

holon serve (Experimental)

• Long-running event-driven runtime for proactive agents.
• API/session model and controller behavior are still evolving.

GitHub Actions quickstart (with holonbot)

1. Install the GitHub App: holonbot in your repo/org.
2. Add a trigger workflow (example minimal setup):

name: Holon Trigger

on:
  issue_comment:
    types: [created]
  issues:
    types: [labeled, assigned]
  pull_request:
    types: [labeled]

permissions:
  contents: write
  issues: write
  pull-requests: write
  id-token: write

jobs:
  holon:
    name: Run Holon (via holon-solve)
    uses: holon-run/holon/.github/workflows/holon-solve.yml@main
    with:
      issue_number: ${{ github.event.issue.number || github.event.pull_request.number }}
      comment_id: ${{ github.event.comment.id || 0 }}
    secrets:
      anthropic_auth_token: ${{ secrets.ANTHROPIC_AUTH_TOKEN }} # required
      anthropic_base_url: ${{ secrets.ANTHROPIC_BASE_URL }}

3. Set secret ANTHROPIC_AUTH_TOKEN (org/repo visible) and pass it via the secrets: map as shown. holon-solve will derive mode/context/output dir from the event and run the agent headlessly. Ready-to-use workflow: copy examples/workflows/holon-trigger.yml into your repo for a working trigger.

Local CLI (holon solve)

Prereqs: Docker, Anthropic token (ANTHROPIC_AUTH_TOKEN), GitHub token (GITHUB_TOKEN or HOLON_GITHUB_TOKEN or gh auth login), optional base image (auto-detects from repo).

Install:

• Homebrew: brew install holon-run/tap/holon
• Or download a release tarball from GitHub and place holon on your PATH.

Run against an issue or PR (auto collect context → run agent → publish results):

export ANTHROPIC_AUTH_TOKEN=...
export GITHUB_TOKEN=...   # or use gh auth login

# Basic usage
holon solve https://github.com/owner/repo/issues/123
# or: holon solve owner/repo#456

# With persistent state under a specific agent home
holon solve owner/repo#123 --agent-home ~/.holon/agents/solver

Behavior:

• Issue: creates/updates a branch + PR with the patch and summary.
• PR: applies/pushes the patch to the PR branch and posts replies when needed.

Using Claude Skills

Claude Skills extend Holon's capabilities by packaging custom instructions, tools, and best practices that Claude can use during task execution.

Quick example - Add testing skills to your project:

# Create a skills directory
mkdir -p .claude/skills/testing-go

# Add a SKILL.md file (see examples/skills/ for templates)
cat > .claude/skills/testing-go/SKILL.md << 'EOF'
---
name: testing-go
description: Expert Go testing skills for table-driven tests and comprehensive coverage
---
# Go Testing Guidelines
[Your testing instructions here]
EOF

# Run Holon - skills are automatically discovered
holon run --goal "Add unit tests for user service"

Skill sources (in precedence order):

1. CLI flags: --skill ./path/to/skill or --skills skill1,skill2
2. Project config: skills: [./skill1, ./skill2] in .holon/config.yaml
3. Spec file: metadata.skills field in YAML specs
4. Auto-discovery: .claude/skills/*/SKILL.md directories

See docs/skills.md for complete documentation, examples, and best practices.

State Persistence

Skills can cache data across runs via the agent home state directory (<agent-home>/state):

# Enable state persistence by reusing a stable agent home
holon run --goal "Analyze project trends" --agent-home ~/.holon/agents/analysis

# Combine with actions/cache in CI for persistent caches

The state directory persists across runs as <agent-home>/state. Skills should write caches using runtime-provided paths/variables rather than hardcoded container locations.

See docs/state-mount.md for complete documentation.

Architecture & docs

• Current architecture baseline: docs/architecture-current.md
• RFC status index: rfc/README.md
• Agent contract: rfc/0002-agent-scheme.md

Development

• Build CLI: make build; test: make test; agent bundle: (cd agents/claude && npm run bundle).
• Operator guide (v0.11): docs/operator-guide-v0.11.md
• run GA contract: docs/run-ga-contract.md
• Skills guide: docs/skills.md
• Serve GitHub MVP: docs/serve-github-mvp.md
• Serve webhook mode: docs/serve-webhook.md
• Design/architecture: docs/holon-architecture.md
• Modes: docs/modes.md
• Contributing: see CONTRIBUTING.md