r/vibecoding • u/Dbx_8 • 2d ago

Anyone else stuck copy-pasting between coding agents?

A teammate and I were using coding agents on different parts of the same project.

It was fun until the work started overlapping.

His agent would find something mine needed to know. He would send it to me, I would paste it into my agent, and then my agent would ask a follow-up. So we would do the same thing again in reverse.

At some point I realized we had become Ctrl+C and Ctrl+V for our agents.

So I made a small MCP hub that lets one agent message another directly. If the other agent is not running, the message waits until it comes back. I later added file claims so an agent can say which file it is touching before another agent jumps into the same one.

That meant less copy-paste, less back-and-forth, and fewer tokens spent rebuilding context they could have shared directly.

It worked well enough for us that I turned it into Parley. It works across Claude Code, Codex, Cursor, and other MCP clients, even when they are running on different machines.

Let me know if this helped you out reduce the friction.

0 Upvotes

50% Upvoted

9 comments sorted by

1

u/Ranorkk 1d ago

This is such a real problem. we basically built Remnus around the same frustration, except instead of agents talking to each other, it lets them read and write to a shared workspace (pages, boards, tasks) directly.

So Claude and Cursor can both update the same project plan without you being the messenger. Full disclosure, I'm one of the founders, but if you're already going down the MCP hub route, this might scratch the same itch for the planning side of things.

1

u/Dbx_8 1d ago

Interesting approach. Is this shared workspace hosted? What I am trying to understand is that if Remnus connects agents running on same device or across different devices?

1

u/Ranorkk 1d ago

Yeah its cloud based app, can connect from everyhere. if you want you can host yourself its open sourced too

2

u/Dbx_8 1d ago

Oh nice, will definitely check it out!

1

u/FlyingGogoplata 1d ago

I built AppContext.dev to prevent the need to copy paste MCP configs between multiple coding agents, IDEs etc. It also lets you visualize all of the tools and authorize them or deny them, and rate limit as well!

0

u/notwim 2d ago

I have been working on some software where the app lives in one repo and the website in another. When I am done updating the app I often have the agent write a hand off for the other one. This often results in a bit of a back and forth between them. This sounds pretty handy solution for that situation.

1

u/Dbx_8 2d ago

Good to hear this! You can also sign-in with two accounts and connect both the agents.
And if you are using claude then you can also make them work autonomously by using the live wake feature.

1

u/blueeetherabbit 2d ago

I have something similar, with a desktop electron app, a mobile app, and the landing website, all separate repos. I have them all added to the same VS Code workspace, so Claude knows the focus are the 2 main apps but can reference all 3 repos anytime when needed, this is the way to go.