Problem
When a user cmd-clicks / ctrl-clicks a conversation in the conversations sidebar to open it in a new browser tab, the new tab is not guaranteed to stay on the backend that owns that conversation.
If the new tab initializes with a different selected backend, it attempts to load the conversation ID against that backend and shows conversation not found.
Expected behavior
Opening a conversation from the sidebar in a new tab should preserve the selected backend identity in the URL or navigation target, so the new tab resolves the conversation against the same backend as the originating tab.
Notes
This affects multi-backend Agent Canvas setups where conversations are scoped to specific backends. The fix should cover normal click and modified-click/new-tab browser behavior.
Problem
When a user cmd-clicks / ctrl-clicks a conversation in the conversations sidebar to open it in a new browser tab, the new tab is not guaranteed to stay on the backend that owns that conversation.
If the new tab initializes with a different selected backend, it attempts to load the conversation ID against that backend and shows
conversation not found.Expected behavior
Opening a conversation from the sidebar in a new tab should preserve the selected backend identity in the URL or navigation target, so the new tab resolves the conversation against the same backend as the originating tab.
Notes
This affects multi-backend Agent Canvas setups where conversations are scoped to specific backends. The fix should cover normal click and modified-click/new-tab browser behavior.