Feature request for product/service
Cursor IDE
Describe the request
Allow agents running in separate live Cursor windows/workspaces to join a temporary shared conversation while retaining their respective workspace/codebase context.
Example: I maintain a compiler, runtime, and kernel driver as separate repositories. A bug occurs at the runtime↔driver interface. Instead of loading both codebases into one agent or manually relaying messages, I could invite the runtime agent and driver agent into a conference.
Each agent would remain authoritative for its own workspace and could inspect its local code independently, while exchanging findings, API contracts, assumptions, and proposed changes through a shared session.
Useful capabilities could include:
invite selected live Cursor agents/workspaces;
shared conference transcript;
each agent retains its own local context/index;
explicit attribution of statements to each workspace;
agents can challenge incompatible assumptions;
produce a final agreed interface contract/action plan;
optionally hand implementation tasks back to each workspace agent.
This would be especially useful for multi-repository systems, client/server development, compiler/runtime/driver stacks, frontend/backend boundaries, microservices, and API migrations.
The important distinction from simply giving one agent more context is that each participant already has deep context for its own subsystem. The feature would allow those specialized contexts to cooperate rather than flattening everything into one enormous context window.