When several developers use coding agents on one feature, assigning tasks is only part of the problem. Someone still has to decide which files each task owns and how the outputs fit together. I’m building Claude Share (session-share) around three separate pieces: shared tasks and contracts to describe the work, file leases to represent ownership, and a live board to show the coordination state. Each developer uses their own Claude Code account and separate checkout. The enforcement boundary matters. The plugin’s PreToolUse hook checks Edit, Write, MultiEdit and NotebookEdit against the participant’s leases. That does not make it a filesystem sandbox. Other write paths are outside those checks, and the hook fails open if the coordination server errors or times out. The practical implication is that a lease helps agents coordinate; it does not prove two branches integrate correctly. Separate checkouts, review and integration testing still matter. A task can be complete on its own while the assembled feature is broken. I’m the creator, and Claude helped implement the project. The plugin/server are MIT licensed. The source is here if you want to inspect the boundary: https://github.com/cyber1443/session-share/blob/main/packages/plugin/src/hook.ts For people building multi-agent workflows, where do you put that boundary: advisory ownership, blocking tool hooks, or isolation below the tool layer? submitted by /u/Historical_Dinner_69
Originally posted by u/Historical_Dinner_69 on r/ArtificialInteligence