Legion

Legion routes AI-assisted engineering, research, editorial, design and commercial work to the right capability, keeps decisions, changes and independent checks separate, and records evidence before anything is called delivered. It is one doctrine projected into Claude Code, Codex or an AGENTS.md harness.

Set up

Public package-manager installation is not open yet. Current shipping contract is signed native Legion; Node package remains private development tooling. From a source checkout, Node 22.13+, pnpm, & Rust toolchain are required.

pnpm install --frozen-lockfile
cargo build --manifest-path engine/Cargo.toml --release --bin legion
engine/target/release/legion --version

After installing a signed release-bound binary through an approved channel:

legion setup --dry-run
legion setup --confirm
legion setup --check

Setup detects supported clients, previews exact persistent changes, projects canonical skills & MCP integration through registered host adapters, records rollback state, then verifies installed host-visible state. setup --check makes no projection changes, but completes any pending rollback journal. setup remove --confirm removes Legion-owned projections while preserving user-owned config.

Claude Code receives packaged plugin surfaces. Codex receives canonical Agent Skills under ~/.agents/skills plus MCP registration. Portable Agent Plugins receive the portable core, every public canonical skill & MCP declaration, assembled with pinned RightAX tooling.

Harnesses & fidelity

One doctrine & kernel project into harness-native slots. Legion does not pretend every host exposes identical controls.

Run legion doctor to inspect repository, binding, coverage, & host state. legion bind --registrations inventories installed hooks across settings & plugins and detects duplicate registrations.

How work flows