agent-overwrite-grader

Did two of your coding agents write the same file within the hour? Run this in your repository:

pipx run agent-overwrite-grader

It reads your local git log for the last month and lists every file two sessions (two authors, or two branches) changed less than an hour apart: the edits most likely to overwrite each other. Nothing is sent anywhere; it is standard-library Python 3.9+, with no dependencies.

5 files written by two sessions within an hour, in 2 days of history.
17 commits by 4 sessions read, on this machine only.

  3  src/routes.ts
     c11c653 claude-code on agent/auth, Oct 5 09:14, then 8 min later 83f4ab6 codex on agent/billing (3 such pairs)
  2  src/db/schema.sql
     c73c1bd codex on agent/billing, Oct 6 09:00, then 12 min later 9a9532b claude-code on agent/auth (2 such pairs)
  2  package.json
     271b801 claude-code-2 on agent/search, Oct 5 09:47, then 8 min later 75e6e7b dev on main (2 such pairs)

Options

agent-overwrite-grader [REPO] [--since "2 weeks ago"] [--top 12] [--json]
agent-overwrite-grader --log saved.log      # grade a saved log; '-' reads stdin

--log takes the output of git log --all --source --name-only --format='%H|%an|%aI|%S'.

The rule

Two commits are two sessions when their authors differ, or both carry a branch name and the names differ. A file collides when two sessions wrote it 60 minutes apart or less. Files rank by how many such pairs they have. The same rule runs in the browser at https://overflow.games/memento/grader/?ref=pypi.

The fix

memento Team gives each file one owner at a time across machines: a session claims a path before it edits, and the next one waits. Pre-order at https://overflow.games/memento/?ref=pypi (10 USD per agent a month).

MIT licensed.