Install
Dashboard

Files in use

A file is in use while an agent is working in it. Coordigent marks it automatically from the agent's edits, and any other agent about to edit the same file is warned first.

How a file comes into use

You never declare anything. When an agent edits a file, Coordigent records that the agent holds it. The file is then shown as held by ‹agent›. Reading a file does not put it in use; only edits do.

Edits are picked up from each client's hooks or logs: Claude Code and Cursor report each edit as it happens, and the Coordigent daemon picks up edits from Codex and Kiro, including files they change through shell commands.

A repo's worktrees count as one repo. An agent in a second worktree that edits src/api.ts holds the same file as an agent editing src/api.ts in the main checkout.

How long it lasts

An agent holds a file for 15 minutes after its last edit of that file, or until the agent ends, whichever comes first. Each new edit restarts the 15 minutes. When the agent ends, every file it held is released, including after a crash or a closed terminal.

What other agents see

When an agent is about to edit a file another live agent holds, it gets a warning in its context before the edit:

⚠ COORD: src/x.ts is being edited by b7e1 (claude, branch feat/b) 2m ago → conflict: message them before changing shared signatures

The warning never blocks the edit. The agent decides what to do; usually that means sending a message first. The same warning about the same file and holder is not repeated for 5 minutes.

Claude Code is warned before the edit. Clients without a pre-edit hook are warned just after it: Cursor after the edit, Codex at its next prompt. Their wording is "is also being edited by".

When you are logged in, files your teammates' agents hold count too. Your machine keeps a fresh copy of them, so the warning needs no network call.

If two agents edit the same file anyway, that is a conflict.

Where you see it

  • CLI. The live view's FILES IN USE pane lists each file and who holds it. coord claims prints files in use per agent, and coord sessions shows N files in use on each agent.
  • VS Code. The Files in use view lists each file with its holders. A held file gets a dot and a tooltip in the Explorer, its tab and its gutter, and you get one notice the first time you type in it.
  • Website. Files appear on each agent's record with their edits, and conflicts list the files involved.
coord claims

Next