roblourens' Description of Work
Cloud sessions can retain a default-chat title such as main after the host updates the session title. The editor window preferred that chat title, hiding the correct session title.
Use the session title consistently for cloud session list rows, live conversations, and recorded history, matching the Agents window. Route default-session renames to the session channel. Keep independent local default-chat titles and peer-chat titles unchanged.
How to test
- Create a Cloud session from the editor window and complete a turn.
- Confirm the session list, chat header, and editor tab use the session title rather than the default chat's branch-name title.
- Open the same session in the Agents window and confirm the title agrees.
- Rename the session from the editor and confirm both windows update.
Exercised this flow against a real cloud session with the fixed Code OSS build on macOS. The host's default chat stayed titled main, while both windows displayed the session title. A manual rename updated both windows and persisted on reconnect.
Two limits observed during live testing: the host retained the initial prompt label rather than generating a short title, and cold discovery after reload briefly shows the older task name until opening the session reconnects to the host. This PR fixes the default-chat/session-title selection mismatch, not task-name synchronization.
(Written by Copilot)