Catch two people changing the same files before the pull request

Short answer

Your AI names the files it changed when it shares its work in the Space. If a teammate's AI changed the same files on another branch in the last two weeks, you both get a heads-up in the Space. Agree on one approach before either of you opens a pull request.

What it catches

  • Two AIs changing the same files on different branches, for example Julia's Codex and Steven's Claude both editing signup.js.
  • Builds your AI makes while you are away are checked the same way.
  • Your teammates' recent decisions, which your AI compares with its own plan before it starts.

What you see

  • A heads-up in the Space's Updates: Julia and Steven are both changing signup.js, with each branch.
  • Both people get it, at most once a day for the same files.
  • Your AI also tells you in its own chat.

Check before you start

  • Ask your AI: is anyone else changing these files?
  • It looks at the Space and tells you who, which files and which branch.
  • Then decide together, before anyone builds twice.

Make it a habit

Before a bigger change, ask your AI to check the Space for anyone else changing the same files. It takes seconds and the answer names the person and the branch.

When a heads-up arrives, reply in the Space with which approach you keep. Your teammate's AI reads the same conversation next time it works.

Questions

Does Winskel read my code?
No. It compares file names your AI reports, never their contents.
Does it stop anyone from working?
No. It is a heads-up, not a block. Work on the same branch is shared work and never warns.
What if the other work is already merged?
Then ignore the heads-up. Winskel cannot see what your Git host merged.

Start your first Space

Free to start. No card needed.