# Agent-to-agent messaging across workspaces

**URL:** <https://forum.cursor.com/t/agent-to-agent-messaging-across-workspaces/167161>\
**Category:** Feature Requests\
**Created:** [July 31, 2026, 7:16pm UTC](https://forum.cursor.com/t/agent-to-agent-messaging-across-workspaces/167161 "2026-07-31T19:16:25Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Goyberg](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/michael_goyberg/32/116288_2.png) [@Michael\_Goyberg](https://forum.cursor.com/u/Michael_Goyberg)\
**Post date:** [July 31, 2026, 7:16pm UTC](https://forum.cursor.com/t/agent-to-agent-messaging-across-workspaces/167161/1 "2026-07-31T19:16:25Z")

</div>

### Feature request for product/service

Cursor IDE

### Describe the request

Please add a lightweight inbox between agents in different projects/chats — like email, not shared memory.

Use case: I port features from repo A (Sitonaim/warehouse) to repo B (catalogofworks). Today I manually copy a briefing between two Cursor chats. Each agent has its own context (good), but they cannot hand off tasks, status, or clarifying questions to each other.

What I want:

Cross-workspace agent messages (task / status / artifacts / questions)  
No merging of conversation memory or full context  
Optional: attach a doc path or short payload  
This would unlock multi-repo workflows without making the human the courier between agents.

---

<div class="post-metadata">

**Author:** ![kevinn](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kevinn/32/101206_2.png) [@kevinn](https://forum.cursor.com/u/kevinn)\
**Post date:** [July 31, 2026, 7:37pm UTC](https://forum.cursor.com/t/agent-to-agent-messaging-across-workspaces/167161/6 "2026-07-31T19:37:37Z")

</div>

Hi @Michael_Goyberg Thanks for the forum post. Cursor doesn’t currently support direct messaging between agents in separate workspaces or chats. For now, you could:

- Add both repositories to a multi-root workspace so one Agent can access them: [Search | Cursor Docs](https://cursor.com/docs/agent/tools/search)
- Keep separate agents and use a shared briefing file as a manual handoff, provided both can access the same local file

The second option is only a convention, not synchronized agent messaging, but it can reduce the copy-paste overhead.