awslabs / awslabs/amazonq.nvim
Amazon Q Developer stopped working on NVIM plugin
- Dominant language
- Lua
- Stars
- 188
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
While using Q Developer Pro for Kiro, Q CLI and in NVIM, started to get error in NVIM from 17th November 2025.
```
{ message = "[2025-11-18T13:42:23.769Z] Amazon Q Token Service Manager: Getting instance of CodeWhispererStreaming client", type = 4 }
{ message = "[2025-11-18T13:42:24.120Z] Q api request error Your subscription does not support this application. Please contact your administrator.", type = 4 }
```
NVIM plugin was working fine and suddenly after Kiro launch, users on 17th November 2025 started to get error "Your subscription does not support this application". Multiple users were getting the same error.
Therefore, can we get the following information:
1. Root cause of why it stopped working suddenly
2. Is it related to some licensing or entitlement change?
3. If account-level changes need to take place in order to restore Amazon Q / CodeWhisperer access so that the NVIM plugin may use it again?
Contributor guide
Research direction
The issue names no source file or test; begin by reproducing the NVIM error with Amazon Q Developer Pro and compare access in Kiro, Q CLI, and NVIM. Trace the Amazon Q/CodeWhisperer entitlement response, then document the root cause and any account-level change needed to restore NVIM access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, lua, neovim
- Domain
- authorization, cli, devtools
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100