Installs into your project
One command adds the agents, tasks, templates and checklists to the repository.
Cyryx Labs / Products / AEXOS
AI agents that work to a method.
AEXOS, the Agentic eXecution & Orchestration System, installs specialised AI agents, the procedures they follow and the gates they must pass into your project. You talk to one orchestrator; it routes the work to the specialist that owns it.
Core available on npm · v5.3.0 · Node.js 18+
Next chapter
What it is, what it is for, and how it runs.
Two simulations below show a story moving through the cycle and a request being routed.
What it is
A team with roles, procedures and gates, not a smarter prompt.
AEXOS is a command-line framework. It scaffolds a team of AI specialists into your repository, together with the procedures they run, the checklists that decide when work is done, and the routing layer that decides who handles what. It works from your terminal and inside the AI coding environment you already use.
Runs where you work
From the terminal and inside supported AI coding environments, with the same roster everywhere.
Leaves a record
Stories, QA verdicts and state live in files you own and can review.
What it is for
AI-assisted delivery breaks in the same four places.
AEXOS enforces the method instead of recommending it. Each failure on the left has a rule on the right.
Planning is inconsistent
Every session starts from a different prompt, so the same kind of work is planned a different way each time.
Context gets lost
The agent that implements never sees what the agent that planned understood.
Authority drifts
Any agent can change anything, including pushing code nobody reviewed.
Output goes unverified
Work is called done because it was generated, not because it passed a check.
Procedures, not prompts
Each task is a procedure with declared inputs, outputs and a completion checklist. The expertise lives in the procedure, so it runs the same way every time.
Stories carry the context
Development begins and ends with a story file that holds everything the developer agent needs, from acceptance criteria to QA evidence.
Scoped authority
Every agent has a scope. Only the DevOps agent may push, open pull requests or publish releases.
Gates that can stop work
Stories are validated before implementation and gated by QA before they ship. A blocking check stops execution.
How it runs
Watch one story move from draft to push.
Every change starts as a story. It is validated before anyone writes code, implemented against its acceptance criteria, gated by QA and pushed by the one agent allowed to push. Nothing skips a step.
- Create@sm *draftDraft
- Validate@po *validate-story-draftGO
- Implement@dev *developInProgress
- QA gate@qa *gatePASS
- Push@devops *pushDone
story-4.2 · simulation
- › @sm *draftStory 4.2 drafted from the epic · status Draft
- › @po *validate-story-draft10-point check · 8/10 · GO
- › @dev *developWorking against 6 acceptance criteria · status InProgress
- › @qa *gateVerdict PASS · evidence written to the story
- › @devops *pushPushed by the only agent allowed to push · story Done
Story Done · evidence recorded
Simulation · commands and verdicts as documented, example story
Routing
You talk to one orchestrator.
The orchestrator reads a generated registry, matches your request to a domain and routes it to the specialists that own it. Adding a squad needs no change to the orchestrator.
You ask
“Add usage-based billing to the dashboard”
Routed by
@aexos-master
- @pmRequirements01
- @architectDesign02
- @devBuild03
- @qaGate04
- @devopsShip05
- @marketing-chiefMarketing squad
- @sales-chiefSales squad
- @ops-chiefOperations squad
Simulation · example requests
What ships in the package
Counted from @aexos/core 5.3.0
- Specialised agents
- 6412 core roles and 52 squad specialists
- Tasks
- 291Executable procedures
- Workflows
- 33Connected task sequences
- Checklists
- 62Validation before done
- Squads
- 9Business domains beyond code
Building blocks
Six concepts carry the whole system.
Workflows are made of connected tasks, not connected agents. That is what keeps the method stable when agents change.
Agent
A role with a scope of authority and a list of procedures it may run. It routes work; it does not hold the expertise.
Task
An executable procedure with declared inputs, outputs and a completion checklist.
Template
The shape of the document a task produces.
Checklist
The validation a task must pass before it counts as done.
Data
The knowledge base a task reads from.
Workflow
A sequence of connected tasks, with the conditions for moving between them.
The team
Twelve core roles, nine squads.
Core roles cover software delivery end to end. Squads extend the same method to business domains, each with one entry agent and specialists that cite the published method they apply.
- @aexos-masterOrchestrator. Reads the registry and routes each request.
- @analystBusiness analysis and research
- @pmProduct requirements and epics
- @poStory validation and backlog
- @smStory drafting from epics
- @architectArchitecture and technical design
- @devImplementation against acceptance criteria
- @qaQuality gates and test architecture
- @data-engineerDatabase design and operations
- @devopsThe only role allowed to push, open PRs and release
- @ux-design-expertUX, UI and design systems
- @squad-creatorBuilds new squads
Squads in Core
- CEO
- Board
- Products
- Marketing
- Sales
- Operations
- Customer Success
- Business Administration
- Claude Code Mastery
Quality and rules
Three gate layers. A constitution the agents follow.
Checks run at three points before code is accepted. The rules every agent follows are written down in the project, and the non-negotiable ones block execution when broken.
- 01
Pre-commit
Lint and type checks on every commit.
- 02
Pre-push
The story's acceptance criteria and status are checked before code leaves the machine.
- 03
CI
The full test suite plus structural validators.
CLI first
The command line is the whole product. No UI is ever required to operate it.
Agent authority
Each agent acts only inside its scope.
Story-driven
No development without a story that defines it.
No invention
Agents work from requirements and sources, not assumptions.
Quality first
Checks run before work moves forward.
Get started
One command to install Core.
Works with
- Claude Code
- Gemini CLI
- Codex CLI
- and other AI coding environments
Requirements
- Node.js 18 or later (20+ recommended)
- npm 9 or later
- Linux, macOS or Windows
New project
$ npx @aexos/core init my-projectExisting repository
$ npx @aexos/core installCheck the installation
$ aexos doctor --fixRestart your AI coding environment after installation so it loads the generated agents and rules. Then ask @aexos-master for *help.
Editions
Start free with Core.
AEXOS is proprietary software from Cyryx Labs. Core is free to use under the AEXOS license; Pro is licensed commercially.
Core
Available on npmFree to use under the AEXOS license for personal, internal, educational and commercial work, including work you deliver to clients. The CLI, the core roles, the squads, tasks and workflows, and the doctor, validate and update commands.
Pro
Commercial licensePro capabilities and squads for licensed users, available under a paid commercial agreement. Talk to us about access.
Questions
Before you install.
Is AEXOS open source?
No. AEXOS is proprietary software from Cyryx Labs. The Core edition is free to use under the AEXOS license, including for commercial work; redistribution and hosted resale are not permitted.
Does AEXOS replace human review?
No. It structures and checks the work, but you remain responsible for reviewing and accepting what the agents produce.
Does it only work for software projects?
Software delivery is the core. The squads extend the same method to business domains such as product, marketing, sales and operations.
What does it take to try it?
Node.js 18 or later and one command: npx @aexos/core init my-project. Restart your AI coding environment afterwards so it loads the generated agents.