fix(amazonq): selection detection #6134
Open
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
aseemxs
changed the title
The LSP server expects cursorState to be CursorState[] (array), but JetBrains was sending it as a single object. This caused the server to fall back to default cursor state when accessing cursorState?.[0] on a non-array value. Fixes selection detection when user types directly in chat panel.
aseemxs
force-pushed
the
fix/amazonq-selection-detection
branch
from
7737611 to
3ffe4e9
Compare
aseemxs
changed the title
laileni-aws
approved these changes
Dec 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Types of changes
Description
Fixes code selection not being detected when users select code in the editor and then type directly in the Amazon Q chat panel.
Root cause: The LSP server's ChatParams interface expects cursorState to be an array (CursorState[]), but JetBrains was sending it as a single object. The server code accesses cursorState?.[0] which returns undefined when given an object instead of an array, causing it to fall back to the default cursor state
(no selection).
Fix: Wrap cursorState in a list before sending to the LSP server.
Screen.Recording.2025-12-02.at.1.31.53.PM.mov
This issue affected users who:
The chat would respond with "There's no highlighted code" even though code was selected.
Checklist
License
I confirm that my contribution is made under the terms of the Apache 2.0 license.