aws / aws/amazon-q-developer-cli
failed to retrieve governance settings — MCP and web tools disabled
- Langage dominant
- Rust
- Étoiles
- 2k
- Forks
- 439
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
### 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
Linux 6.12.100-125.179.amzn2023.x86_64 - Ubuntu 24.04.4 LTS
### Expected behaviour
A profile is loaded and kiro executes without issue
### Actual behaviour
No profile is loaded and I can login but kiro is not functional
### Steps to reproduce
just login with:
$kiro-cli login --use-device-flow
✔ Select login method · Use with Your Organization
✔ Enter Start URL · https://d-9367077c28.awsapps.com/start
✔ Enter Region · eu-west-1
### Environment
```yaml
[q-details]
version = "2.20.1"
hash = "dc1a243b88b0ba6c216ff345363f02b7a9c5884d"
date = "2026-08-27T07:20:26.409931Z (5d ago)"
variant = "minimal"
[system-info]
chip = "Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz"
total-cores = 4
memory = "62.10 GB"
[system-info.os.linux]
kernel_version = "6.12.100-125.179.amzn2023.x86_64"
id = "ubuntu"
name = "Ubuntu"
pretty_name = "Ubuntu 24.04.4 LTS"
version_id = "24.04"
version = "24.04.4 LTS (Noble Numbat)"
[environment]
cwd = "/home/USER/uegrouping/uegrouping_ideaproposal"
cli-path = "/home/USER/uegrouping/uegrouping_ideaproposal"
os = "Linux"
shell-path = "/usr/bin/bash"
shell-version = "5.2.21"
terminal = "VSCode"
install-method = "unknown"
[env-vars]
PATH = "/home/USER/java17/bin:/home/USER/.local/bin:/opt/conda/share/sagemaker-code-editor/bin/remote-cli:/opt/conda/bin:/opt/conda/condabin:/etc/sagemaker-inference-server:/opt/conda/condabin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/USER/.local/bin"
Q_SET_PARENT_CHECK = "1"
SHELL = "/bin/bash"
TERM = "xterm-256color"
```
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Le point d’entrée signalé est `kiro-cli login --use-device-flow` ; commencez par le reproduire et examinez la sortie de `q doctor` après `q restart`. Le travail est terminé lorsque le profil se charge correctement et que les outils MCP et web de kiro sont disponibles.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- aws, linux
- Domaine
- authentication, authorization, cli
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- Active
- Clarté
- Plutôt claire
- Accessibilité débutants
- 48/100