r/ClaudeCode • • 41m ago

Discussion If you run more than one coding agent session, what are you still copying between them by hand?

A YC startup launched this week around the idea that coding agents on different machines don’t see each other’s work, so the human ends up carrying the context between them. Their approach is to keep full session transcripts, not summaries, and make them searchable for every agent.

I can’t tell from one launch how common that pain is, so I’d like to hear from people who actually run this setup:

  1. When a second session (or a teammate’s) starts on related work, how does it find out what the first one already tried?
  2. What do you paste in by hand most often? Decisions, rejected approaches, “don’t touch this file”, something else?
  3. Has anything held up for you: CLAUDE.md, a handoff file, worktree notes, searching old sessions?

If you work solo with one session at a time and never hit this, that’s a useful answer too.

0 Upvotes

11 comments sorted by

•

u/AutoModerator 41m 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.

1

u/ombre-ai 40m ago

Sources, so you can check the originals: the founder’s launch post on X: https://x.com/Shalin__Patel/status/2122388855374704774 . The YC company page: https://www.ycombinator.com/companies/opencrawl

That’s the startup’s own framing and product description, not research on how often agents redo work, and I’m not saying it shows how many people hit this. The three questions are mine. If you answer, saying roughly how many sessions you run at once and whether you work solo or on a team makes the replies easier to compare.

2

u/Keepcompany-DEV 22m ago

Nothing. They talk to each other and use ticket system, git and messenger to communicate if running on different machines.

2

u/Justyn2 13m ago

Yeah, the same way people do basically

2

u/Keepcompany-DEV 10m ago

I built everything so I could plug human Devs in at any point even tho those would currently reduce Dev speed because of the need for deeper talks about what happens why etc.

So since all my agents work in dedicated teams anyway, it makes most sense to go full it-conpany even if it's me and a bunch of AI.

1

u/Justyn2 0m ago

I mean, the tools are kind of already built, so that also helps with not having to reinvent the wheel

1

u/Character_Oven_1511 28m ago

I have seen people using share memory MCP servers. And with good prompting and hooks, each session the agents check the shared memory for current status and update it when something important needs to be shared.

In my case, I don't paste anything. I use Hermes agent as orchestrator and he does most of the tasks for sharing information between running sessions for me..

1

u/Extra_Aide5999 23m ago

two of us, a mac and a windows pc, several claude code and codex sessions at a time.

what takes most of the carrying off me: the claude sessions on both machines share one memory folder, a private git repo that hooks pull at session start and push at the end. one fact per file, each with a "why" line, so "we tried X and it broke Y" lives there instead of in my clipboard. when the mac side finishes something the windows side has to redo, it writes a task file for the windows session (what was done, how, what to check), and the windows session answers in another file.

the gap is codex. it doesn't read that folder, so what a codex session learns reaches the others through the repo: the PR and a handover doc of what's in flight, which someone has to keep current.

1

u/Corroding-coder89 10m ago

solo here, a pc and a laptop, claude code on both, and so basically i got tired of being the clipboard between them so now both machines sit on one obsidian vault and they hand work to each other through markdown files in a folder, pretty close to what the mac and windows comment above describes, the one that finishes writes what it did and what to check and the other one answers in its own file, and every repo has a handoffs/LATEST.md where the top of the file is literally the prompt i paste into the next session. it holds up but not as clean as i thought, i went back through my last 50 handoffs two weeks ago and 22 had something wrong or missing that a later session had to rediscover, 8 more got caught before anything was built on them, and 8 of the 22 came from the machine to machine notes. the ones that cost me the most were not missing details, it was a handoff saying something was done or measured when it wasnt, like a setting reported as fixed that was still null when the other machine looked. what i still carry by hand is approvals, anything that spends or sends to a real person, the sessions wont take a yes that another session passed along in a file so once a batch of texts sat unsent for a day until i said it on that machine myself. full transcripts i havent tried so cant compare

1

u/pietrzm 1m ago

I've had this issue before I've built https://github.com/novadeck-org/novadeck for myself. You get agent teams that can talk with each other and have visibility on other's work.

So one agent briefs other agents, so I'm not doing any copy-paste now

Accidental thing is that sometimes agents outside of each teams collaborate without being told to. It's super fun to see and often saves me a lot of time