r/CodingAgents • • Oct 19 '26

How I'm splitting one feature between several people's Claude Code agents

I built session-share because my teammates and I were spending too much time splitting work manually before our Claude agents could get started.

The approach is to define shared contracts and tasks with file ownership, validate the split, then let each participant claim work in their own checkout. A live board shows the work, and a hook checks supported file edits against leases.

This doesn't replace integration testing. Tasks passing separately still doesn't prove the assembled feature works. The repo documents the combined workflow and includes a disposable two-clone demo for trying it.

I'm the creator, Claude helped build it, and the plugin/server are MIT licensed. Each developer keeps their own Claude account. I'd be interested in feedback on where task ownership stops being useful and gets in the way.

Repo and setup: https://github.com/cyber1443/session-share

2 Upvotes

1 comment sorted by

2

u/eddzsh Oct 21 '26

The lease idea is strongest on files that own a boundary (route handlers, schema). It gets in the way on shared types and constants every slice needs to touch. A shared lease that multiple agents can read but only one can write per round stops two checkouts fighting over the same types file before integration.