Skip to content

AWS Q Chat Interface Input Lag After Brief Usage

0

I'm experiencing consistent input lag in the AWS Q chat interface after approximately three message exchanges. The lag only affects the chat window - when typing in the chat, there's a delay of a couple of seconds before text appears. Regular coding in VS Code remains responsive with no delay. This issue began approximately 6 days ago.

Steps to Reproduce:

  1. Open AWS Q chat interface
  2. Exchange 2-3 messages with AWS Q
  3. Continue typing in the chat window
  4. Observe significant lag between typing and text appearing

Environment Details:

  • Operating System: Linux (Ubuntu 24.04.2 LTS)
  • Kernel: 6.11.0-29-generic
  • Architecture: x86_64
  • VS Code Version: 1.100.0 (19e0f9e681ecb8e5c09d8784acaa601316ca4571)
  • AWS Q Extension Version: [Your current AWS Q version]

Version Testing:

  • Tried the latest VS Code version and reverted back to the second latest version
  • Tested approximately five previous versions of both AWS Q extension and VS Code

Troubleshooting Already Performed:

  • Cleared conversation history
  • Reinstalled VS Code and AWS Q extension
  • Tried previous versions of both VS Code and AWS Q
  • Disabled all other extensions to check for conflicts
  • Monitored system resources (no unusual CPU/memory spikes observed)
  • Tested on different network connections
  • Created swaps and minimized the environment
  • Tried previous secured builds for AWS Q and VS Code

Additional Notes: The issue is consistent and reproducible. The lag only affects the chat interface input, not the response time from AWS Q or any other VS Code functionality. Regular coding remains responsive with immediate keyboard feedback.

asked a year ago318 views

1 Answer
0

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:

  1. Try starting a new conversation by selecting the "+" icon in the Amazon Q chat window, as this resets the conversation context.

  2. 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
  1. 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.

  2. 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

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.