Skip to content

feat(amazonq): Add model selection for agentic chat #5771

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 10 commits into
base: feature/q-lsp-chat
Choose a base branch
from

Conversation

zuoyaofu
Copy link
Contributor

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)

Description

Users should be able to select a specific bedrock model for agentic chat.

Adds a dropdown with 3 options: auto, sonnet 3.7 and sonnet 3.5, the selected value gets passed to the model request.

Flare changes: aws/language-servers#1294

Checklist

  • My code follows the code style of this project
  • I have added tests to cover my changes
  • A short description of the change has been added to the CHANGELOG if the change is customer-facing in the IDE.
  • I have added metrics for my changes (if required)

License

I confirm that my contribution is made under the terms of the Apache 2.0 license.

@zuoyaofu zuoyaofu changed the title feat: Add model selection for agentic chat feat(amazonq): Add model selection for agentic chat May 30, 2025
@zuoyaofu zuoyaofu marked this pull request as ready for review May 30, 2025 23:54
@zuoyaofu zuoyaofu requested review from a team as code owners May 30, 2025 23:54
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: do we need this? if so, can we make it a little bit more descriptive

@@ -400,6 +401,17 @@ class AmazonQLanguageClientImpl(private val project: Project) : AmazonQLanguageC
return CompletableFuture.completedFuture(Unit)
}

override fun chatOptionsUpdate(params: LSPAny): CompletableFuture<Unit> {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: should we call it sendChatOptionsUpdate to be consistent with sendChatUpdate?

Copy link
Contributor

@rli rli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hold for release approval

@@ -394,6 +394,8 @@ private handleDocCommand(chatPrompt: ChatPrompt, tabID: string, taskName: string
loadingChat: true,
cancelButtonWhenLoading: false,
})
} else {
this.mynahUI?.updateStore(affectedTabId, { promptInputOptions: [] })
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this required?

@@ -21,6 +21,7 @@ const val CHAT_LINK_CLICK = "aws/chat/linkClick"
const val CHAT_LIST_CONVERSATIONS = "aws/chat/listConversations"
const val CHAT_OPEN_TAB = "aws/chat/openTab"
const val CHAT_PROMPT_OPTION_ACKNOWLEDGED = "chatPromptOptionAcknowledged"
const val CHAT_OPTIONS_UPDATE_NOTIFICATION = "aws/chat/chatOptionsUpdate"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: alphabetical order of commands

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants