awslabs / awslabs/amazonq.nvim

Configure different models

Open
#18 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Lua
Stars
188
Forks
13
PR merge metrics
No merged PRs in 30d

Description

It would be great to be able to select what model (out of the ones supported by Amazon Q/Kiro) is used by the plugin. Preferably even different models for chat vs code completion. Having a slower, smarter, more expensive reasoning model for chat, while having a smaller, cheaper, faster model for auto completion.

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named in the issue. Begin by locating the plugin's configuration and the code paths for chat and code completion, then determine how supported Amazon Q/Kiro models are exposed; done means users can select models independently for those two workflows.

Written by the indexing model from the issue text.

Assessment

Tech stack
lua, neovim
Domain
ai, devtools
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.