- Newest
- Most votes
- Most comments
I understand you're experiencing input lag in the Amazon Q chat interface in VS Code after exchanging a few messages. Based on the information available, there are no known widespread issues specifically matching your description of input lag developing after a few message exchanges in the Amazon Q chat interface.
Since you've already performed extensive troubleshooting including reinstalling VS Code and the AWS Q extension, testing different versions, disabling other extensions, and monitoring system resources, here are some additional suggestions:
-
Try starting a new conversation by selecting the "+" icon in the Amazon Q chat window, as this resets the conversation context.
-
Consider using alternative ways to interact with Amazon Q:
- Try the inline chat feature by highlighting code and using Ctrl+I (Windows) or ⌘+I (Mac)
- Use Amazon Q from the command line with the "q chat" command if you have the Amazon Q Developer CLI installed
-
Monitor the chat session with CloudWatch if you have access to it, as Amazon Q Developer can be monitored using CloudWatch metrics that might reveal performance issues.
-
Since this appears to be a specific issue with your environment that persists across versions and configurations, I recommend reporting this as a bug to AWS Support or through the AWS Toolkit for VS Code GitHub repository, providing all the detailed information you've shared here.
The issue might be related to how the chat history is being processed or stored in your specific environment, especially since it consistently occurs after a few message exchanges.
Sources
Using chat on the command line - Amazon Q Developer
Monitoring Amazon Q Developer in chat applications with Amazon CloudWatch - Amazon Q Developer in chat applications
Community | AWS Toolkit for VS Code: Amazon Q & CodeWhisperer
Chatting inline with Amazon Q Developer - Amazon Q Developer
answered a year ago
Relevant content
asked 2 years ago
asked 2 years ago
- AWS OFFICIALUpdated 4 months ago
