awa gives an agent a memory of what it changed.

The loop

Inside an initialized project, this is the whole loop. Built-in defaults are enough.

What it looks like

$ awa status
root:        /home/dev/acme-api
config:      built-in defaults (no awa.toml or .awa/config.toml)
initialized: yes
checkpoints: 1
  latest:    32td8sbxh2dw at 2026-07-26T20:51:51.487112Z (0 skipped)
run cache:   1 runs
  latest:    18c5f22f2059 exit=0 at 2026-07-26T20:51:51.542414Z
store:       /home/dev/acme-api/.awa/store
checkpoint:  checkpoint 32td8sbxh2dw "before extracting the rate limiter" (just now)
  dirty:     1 changed (0A 1M 0D 0R 0T 0S) — awa changes --stat
git:         branch main @ ef47c97 (dirty)
reusable:    none — 1 near miss(es), inspect with: awa run ls --near
  nearest:   18c5f22f2059 go test ./... not-reusable(input-tree-differs)
next:
  awa changes --stat     # what changed since the checkpoint
  awa diff src/          # focus the review on a path
  awa run ls --near      # why recent checks are stale
  awa run explain -- <command>
  awa log -n 5          # inspect recent checkpoints if this baseline is surprising
  awa gc --dry-run --json # store footprint and what cleanup would free
note: awa shows changes vs the checkpoint baseline; review the full git diff before acceptance

Find the answer

Every card links to a page of this release's documentation.

• I am an agent. What is the loop?

  The four commands that cover checkpoints, cached checks, supervised records, and output inspection.

  awa for coding agents

• How do I install it?

  The Homebrew formula, release archives, checksum verification, and what upgrading changes.

  installing, verifying, and upgrading awa

• How do I review what changed?

  Ranges, baselines, and why a clean delta is not the same as a reviewed worktree.

  awa changes / awa diff

• Why is my check no longer reusable?

  Near misses, mismatch reasons, and what the run cache does and does not observe.

  awa run — deterministic run cache

• What does `awa` store on my disk?

  Everything .awa/ keeps, why it is owner-private, and what must never be committed.

  awa local evidence and privacy

• How do I parse the output?

  The schema-versioned JSON envelope, and how to tell a failed command from a broken protocol.

  JSON output, exit origin, and script rules

• Something is wrong. Where do I start?

  Diagnosis by symptom, the awa doctor finding codes, and how to recover state.

  diagnosing awa — slow, stale, blocked, or broken

• Where is every command and flag?

  The exhaustive syntax reference for every command and flag.

  awa command reference

Install

A maintained Homebrew formula is the shortest path on macOS and Linux; it builds from the released source and needs no Go of your own. Prebuilt archives are published for Linux, macOS, FreeBSD, and Windows; verify the checksum before you run one.