Option to disable Amazon Q and CodeWhisperer

[fayyazul-centaurlabs]

Is your feature request related to a problem? Please describe. The bundled plugin Full Line Code Completion by jetbrains gets disabled due to Amazon Q and CodeWhisperer

Describe the solution you'd like The option to disable Amazon Q and CodeWhisperer so the aws toolkit plugin does not conflict with the bundled plugin

Describe alternatives you've considered None so far

Additional context I make use of the plugin mainly for the tools under Explorer, particularly the cloudwatch logs and s3 explorer. Additionally I've found use from the Lambda run configurations. I haven't touched the AI related tools nor do I plan to. I would like to be able to use this plugin alongside the FLCC plugin by jetbrains.

[thecodemonk]

Please make this a priority. I tried Q and CodeWhisperer and they do not work well, at all and I need to disable them to get the JetBrains AI functionality back. Q and CW should be a separate plugin than the explorer related items.

[TiansuYu]

It is so annoying that Amazon set the Amazon Q button on the top of the right click list. If you care about developer experience at all, you will not push such blatant marketing moves.

[justinmk3]

We are considering how to address this, though it may take some time.

[Syrus-at-Philips]

I don't have Codewhisperer or Q setup at all and I'm not allowed to use them in my corporate work environment. The addition of these to the AWS Toolkit has broken full line completion in PyCharm Professional. The features of the AWS Toolkit are essential--managing SSO and the explorer for S3 and Cloudwatch. If I cannot use full line completion, I might as well switch to VS Code fulltime.

[justinmk3]

The addition of these to the AWS Toolkit has broken full line completion in PyCharm Professional.

That sounds like a serious bug, can you open a new issue with details about your system, and steps to reproduce (including things like the kind of code you're editing)?

[Syrus-at-Philips]

The addition of these to the AWS Toolkit has broken full line completion in PyCharm Professional.

That sounds like a serious bug, can you open a new issue with details about your system, and steps to reproduce (including things like the kind of code you're editing)?

I will attempt to verify today and follow up here.

[Syrus-at-Philips]

Here is the actual problem: So I cannot use the AWS toolkit to manage my SSO connection and browse S3 and CloudWatch if I want to use full line completion. In this context, it looks somewhat like a "feature" but I agree it is a serious bug.

[justinmk3]

That would be helpful as a new, separate issue. Then can ask jetbrains for advice.

[Syrus-at-Philips]

Issue submitted here: https://github.com/aws/aws-toolkit-jetbrains/issues/4076

[asnare]

To add a bit of context on this, I do work for several organisations that all have policies (enacted over the last year) banning the use of generative AI from vendors unless it's been through legal and procurement. It depresses me greatly to be writing this, but at the moment not being able to turn Q and CodeWhisperer off in the plugin is going to lead to org-level discussions about banning the plugin outright. Nobody will benefit from this.

[lpar]

Ideally I'd like to see the Q and CodeWhisperer stuff in a separate plugin. Failing that, I think there needs to be a way to disable it at AWS account level or for all JetBrains users.

I went to install the plugin today for the S3 and CloudWatch support, but the LLM functionality is against policy, so no plugin for me.

[AutoMatt-ic]

How do we +1? Same policy and same problem for me. With a very high level of "SO SICK OF SEEING" prompts around enabling CodeWhisperer and Amazon Q where I would expect to find helpful text instead! Marketing disguised as being helpful might be the worst kind.

[Forfend]

Please, let us disable Q and CodeWhisperer. WIth the new release of IntelliJ 2024.1 it's now possible to use Full Line Code Completion due to conflict with plugin

[GrantGochnauer]

+1 bump!

[zixlin7]

this should be resolved that now Amazon Q is in its own plugin