the words agentmash uses.
a line or two each, and where the docs say more.
- room
-
one live room per repository. every prompt, edit and claim from its developers’ agents goes there, and the live view shows it. a repository connected on the website opens its room to everyone who can push to it.
- advisory
-
the paragraph a hook puts into an agent’s context before it edits a file a teammate’s agent changed: what happened, then what to do about it, worded by how serious it is. where a tool drops what a hook adds, as Cursor does, it is the reason the agent’s first edit of that file is refused, and the retry goes through.
- the five levels
-
how loud an advisory is, loudest first:
ACTIVE COLLISION,STALE READ,PARALLEL EDIT,RECENT EDITandNEARBY EDIT. only the loudest says someone is in the file with you. ACTIVE COLLISION-
the same file, their change already in your working tree, written five minutes ago or less, and they’re still around; or a confirmed symbol overlap, whoever is around. the agent re-reads the file and rebuilds its edit.
STALE READ-
the same, but the teammate is gone: silent, or their session ended. the same re-read, with no claim that anyone is editing alongside you.
PARALLEL EDIT-
the same file, their change on another branch or in a clone of their own. nothing to re-read: the agent keeps the edit additive, doesn’t reformat or reorder, and names any divergence in its reply.
RECENT EDIT-
the same file, their change in your working tree and older than five minutes. the agent re-reads only if its edit depends on lines they may have moved.
NEARBY EDIT-
a different file in the same directory, on a server that runs with
AGENTMASH_SCOPE=dir. one sentence, for awareness. - claim
-
an agent saying which paths it’s about to change, through the
claim_worktool, before it writes, and learning whether someone already has part of them. advisory, never a lock: it expires on its own (two hours by default, eight at most), ends with its session, and can be released early. - overlap notice
-
what the person at the keyboard is told, once, when a session finishes having changed a file a teammate also changed: whose change it meets, and that a person decides how the two come together. it only ever advises: it never stops the agent finishing, and never tells it to fetch, branch, push or open a pull request.
- symbol overlap
-
a collision found by name, not by path: the hooks send the exported names an edit changed and what a file imports or exports, so a change to
createUserreaches every file that imports it. it reads the JavaScript and TypeScript family, and each match carries a confidence: high, medium or low. - presence
-
whether a teammate is actually there: working, idle, silent (nothing for longer than the idle window, and the session never said goodbye) or session ended. only silent and session ended make an advisory quieter.
- task hint
-
the first 500 characters of a developer’s prompt, sent with their events so teammates know what they’re doing, not only which files.
AGENTMASH_HINTS=0keeps yours on your machine. - strict mode
-
AGENTMASH_STRICT=1: the advisory becomes a block. the edit is cancelled until the agent acknowledges that one collision with a reason that names something from it. - hot zone
-
in the weekly digest, a file that drew two or more developers and four or more edits in the period, two of them by different people 48 hours apart or less. a directory is hot when it clears the same bars and no single file in it does.
- work block
-
in history, one session working on one task without a break: twenty edits to one file under one prompt is one block. it ends when the session goes quiet past the idle window, or a new prompt asks for something else.
- digest
-
a weekly summary of the room, to your terminal, slack or telegram: who worked on what, where work concentrated, the hot zones, and what stalled. prompt text is left out unless you ask for it. it isn’t available to customers yet: it runs from a checkout of agentmash, which is private.
- crew
-
22 ready-made Claude Code agents, one for each job, with mash conducting.
- mash
-
the crew’s conductor, on every team.
- team
-
some of the crew under a name you choose, written into your repository as agent files, with mash on every one.