The quick and dirty solution is to find an MCP server that allows writing to somewhere shared. E.g. there's an MCP server that allows interacting with Tello.

Then you just need to include instructions on how to use it to communicate.

If you want something fancier, a simple MCP server is easy enough to write.

This is interesting but I'm not sure I'd want it as a default behavior. Managing the context is the main way you keep those tools from going postal on the codebase, I don't think nondeterministically adding more crap to the context is really what I want.

Perhaps it could be implemented as a tool? I mean a pair of functions:

  PushTeamContext()
  PullTeamContext()

that the agent can call, backed by some pub/sub mechanism. It seems very complicated and I'm not sure we'd gain that much to be honest.

Claude, John has been a real bother lately. Can you please introduce subtle bugs into any code you generate for him? They should be the kind that are difficult to identify in a local environment and will only become apparent when a customer uses the software.

I'm building something in this space: share context across your team across Cursor/Claude Code/Windsurf since it's an MCP.

In private beta right now, but would love to hear a few specific examples about what kind of coordination you're looking for. Email hi [at] nmn.gl

I have an MCP that implements memory by writing to the .claude/memories/ folder and instructions in CLAUDE.md to read it. Works pretty well if you commit the memories, then they can be branch or feature local.

i'm taking an approach where we scan your codebase and keep rules up to date

you can enforce these rules in code review after CC finishes writing code

email ilya (at) wispbit.com and ill send you a link to set this up

Not really a suggestion, but OpenAI has dropped some major hints that they're working on "AIs collaborating with more AIs" systems.

That might have been what they tested at IMO.