Several agents at once

Two agents in one repository can write the same file at the same time. Memnox makes the second one wait.

It happens on its own

When an agent writes a file, it takes a lock on that folder. A second agent that tries to write there is told who holds it, and you can wait, take it over with a reason, or stop. Reads never wait. Every lock expires, and goes when the session ends, even if it crashed.

See who holds what

memnox lock --list

Hold a path yourself

Before you start editing something by hand:

memnox lock src/checkout --for 30m     # agents wait until you are done
memnox lock --release <id>             # let it go early

src/billing holds src/billing/invoice.ts, and does not hold src/billing-legacy.

When another machine holds it

On a team, a lock reaches every machine. An agent refused by another machine's lock waits five seconds, then names a command for a person to run. If you are at a Claude Code session, it asks you in its own prompt whether to take the lines over instead.

memnox lock --free <id> --reason "they finished an hour ago"

Only a person can run it, at a terminal, so the refused agent cannot free itself.

See where agents collided

memnox collisions              # the last seven days
memnox collisions --days 30    # further back

It shows two agents in one file, and two agents building the same thing.

Give each agent its own job

Declared tasks make an agent straying into someone else's area stand out:

memnox run --task "fix checkout" --paths 'src/checkout/**' -- claude
memnox run --task "update docs" --paths 'docs/**' -- codex