Quick Destktop App. I have just changed into new laptop. How can i transfer the previous chats, artifact, memory etc? It’s still in the old laptop but not in the new laptop
Hi @edwinkk and welcome to the community!
As per my understanding, Quick Desktop data (chats, artifacts, memory) is tied to your user account, not stored locally on your machine. So in theory, when you sign in on your new laptop with the same credentials, your conversations, memory, and any agents you created should still be there. Make sure you’re signing in with the exact same account and identity provider (SSO, Google, etc.) on both machines. I would also check the app on your new laptop is set to the same AWS Region as the old one. Also double check that the Quick Desktop version on your new laptop is up to date since older versions may not display newer features. If everything matches and your data still isn’t appearing, it’s possible the “old laptop” data was associated with a different account or region. You can verify by checking the old laptop while still signed in to confirm which account and region your data lives under.
Hope this helps and feel free to keep us updated!
I have similar challange, i got new laptop today, previous got ashed and never rebooted. I had my scheduled agents installed in previous laptop, so many chat history, how to enable in new laptop. chnaged region not helping, logged in my previous account login but not showing up. i had so many doc prepared out there- kindly help .
After looking into this further, I found another user that had a similar issue. If you still have access to the old laptop (or its drive), you can copy the profile folder over to the new machine and your history should appear. Detailed recovery steps were shared in this thread: I lost all my chats, context, etc after software update.
For panisant, since you mentioned your previous laptop “got ashed and never rebooted,” if the drive isn’t recoverable, unfortunately there’s no server-side copy to restore from. In that case I’d recommend opening an AWS Support case to confirm whether any recovery options exist on their end.
Hope this helps!
Not true. Not tied to your account.
Just checking back in since we haven’t heard from you in a bit. I wanted to see if the guidance shared earlier helped resolve your question, or if you found a solution in the meantime. Moreover, if you submitted a support ticket and it uncovered any findings, please feel free to share them!
If you still have any additional questions related to your initial post, feel free to share them. Otherwise, any update you’re able to provide within the next 3 business days would be helpful for the community.
Thank you.