I'm not sure if this is a bug or not. I used the device link flow to add a cloud backend in Agent Canvas. I'm still seeing my list of conversations shift between personal workspace conversations, to my Openhands Org conversations, in Agent Canvas based on which org I'm looking at in https://app.all-hands.dev/. Essentially, giving me access to both org's conversations with the addition of one backend. Maybe that's by design?

Oh I wonder if on the Device Link page we need to have the user specify the Org they want to Device Link with.

Yeah that might be one piece of this, is being able to select which. The other is that the conversations list still seems to toggle based on what org is selected in the cloud even if only one of them has been added as a backend in Agent Canvas. I thought @flaky-jordan-67349 and @millions-afternoon-47582 had done some work here, but maybe we're waiting on a release?

Yes, we are waiting for the next OpenHands release. thankyou

ah okay, perfect

Shouldn't the API key only have access to one or the other?

In the past, the backend APIs retrieved data based on the

current_org_id

in the users’ database table. As a result, when we switch organizations within the SaaS environment, this column is updated accordingly. Therefore, when using the API key to call the

get_conversations

API, it reads the

current_org_id

from this database column to ensure the correct data is retrieved. The changes from Chuck have not been deployed yet thankyou