Let one agent chat peek into / coordinate with another in-flight chat

Ideas Feature Requests
, ,
1

Feature request for product/service

Chat

Describe the request

Right now, when I run two Cursor agent chats in parallel on the same repo (e.g. one doing a data-ingest task, another doing UI/feature work), each chat only sees its own conversation history — even though they’re both editing the same working tree. If chat A wants to know “is chat B still writing files, and what did it just do,” there’s no way for A to peek at B’s live status or transcript; I have to manually relay updates between them.

Why the existing subagent (Task tool) feature doesn’t solve this: Cursor already lets an agent spawn a subagent, but that forks away from the main thread — it collapses two independent trains of thought into one. As the operator, I lose the ability to keep two separate, continuous conversations going at once, each with its own context and my own ongoing input/interjection, while still letting them stay coordinated. Subagents are for delegating a bounded task, not for running two parallel, operator-driven lines of work that need to see each other.

Requested feature: a way for one agent (or the user, from within a chat) to:

  1. List other currently-running/recent chats in the same workspace, with a lightweight status (running / idle / done).
  2. Read a summary or the live tail of another chat’s transcript.
  3. Optionally inject a note/instruction into another running chat (“insertion”) — e.g. “pause before touching file X” or “here’s what I just changed, please account for it.”

This would let two independent, operator-driven chats stay coordinated without collapsing into a single subagent thread, and without the operator having to manually relay status between windows — reducing the risk of two chats stepping on each other’s uncommitted changes.

Operating System (if it applies)

Windows 10/11

6

Thanks for writing this up so clearly. Two chats you are driving yourself, on the same working tree, should be able to see each other without collapsing into one parent thread.

Today, each agent chat only has its own conversation. Chat A cannot list other running chats, follow a live tail, or drop a note into chat B. That is not something you misconfigured.

We’ve let the team know. For now, you can search other transcripts from the Agents Window with Ctrl+K: Conversation search | Cursor Docs

I’ll post here if there’s an update.