Documentation Guides / Claude Code

Site

Docs Guides

Claude Code

Context

Keep a minimal CLAUDE.md (or .claude/CLAUDE.md) that points at AGENTS.md, .gitagent/planner/RULES.md and .gitagent/foreman/MANIFEST.yaml. Link the canonical files rather than copying RULES into it, and keep it under about 200 lines.

Session bootstrap

Claude Code does not run project hook directories, so use the shell wrapper:

scripts/gxt-pin-mission.sh .gitagent/missions/MSN-0001.<slug>.yaml
scripts/gxt-shell-agent.sh claude .gitagent/missions/MSN-0001.<slug>.yaml

Or run a task inside the process boundary:

gantry runtime exec --mission .gitagent/missions/MSN-0001.<slug>.yaml -- claude "<task>"

How strongly it holds

An interactive session is advisory: the agent is guided by the context files, not trapped. Wrapped with gantry runtime exec or gxt-shell-agent.sh, it runs at the process boundary (Enforcement boundary).

The steps every tool shares are on Wire any agent.