A workflow depends on asking side questions of a long-running Cloud Agent without interrupting its main thread. What should be expected today?

The principle — Not every agent capability lands locally and in the cloud at once. Side chats are local-only for now; Cursor states they are not currently available for Cloud Agents, with support described as coming.

Why the key is correct — A workflow that assumes a side question can be parked beside a cloud task has nowhere to put it today, so the question goes into the cloud agent's own thread.

Why the others are wrong — Availability is the constraint rather than parity, so a cloud agent offers no side chat to open. The limit is the feature being absent, not side chats expiring when a cloud run ends. And the direction is reversed: side chats are the local case, while worktrees are the Agents Window native one.

Remember this — Side chats are local today; cloud support is promised, not present.

Sources — Cursor's Side chats documentation.