Bug: Voice dictation interrupts response stream when window focus changes

Summary

When using voice dictation (Windows Speech Recognition or similar) to compose messages in the Amazon Quick desktop app, switching focus away from the Quick window while the assistant is streaming a response causes the response to stop mid-stream. The response does not resume when focus returns — it appears truncated/incomplete.

Steps to Reproduce

  1. Open the Amazon Quick desktop app (Windows)
  2. Start a conversation and ask the assistant a question that produces a long streaming response
  3. While the response is still streaming, activate voice dictation (e.g., Win+H or another speech input method)
  4. The dictation overlay/window steals focus from the Quick app
  5. Observe that the response stream stops immediately

Expected Behavior

The assistant’s response should continue streaming to completion regardless of whether the application window has focus. Background streaming should not depend on window focus state.

Actual Behavior

The response stream is interrupted when the window loses focus. The partial response remains visible but is incomplete, and there is no way to resume or regenerate the rest of the response without re-asking the question.

Environment

  • App: Amazon Quick Desktop (Windows)
  • OS: Windows 11
  • Trigger: Voice dictation (Win+H) or any action that moves focus away from the Quick window during response streaming

Additional Notes

This is particularly disruptive for accessibility workflows that rely on voice input, since dictation inherently requires focus changes. Users who depend on voice input cannot reliably use the app while responses are streaming.

Hi @kavulum and welcome to the community!

This is interesting behavior you’ve found. Unfortunately, I don’t have a workaround for this case since this is a public facing forum. I would strongly recommend opening a support ticket (Case management - AWS Support) and framing this as both a bug and an accessibility issue.

Hope this helps and feel free to keep us updated!

Hi @kavulum,

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.

Hi @kavulum,

Since I haven’t received any further updates from you, I’ll treat this inquiry as complete at this time. Please feel free to create a new post if you have more questions.

Thank you.