aws / aws/aws-toolkit-vscode

EDITING INACTIVE FILES!

Open
#7,976 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
TypeScript
Stars
2k
Forks
807
Avg merge
10h 12m
Merged PRs (30d)
7

Description

I have just found that while using amazon Q requesting solutions to issues with a CLI that amazon Q has been editing code in an index.js file unrelated to the CLI instead of my CLI.js file. I have just had to stop amazon Q 3 times from editing code in my index.js file that IS NOT EVEN OPEN in vscode! I want to know HOW this thing can possibly be allowed to just charge in and edit code without PERMISSION and CONFIRMATION that I, am HAPPY to ALLOW these edits.

I have turned off agentic since I can not trust it.

- OS: macOS
- Visual Studio Code version:

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the reported behavior in Visual Studio Code on macOS using the referenced index.js and CLI.js files, noting whether the files are open and what Amazon Q request triggers the edit. Determine the permission or confirmation behavior expected for edits, and document a verified outcome with a focused reproduction or test.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript, vscode
Domain
developer-experience, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.