I am a user for quick. I started with the web version, but then fairly quickly discovered and pulled down the desktop version. I maybe had 5-10 chats started at that point, mostly exploring and setting up some connectors.
The chats were not shared at all between the browser and the desktop application. In fact, other than Spaces, it appeared that nothing was shared.
I updated my desktop application version several days ago, and it mentioned cloud sync. I believe the update specifically mentioned being able to reach the same chats across all devices.
It mentions your conversations/context/etc are shared between web/mobile/desktop.
However, the web surface still has its own, separate list of conversations. I can see activity on the conversations in the activity center on the desktop app, but if I try to open the chat from there I am taken to an empty conversation page that seems to just sit, loading.
I have confirmed that the accounts are the same. I’ve fully signed out of the web version multiple times. I have additionally used private and separate browsers and separate devices to ensure there are not any cached sessions/tokens.
I installed the mobile app on my phone, and it correctly shows the same conversations as my desktop application.
Are there any other suggestions for the web to show the same chats as my other devices? Is this working as intended?
Welcome to the Quick Community! To my knowledge, you are correct that they should be synced together. That is definitely interesting behavior you are encountering.
I would definitely recommend creating a support ticket with AWS Support, as they can look further into your account and potentially see why this is occurring. I will also leave this post marked as an error to promote further awareness to the AWS Team.
You’re reading the docs right: conversations, memory, and knowledge graph live in your Quick account in the cloud and are meant to match across web, mobile, and desktop, so this isn’t intended. Mobile and desktop agreeing while only the web is off rules out a local profile issue and points at the web session specifically.
Two things to check, since the thread hasn’t. First, the Region: your account spans multiple AWS Regions, assets live in the Region they were created in, and each surface has its own Region setting. If the web is pointed at a different one, you’d see exactly this (a separate, empty list on the same account). It’s in the web profile menu next to a location icon, and on desktop under Settings, Account ( Plan your Quick account structure and AWS Regions - Amazon Quick , Settings - Amazon Quick ). Second, check whether your Builder ID belongs to more than one Quick account: the web profile menu shows “Switch accounts” when it does, and if the web defaulted into a different account the chats wouldn’t be there ( User profile and preferences in Amazon Quick - Amazon Quick ).
If both line up and the web still hangs on an empty, endlessly-loading chat, that needs AWS Support on your account. Only the Support team will have the ability to access your account and properly investigate into the cause of this (Case management - AWS Support).