Argot

Lint the rules you never wrote down.

  AI writes the code. argot harnesses it with the one thing that can’t
  hallucinate: your repo’s own history.
  Statistics, not a second LLM. 100% local. It surfaces the divergence — you
  decide what to accept.

  argot.tmonier.com
   · 
  Documentation
   · 
  Evidence
   · 
  Research log

      🎬 Watch the 45-second launch film

Start with an audit

argot audit needs no prior Argot fit or configuration. It fits a historical
base in a temporary worktree, then evaluates the surviving base-to-HEAD net
diff. Your working tree is left untouched. It is a review prompt—not a census
of who wrote code, or proof that a finding is a defect.

Windows: powershell -c "irm https://github.com/get-tmonier/argot/releases/latest/download/argot-installer.ps1 | iex".
The npm package is also available as npm install -g @tmonier/argot.

Audit needs usable Git history and supported source. It has no fixed runtime
promise. It runs fully offline — the code-embedding model behind the semantic
findings ships inside the binary. See
Getting started for install
and fit details.

If the audit gives you a useful lead, fit the current repository and score the
changes you intend to review:

Review and commit the generated argot.toml and .argot/ fit snapshot, then
merge it into the branch future PRs target before adding a CI workflow. Local
tools and CI then use the same learned baseline. CI only reads the base branch
snapshot; it never fits, so the initial snapshot PR must be separate from the
CI-workflow PR. argot status later recommends a local
fit-and-commit refresh only when accepted source, function, or layout surfaces
have materially changed. Commit count and age are not refresh triggers by
default; [fit] refresh-after is…