Paste into Claude Code, Cursor, or any agent — it reads the repo and wires the tool into your project.
Install and set up axiom-chronos (claude-plugin project) into my current project.
Found on https://claudeers.com/axiom-chronos
Repo: https://github.com/xinhi6716/axiom-chronos
Homepage/docs: —
Detected install method: claude-plugin → /plugin install axiom-chronos@xinhi6716/axiom-chronos
Category: devtools. Platforms: cli, mobile.
Read the repo's README for exact setup and env vars, then install it and wire it into my project.
Claudeers Health Verdict:
unknown; community-verified: false. Confirm the source before running anything.
// or install directly (claude-plugin)
⚠ Unverified / not recently updated — review before pasting a run-this config.
Make a wish on your codebase. Chronos plans it, splits it into modules, has Codex build them, has Claude review them, and keeps working until the change is verified or blocked.
Review each diff before committing.
Start
You need Claude Code and the Codex CLI, both signed in. Download axiom from Releases, or build it with Rust:
cargo install --git https://github.com/xinhi6716/axiom-chronos --locked
axiom doctor
In a project whose tests you can run:
axiom wish add a --stats flag to cli.py that prints done/total
Inside Claude Code, use /chronos:wish with the same text.
Save a checkpoint first. A wish edits files and sends project material to your signed-in model services.
How a wish runs
Every wish starts with Astra: Astra plans the change, chronos:critic reviews the plan, and the core rules on it before any unit is built.
The architect splits the work into modules with contracts and acceptance tests. The dispatcher sends each unit to a Codex terra worker; sol steps in only when the full suite fails after several units changed files.
Claude (chronos:reviewer, chronos:critic) reviews the Codex work; the core writes the final report in plain language.
The binary enforces the gates: no write without a claimed unit, no verified unit without a passing review of the exact files, no finished goal without a current full test.
Questions are asked only at the start. While it runs you keep interjection: in axiom wish, type a line and press Enter to add instructions, ask, or stop.
Option
Purpose
--project PATH
Work on another project.
--resume <session-id>
Continue a stopped or blocked wish.
--creative
Let Chronos find one small, evidence-backed improvement.
--max-turns N
Limit core-session turns.
Put options before the wish; everything after them is wish text. axiom research turns a question into a reviewed research plan.
Records
State lives in ~/.axiom (set AXIOM_HOME to move it): work records and briefs in orchestrate/, searchable memory in memory/, raw session events in logs/. They may contain project material; inspect them before sharing.
Status
Available: axiom wish, axiom research, axiom doctor. Tests run the protocols against scripted stand-ins for Claude and Codex; live-model results vary by project.
Beta codebase workflows with Claude Code and Codex. Scoped tasks, check records and reusable context; optional Gemini summaries.. It is open-source on GitHub.
Is axiom-chronos free to use?
axiom-chronos is open-source under the MIT license, so it is free to use.
What category does axiom-chronos belong to?
axiom-chronos is listed under devtools in the Claudeers registry of Claude-compatible tools.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Curs…
// devtoolsaffaan-m/⟨JavaScript⟩★ 297,269◷ MIT[ claude ]
AI coding assistant skill (Claude Code, Codex, OpenCode, Cursor, Gemini CLI, and more). Turn any folder of code, SQL schemas, R scripts, shell scripts, docs,…
// devtoolssafishamsi/⟨Python⟩★ 147,800◷ MIT[ claude ]