Hey everyone! I've been diving into AWS Q Chat, and it's been a helpful experience for me and my family. However, I'm running into two major issues. My son set up his account first, and after some digging, I made my own account to explore too, following what he recommended about joining AWS Q Chat Developer. I got it running in Ubuntu WSL, and it's awesome! While my son has had his share of fun, he hit a wall saying he ran out of tokens and needed to subscribe or wait. I thought I'd hit the same wall soon, but thankfully my account keeps going.
So here's where it gets tricky. My version started needing to compress chat frequently, but it seemed to handle it well for a while. However, I began noticing these annoying 'ghost texts' popping up—old messages showing up randomly, greyed out, and disrupting our ongoing chats. Eventually, it couldn't even compress successfully; my only options were to start fresh or clear everything. I went ahead and cleared it to keep some context alive.
Now, I've got those ghost texts back and worrying about my monthly allocation while I was in the middle of organizing files. I really liked how my setup had some compression support, and I'd prefer that over the timeout my son experiences.
My questions are: 1. Is there a fix for the ghost text issue, or is it just a glitch? 2. How can I log back into the original setup I had, which allowed for those longer sessions with compressions? I might have taken a wrong turn while trying to re-login and ended up in a system similar to my son's rather than my original. If anyone can guide me back to the version I had, I'd really appreciate it! Cheers!
2 Answers
It sounds like you've been on quite a journey with AWS Q Chat! For the ghost text issue, it’s probably a backend bug that’s cropping up due to how the chat history is managed. Unfortunately, I’m not sure there’s an official fix yet; you might have to clear it out every so often. As for logging in the way you originally did, make sure you have your credentials saved somewhere. If you remember the specific details like 'Builder' and 'Developer,' that might help. Try checking your user management settings in AWS or re-visit the initial setup prompts, just to make sure you’re picking the right options. Good luck!
Totally get your frustration! For the ghost text, some users have noticed clearing the chat history often helps prevent it from piling up too bad. Regarding the login situation, just ensure you’re selecting the right account type during the sign-in process. If you think you’ve made any IAM changes, that could explain the timeout. Maybe check if you can revert or adjust those IAM settings back to your original setup? Stick with it; you’ll get there!
Good tips! I’d suggest keeping a doc with your setup steps as you go, so you don’t lose track next time. It'll save you some headaches!
Yeah, I agree, the ghost text is annoying! But just to add on the login part, maybe reaching out to AWS support could clarify how to access the version you had before. They might be able to track it down for you.