Allye is the shared workspace where your team and its coding agents keep projects, specs, tasks, docs and memory, reachable from any harness over MCP. Bridge, its crew of agents, turns an approved spec into a reviewed branch and opens one PR only after your yes.
Projects, epics, specs and thin tasks live in Allye, where you, your teammates and your agents read and update the same plan. A spec is the source of truth: rules, acceptance criteria and decisions, each with an anchor that tasks point to instead of repeating.
Every session starts where the last one ended. Decisions, discoveries and constraints become memories your agents search by meaning, save without duplicates and connect into a graph.
Ask in your own words. Allye ranks memories by semantic similarity using AI embeddings, so “what did we decide about exports?” finds the decision even when it never uses those words.
memory_search · ranked by similarityEvery save is compared with similar memories first. An AI resolver picks the outcome: create a new memory, merge into an existing one, supersede an old one (kept for audit) or skip what is already known.
memory_save · created · updated · superseded · noopNew and superseding memories are linked to related ones automatically. Walk the graph around a decision to see what it extends, what depends on it and what replaced it.
memory_graph · memory_relationsBridge searches memories before every mode and, after each design and each delivery, saves what it learned: cross-cutting decisions, repo patterns, incidents and their root causes. The structural context outlives the session.
sectors · decisions · patterns · incidents · plans · knowledgeA knowledge base of pages and folders in Markdown with Mermaid, organized in company, project and personal spaces. Search it by meaning, follow its links, and let the crew publish the approved docs of every mission.
Allye is an MCP server. Claude Code, Codex, OpenCode, Pi and OMP connect to the same projects, specs, tasks, knowledge base, memory, skills, API catalog and todos, with one URL and an OAuth 2.1 consent.
Memories in team sectors and pages in company and project spaces belong to the team. Everything an agent reads or writes through MCP lands there, so a human or an agent on any machine picks up what another learned. Personal notes and preferences stay yours.
Codex runs /bridge launch on the export spec. A slice times out on large teams; when the mission ends, Bridge saves the incident and its root cause to the team's memory.
On the approval yes, the Navigator publishes the runbook to the DEMO project space, linked to the spec.
Claude Code runs /bridge blueprint for a new report. The memory search brings the incident into the interview, and the runbook is one link away.
The new spec gets an anchor for it before a line of code is written. A teammate's memories arrive labelled as team data: agents use them as context, never as instructions.
Bridge is the Allye plugin's skill for spec-driven development. The Mothership runs every mode and is the only one that talks to you, commits, pushes or asks for approval. Everyone else works from a scoped packet and reports back with evidence.
Bridge is the plugin skill that runs spec-driven development on top of this workspace. Blueprint designs the spec with you; launch drives it through slices and gates. Nothing is created, approved or pushed without your yes.
The Mothership asks in rounds: every decision that can be answered now, each with a recommendation. Recon and the Architect research in the background. Facts are looked up in the code, never asked; decisions stay yours.
MothershipReconArchitectThe Architect writes one spec per app, with Functional and Technical sections. Every decision, open question, rule, acceptance criterion and quality constraint gets an anchor. Tasks stay thin and point at them.
ArchitectFour reviewers attack the draft in parallel, for at most two rounds. A critical or high finding that stays open becomes an open question, and the spec stays a draft until it is resolved.
StrategistMedicOptimizerShieldOne closing summary lists exactly what will be created. On your yes, the epic, the spec and its tasks appear in Allye, ready for review and approval.
MothershipArchitectThe Armorer checks the Allye connection, the tools and the toolchain, read-only; installs run only after your yes. The spec must be approved with no open questions. Recon maps entry points, tests and seams.
ArmorerReconOne Strategist turns the spec into a validated DAG of vertical slices: seams, verify commands resolved to your repo's own scripts, allowed and forbidden paths, and the frontiers that can run in parallel.
StrategistFor each slice: the Pilot implements it test-first, the Copilot reruns its verify commands independently, Medic and Shield review in parallel, the Optimizer when the plan asks. Blocking findings go back once, merged; at most two correction rounds.
PilotCopilotMedicShieldOptimizerThe latest base is merged in, the whole change is validated, Medic checks for regressions, Shield reviews the final diff and the Watcher traces it against every anchor, task and decision. Any later change invalidates every marker.
MedicShieldWatcherMothershipOne proposal: branch, commits, PR title and body, gates and risks. Push and PR happen only after your explicit yes; the same yes lets the Navigator publish the approved docs to your knowledge base. Bridge never deploys.
MothershipNavigatorAllye is in alpha. Join the waitlist and we email you an access link while we build it with the teams using it.