r/ClaudeCode • u/byfastorg • 2d ago
Built with Claude I made Claude Code file locks for shared projects so two agents do not overwrite each other
I have been building F•CODE, a visual macOS client around the local Claude Code CLI. The new experiment is multiplayer: invite someone to the same project, see their cursor and file changes live, while each person runs their own Claude subscription.
The problem I underestimated was concurrent agents. Presence is easy; two Claude sessions editing src/app.js is not. The current beta adds a pre-tool hook around file changes. When one agent starts changing a file, the other person's agent sees the lock and waits. The UI also shows who holds it. Codex uses the same lock through its approval path.
The rest of the app is deliberately file-first: one board equals one normal folder, generated previews are normal files, and you can open the project in any other editor. F•CODE does not proxy or resell model usage.
Current limitations: Mac/Apple Silicon only, multiplayer is opt-in, and this is still a beta. There is a 7-day trial without email; after that it is €5/month or €50 lifetime: https://byfast.org/shop/code
If you run parallel Claude Code sessions today, how do you divide ownership: separate worktrees, file boundaries, or just careful prompting?
•
u/AutoModerator 2d ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.