Ax

ax

the retro loop for AI coding agents

Make your agent learn.
Turn every agent session into a better next run.

Website · Documentation

Every sub-agent you spawn finishes its work and disappears. Whatever it
figured out - which command failed three times before the right one, which
file actually mattered, which approach to skip - dies with it. The next
sub-agent rediscovers it from scratch. Your own next session does too.

ax watches every session your harness runs, spots the mistakes it
repeats, and turns them into small, repo-specific fixes you review and
apply - one at a time.

Under the hood, the /retro workflow pulls unreviewed sessions from the local
graph when you ask for them. It records a structured retro (*tried · worked ·
failed · next*) and turns repeated friction into proposals you review. Accepted
proposals become experiments with verdicts after 3, 10, and 30 sessions. The
next session reads what worked.
*What did this sub-agent learn? Which experiments are still open?
Which skills earned their keep? What did that branch cost in tokens?*
ax answers these by reading what already happened.

60 seconds in

Or skip the terminal entirely - paste this into Claude Code / Codex and your
agent installs ax, ingests your history, labels your skills, and tells you
which ones to actually use:

the setup prompt - give this to your agent

Then ask the graph things you couldn't ask before:

Requires Bun ≥ 1.3. No database server - the graph is an embedded DuckDB
file plus a small SQLite sidecar for the decisions you make, so there is
nothing to install, start, or connect to. macOS-first; Linux works for ingest
and CLI (the one optional launchd agent is the telemetry receiver). Dev
install, schema, queries, benchmarks:
docs/development.md.

Every harness, one…