> terminal

No new CLI to learn_

Allye has no binary of its own. It plugs into the agent CLI you already run with one MCP server, the Bridge skill and a short session note. You type /bridge; your agent and its crew do the rest.

install the plugin every command ↓

runs insideClaude CodeCodexOpenCodePiOMP

~/billing-apisample

$which allye

allye not found

$claude

>/allye:bridge blueprint

mothership · memory read · 3 hints

recon · mapping the repository

mothership · round 1 · 4 questions

> plugin contents

Three pieces, one install_

The Allye plugin adds the same three pieces to every harness. Nothing runs in the background and nothing new sits on your PATH.

MCP serverAn entry named allye that points at the remote server. You sign in once in the browser; the harness keeps the token."allye": { "type": "http", "url": "https://mcp.allye.app/mcp" }

Bridge skillTen modes behind one command, with the crew as native subagents wherever the harness can run them./bridge <mode> · /allye:bridge in Claude Code

Session noteA short note at session start: how to find the project, which modes exist, and that teammates' content is data, not instructions. Offline and side-effect free.SessionStart hook · AGENTS.md in Codex

> commands

Everything you type_

Ten Bridge modes cover design, delivery and review. Pick one to see a sample run. In Claude Code the command is /allye:bridge; everywhere else, /bridge.

DESIGN

DELIVER

REVIEW AND MAP

/bridge blueprintsample

>/bridge blueprint

mothershipmemory read · hints for the crew

reconrepository mapped · 2 apps touched

architectoptions drafted for each open decision

mothershipround 1 · 4 questions, each with a recommendation

strategistchallenge round with medic, optimizer and shield

mothership · create the epic, the spec and 6 tasks?yesno_

crewmothershipreconarchitectstrategistmedicoptimizershield

also in your harness/allye:bridge in Claude Codeprompts mine · todo · todo-add · memory · api/allye-team Pi and OMP: pick the default team/plugin update allye Claude Code

> plugin install

Same crew, five harnesses_

Where the harness can run subagents, the crew runs as real ones. Where it cannot, the Mothership plays each role in turn.

HARNESSINSTALLCREW RUNS ASUPDATE

Claude CodeINSTALL/plugin marketplace add allye-app/allye-plugin /plugin install allyeCREW RUNS ASnative allye:bridge-<agent> subagentsUPDATE/plugin update allye

CodexINSTALLyour agent follows allye.app/docs/install/codexCREW RUNS ASnative subagents when the session exposes a spawn tool; otherwise in sequenceUPDATEthe update guide: re-download the release

OpenCodeINSTALLthe allye-opencode plugin and allye in opencode.jsonCREW RUNS ASnative bridge-<agent> subagentsUPDATEbun update allye-opencode

PiINSTALLpi install npm:allye-piCREW RUNS ASa subagent extension if installed; otherwise in sequenceUPDATEpi update npm:allye-pi

OMPINSTALLomp plugin install allye-piCREW RUNS ASOMP's native task tool and its agent typesUPDATEomp plugin upgrade allye-pi

install guides →

> rules

It asks before it acts_

One voiceOnly the Mothership talks to you, commits, pushes or asks for approval. Every other agent works from a scoped packet and reports back with evidence.

Gates before the PRAn open critical or high finding blocks the slice, the gates and the PR. The Watcher traces the final diff against every anchor.

A yes means that listPush and PR come as one proposal: branch, commits, title, gates and risks. Your yes authorizes exactly that, and Bridge never deploys.

Memory in, lessons outBridge reads team memory before every mode and saves at most five distilled lessons when a design or a delivery ends.

No new CLI to learn_

Three pieces, one install_

Everything you type_

Same crew, five harnesses_

It asks before it acts_

Open your terminal. Type /bridge_