Integrations

ADLC gates are implemented once in @adlc/core and wired into each harness through its own native mechanism: skills, hooks, plugins, or agents. Pick your harness below.

• Claude Code ships a phase-routing skill, gate commands, a prosecutor subagent, and hooks that fire the gates automatically.
• Codex is a native Git-marketplace plugin with six skills, eight lifecycle hooks, allowlisted MCP gates, and project agents.
• Cursor is a marketplace .cursor-plugin with a preToolUse rails dispatcher, skills, /adlc-* commands, and the sequential five-lens /adlc-prosecute loop, backed by the CI rail-freeze gate.
• opencode ships a rails-guard plugin hook, eight lifecycle commands, a five-lens prosecutor panel, and a keyless gate bridge.
• pi is a native extension with proactive rail blocking, git-diff revert, and a suppression gate. Five phase skills wrap the CLIs.
• Antigravity is a native agy plugin with an in-session rails-guard hook, backed by the unbypassable CI rail-freeze gate.

Any other agent

Harnesses without a native ADLC plugin can install the harness-neutral skill catalog from skills.sh, which reaches roughly seventy agents:

npx skills add voodootikigod/adlc
npm install -g @adlc/cli
adlc init

That channel installs skills only — the phase router, the bootstrap guide, and the P5 prosecution workflow, each driven through the adlc CLI. It installs no hooks, no MCP tools, no agents, and no in-session rail enforcement, so it is strictly weaker than any native integration above. Where a native plugin exists, prefer it. With the catalog alone, the CI rails-guard job is your only rail control.

Orchestrating harnesses in parallel

These integrations wire the gates into each harness. The @adlc/fleet orchestrator runs the other direction: it dispatches ready tickets to sandboxed headless workers in isolated worktrees and merges them through the gates. Its scheduler is harness-blind via a WorkerAdapter seam. Claude Code is the default worker, and adapters for Codex, Antigravity, opencode, pi, and Cursor let a single fleet run build tickets on any of them (the harness is an operator-local --adapter choice).

See the toolkit overview and the ADLC theory for the gates these integrations wire up.