aws / aws/amazon-q-developer-cli

Need ability to manage trusted commands - convert trusted commands back to untrusted

Aperta
#2,404 1 commento 0 reazioni 0 assegnatari Vedi su GitHub
waiting-for-feedback
Lingua principale
Rust
Stelle
2k
Fork
439
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

### Checks

- [x] I have searched [github.com/aws/amazon-q-developer-cli/issues](https://github.com/aws/amazon-q-developer-cli/issues?q=) and there are no duplicates of my issue
- [x] I have run `q doctor` in the affected terminal session
- [x] I have run `q restart` and replicated the issue again

### Operating system

macOS 15.5.0 (24F74)

### Expected behaviour

Users should be able to:

1. View a list of currently trusted commands/patterns
2. Remove specific commands from the trusted list (convert trusted back to untrusted)
3. Clear all trusted commands at once
4. Have a configuration interface or command to manage trust settings

For example: `q settings trusted-commands list`, `q settings trusted-commands remove `, `q settings trusted-commands clear`

### Actual behaviour

Currently, when a user accidentally marks a command as trusted (using 't' in the y/n/t prompt), there's no apparent way to:

- See what commands are trusted
- Remove a specific command from the trusted list
- Manage trust settings through the CLI

The trust settings appear to be stored internally without user access through `q settings` or configuration files. Users can only reset ALL settings by removing the entire configuration directory.

### Steps to reproduce

1. Run a command that triggers the y/n/t prompt
2. Select 't' (trusted) by mistake
3. Try to find a way to untrust that command
4. Check `q settings --help`, `q --help`, configuration files
5. No clear method exists to manage trusted commands

### Environment

```yaml
[q-details]
version = "1.12.7"
hash = ""
date = "2025-07-22T17:41:04.597455Z (5d ago)"

[system-info]
os = "macOS 15.5.0 (24F74)"
chip = "Apple M2"
total-cores = 8
memory = "16.00 GB"

[environment]
cwd = ""
cli-path = ""
install-method = "unknown"

[env-vars]
QTERM_SESSION_ID = "e1c2b123e2a9488bab7952aa203caa00"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.12.7"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.todesktop.__"

[chat-settings]

[chat-trusted_tools]

[chat-failed_request_ids]
none

[chat-context]
current_profile=default
profiles=
default

global_context=
.amazonq/rules/**/*.md
README.md
AmazonQ.md

profile_context=none

files=none
```

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Inizia eseguendo `q settings --help` e `q --help`, quindi traccia il modo in cui il prompt `y/n/t` memorizza i comandi considerati attendibili e come viene utilizzata la directory di configurazione. Il lavoro è completato quando gli utenti possono elencare i comandi considerati attendibili, rimuovere un pattern specifico, cancellare tutti i comandi considerati attendibili e gestire queste impostazioni senza eliminare l’intera directory di configurazione.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
rust
Ambito
cli, security
Tipo di issue
Funzionalità
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Ferma
Chiarezza
Abbastanza chiara
Idoneità per principianti
35/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.