feat(amazonq): Auto Debug Functionality #7609
Merged
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
… ## Problem - to reduce # of service calls within short time duration and result in throttling error thrown - ## Solution --- - Treat all work as PUBLIC. Private `feature/x` branches will not be squash-merged at release time. - Your code changes must meet the guidelines in [CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). - License: I confirm that my contribution is made under the terms of the Apache 2.0 license.
…ble deployment from WFS (aws#7315) ## Problem - Save telemetry was being recorded for all document saves in VS Code, not just for the active workflow studio document. - Save & Deploy functionality required closing Workflow Studio before starting deployment ## Solution - Add URI comparison check to ensure telemetry is only recorded when the saved document matches the current workflow studio document. - Refactored publishStateMachine.ts to accept an optional TextDocument parameter and updated activation.ts to support new interface - Removed closeCustomEditorMessageHandler call from saveFileAndDeployMessageHandler --- - Treat all work as PUBLIC. Private `feature/x` branches will not be squash-merged at release time. - Your code changes must meet the guidelines in [CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). - License: I confirm that my contribution is made under the terms of the Apache 2.0 license. --------- Co-authored-by: Diler Zaza <[email protected]>
## Problem Instead of running `mvn dependency:copy-dependencies` and `mvn clean install`, we have a JAR that we can execute which will gather all of the project dependencies as well as some important metadata stored in a `compilations.json` file which our service will use to improve the quality of transformations. ## Solution Remove Maven shell commands; add custom JAR execution. --- - Treat all work as PUBLIC. Private `feature/x` branches will not be squash-merged at release time. - Your code changes must meet the guidelines in [CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines). - License: I confirm that my contribution is made under the terms of the Apache 2.0 license. --------- Co-authored-by: David Hasani <[email protected]>
laileni-aws
reviewed
Aug 4, 2025
laileni-aws
reviewed
Aug 4, 2025
laileni-aws
previously approved these changes
Aug 4, 2025
laileni-aws
previously approved these changes
Aug 4, 2025
ashishrp-aws
previously approved these changes
Aug 5, 2025
ashishrp-aws
dismissed stale reviews from laileni-aws and themself
The base branch was changed.
ashishrp-aws
previously approved these changes
Aug 5, 2025
|
/retryBuilds |
…s-toolkit-vscode into feature/auto-debug
ashishrp-aws
approved these changes
Aug 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
Developers frequently encounter compilation errors, linting issues, and other diagnostic problems while coding in VS Code. Currently, they need to manually copy error messages and switch to Amazon Q chat to get help fixing these issues, creating friction in the development workflow and breaking their coding flow.
Solution
This PR introduces Amazon Q Auto Debug, a new feature that seamlessly integrates diagnostic problem-solving directly into the VS Code editor experience. The feature provides three main interaction methods:
Quick Fix Integration: When hovering over diagnostic errors/warnings, developers see Amazon Q options in the quick fix menu including "Fix Problem", "Fix All Errors", and "Explain Problem" actions.
Command Palette Access: Three new commands are registered (amazonq.01.fixWithQ, amazonq.02.fixAllWithQ, amazonq.03.explainProblem) that can be triggered from the command palette or bound to keyboard shortcuts.
Intelligent Error Processing: The system automatically captures diagnostic information from VS Code's language servers, formats error context with surrounding code snippets, and sends structured prompts to Amazon Q chat. For "Fix All" operations, it processes up to 15 errors at once to avoid overwhelming the AI system.
The workflow operates through a controller-based architecture that monitors VS Code diagnostics, formats error context with file paths and line numbers, and communicates directly with the Amazon Q chat panel via LSP client messaging. When users trigger a fix action, the system automatically focuses the Amazon Q panel and submits a formatted prompt containing the error details and surrounding code context, enabling Amazon Q to provide targeted solutions without requiring manual context switching.
Video Demos
Fix single problem
Screen.Recording.2025-08-03.at.11.49.20.AM.mov
Explain single problem
Screen.Recording.2025-08-03.at.11.50.31.AM.mov
Fix all errors
Screen.Recording.2025-08-03.at.11.51.23.AM.mov