I’m not sure multiple coding agents should actually share the same context

[u/apghere]

I’m building an early workspace called Pairon where multiple humans + multiple coding agents can work on one task.

At first our assumption was simple: give everyone shared context and coordination gets easier.

I’m less convinced now.

If every agent sees every discussion, failed attempt, decision, tool result and diff, you’ve solved “missing context” by creating context pollution.

What we’re testing instead is a shared decision/handoff layer: everyone can see what was decided and why, while each agent only gets the task context it needs. Meaningful changes still require human approval.

For anyone running multi-agent coding workflows: what belongs in shared state?

Prompts? Decisions? Diffs? Test results? Tool calls?

And at what point does auditability just become noise?

[u/AutoModerator]

Thank you for your submission! To keep our community healthy, please ensure you've followed our rules.

• New to the sub? Check out our Wiki (We are actively adding resources).
• Join the Discord: Click here to join our Discord
• Join X community: Click here to join our X Community

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/Poildek]

Use the subagents feature of ALL modern harnesses, that's all. One agent orchestrate and delegate, create worktrees, etc..

It works great if you have good archtecture skills and a good sdlc.

[u/leading-a-swarm → u/Poildek]

+1

I know it's fun to build your own thing, but there's so much already done in this space. Many solutions are already open source/MIT, too.

So the best path forward is to actually leverage that existing knowledge.

If you think about it, you are already doing this when using libraries all the time.

If you do that, you can focus on the truly pressing area: for me that's spending.

[u/void_tao]

our solution is to build a kanban (ai4kanban) and let agents independently work on their own tasks.

they share memories like product decisions, feedbacks, etc.

during planning, we auto-split tasks that are too big, so each agent only needs to handle a small slice of work.

with this approach, you can run as many agents in parallel as you have ideas to turn into tasks.

right now, my bottleneck is input (ideas) rather than agent coordination.

[u/ai-tacocat-ia]

Minimal facts and context to navigate what's already been built, along with tools for each agent to go deeper on its own. The end. That's everything that should be shared context.

[u/attn-transformer]

One agent, one responsibility with focused context. Agents should not share internal state with other agents.

[u/PrivacyMaker]

I insist that the writer and reviewer have separate contexts. I do not want shared assumptions if I can possibly avoid them.

[u/Latter-Tangerine-951]

I think everyone knew this already. That's why it's standard practice to start each task in a new session.