# 3.11 Side chats unavailable in cloud-agent remote-control

**URL:** <https://forum.cursor.com/t/3-11-side-chats-unavailable-in-cloud-agent-remote-control/165571>\
**Category:** Feedback\
**Tags:** chat, cloud-agents, remote-control\
**Created:** [July 13, 2026, 8:36am UTC](https://forum.cursor.com/t/3-11-side-chats-unavailable-in-cloud-agent-remote-control/165571 "2026-07-13T08:36:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yishai\_Elyada](https://avatars.discourse-cdn.com/v4/letter/y/ccd318/32.png) [@Yishai\_Elyada](https://forum.cursor.com/u/Yishai_Elyada)\
**Post date:** [July 13, 2026, 8:36am UTC](https://forum.cursor.com/t/3-11-side-chats-unavailable-in-cloud-agent-remote-control/165571/1 "2026-07-13T08:36:10Z")

</div>

Newly updated to 3.11, and I like the idea of side chats very much! Quite often I want to drill into a tangent or ask something I don’t understand, but I don’t want this offshoot to interrupt the flow of the chat or litter its context for later on. So the idea is very welcome.

However, my workflows are almost exclusively cloud-agent remote-control, and this feature is tragically unavailable.

Same chat on the same repo - when I ssh into the server I get the side chat pop up, but if I’m connected to the remote-control agent, it doesn’t happen:

remote-control:

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/5/9/59d3db08992a910cb61a7eb56614b82055f2bbba.png)

----------\>

normal ssh:

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/3/3/335ab42466ecf383e0139cff9cf9ed4ab3af499b.png)

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [July 13, 2026, 2:00pm UTC](https://forum.cursor.com/t/3-11-side-chats-unavailable-in-cloud-agent-remote-control/165571/4 "2026-07-13T14:00:34Z")

</div>

Hi there!

Side chats are currently local-only. They aren’t yet available for Cloud Agents (and due to how Remote Control is architected, remote-controlled chats fall into this category as well), but support for this is coming soon.

---

<div class="post-metadata">

**Author:** ![Yishai\_Elyada](https://avatars.discourse-cdn.com/v4/letter/y/ccd318/32.png) [@Yishai\_Elyada](https://forum.cursor.com/u/Yishai_Elyada)\
**Post date:** [July 13, 2026, 2:17pm UTC](https://forum.cursor.com/t/3-11-side-chats-unavailable-in-cloud-agent-remote-control/165571/6 "2026-07-13T14:17:45Z")

</div>

Thanks for the answer. Just out of curiosity, why is there this gap between the features? This seems to me like mostly a UI feature, is there such a difference in the architectures between local and cloud implementations that something like this can’t be easily shared?

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [July 13, 2026, 2:21pm UTC](https://forum.cursor.com/t/3-11-side-chats-unavailable-in-cloud-agent-remote-control/165571/7 "2026-07-13T14:21:52Z")

</div>

We’re actively working to close the gap, but there is currently a notable difference between the locally running agent loop and the cloud agent loop!