@axiom-org-ai/axiom
v1.0.2
Published
Axiom — the autonomous company: a persistent, self-evolving multi-agent organization
Readme
Axiom 🦞 — The autonomous company that runs itself
Axiom is a persistent, self-evolving autonomous company that runs on your own hardware. You are the operator, not the workforce. Describe a mission in plain words, pick the CEO model, review the team the CEO proposes, and Axiom starts working — every decision recorded, every action observable, and everything you disapprove of stoppable.
Built on the OpenClaw Gateway, developed in the open by the OpenClaw Foundation, a non-profit.
Website · Docs · User guide · Getting started · Showcase
Quick start
# 1. Install (scoped package — the unscoped `axiom` on npm is a different project)
npm install -g @axiom-org-ai/axiom@latest
# 2. Onboard: describe your mission, pick the CEO model, review the team proposal
axiom onboard --install-daemon
# 3. Open the live company dashboard
axiom org webThat is the whole setup. Onboarding verifies model access, creates the
workspace, configures the Gateway, and seeds your company. The dashboard
serves at http://localhost:8456 with overview, approvals, agents, tasks,
budgets, incidents, trace, and a live event stream.
Onboarding is one-time. After it, axiom org web is how you return to the
company; axiom org status is the quick command-line check.
Setup asks how to configure model access, and the defaults are manual: it does not scan your machine for AI apps or keys. Answer No, I'll add a key or sign in myself at the scan question to pick a provider and paste a key or log in. Choose Full access instead if you would rather Axiom look around and test what it finds.
Prefer to chat first? Run axiom setup and talk to Axiom before committing to
setup.
Requires Node 22.22.3+, 24.15+, or 25.9+.
What Axiom runs for you
- A CEO interprets your mission, proposes a team, sets objectives, and delegates work across departments.
- A heartbeat wakes the company (default every minute, tunable at setup) and runs the organizational cycle: review work, plan, and assign tasks.
- Agents execute tasks, decomposing work into parent and child subtasks with dependencies, so the CEO's delegation chains down the org chart.
- Every turn, decision, budget line, and incident is recorded, so you can trace exactly what happened and why.
Keep control
| Action | Command |
| ------------ | ------------------------------------------------------------------------------ |
| Dashboard | axiom org web — the live company UI at http://localhost:8456 |
| Status | axiom org status — task success rate, agent activity, department health |
| Agents | axiom org agents — status, model, department, last activity |
| Tasks | axiom org tasks — status, assignee, priority |
| Budgets | axiom org budgets — per-agent and per-department cost tracking |
| Incidents | axiom org incidents — failure, recovery, security |
| Trace a task | axiom org trace <task> — full chronological execution trail |
| Approve | axiom org approve <id> --reason "plan looks good" |
| Deny | axiom org deny <id> --reason "too risky" |
| Interrupt | axiom org interrupt <id> — pause a running task (waiting) |
| Resume | axiom org resume <id> — move interrupted work back to running |
| Message | axiom org message <agent> "recheck the approach" — high-priority instruction |
High-risk actions require your approval; medium-risk actions are evaluated automatically; low-risk actions proceed on their own. The web dashboard adds one-click approve and deny, and streams live events as the company works.
Keep it safe
- Back up with
axiom backup create, verify withaxiom backup verify, restore withaxiom backup restore, and enable scheduled Git backups withaxiom backup enable. - Update with
axiom update, or stay on an automatic release channel. - Read the security guide before connecting other users or exposing the Gateway remotely. Treat inbound messages as untrusted input.
Documentation
| Goal | Start here | | -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | Operator walkthrough | User guide | | Full CLI reference | CLI reference | | Connect a messaging service | Channels | | Models and providers | Models · Model providers | | Tools, skills, plugins | Tools · Skills · Plugins | | Configure or operate the Gateway | Configuration · Architecture |
Contributing
See CONTRIBUTING.md for the contribution workflow, and SECURITY.md for reporting vulnerabilities. Report bugs and feature requests through the GitHub issue chooser.
License
MIT
