aws / aws/amazon-q-developer-cli

github authenticated non enterprise user requires profileArn

Aperta
#3,696 2 commenti 4 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

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 26.2.0 (25C56)

### Expected behaviour

I am able to use Kiro-cli post authentication.

### Actual behaviour

Currently I am unable to use Kiro-cli post authentication due to the following error:

```shell
Kiro is having trouble responding right now:
0: Failed to send the request: An unknown error occurred: profileArn is required but no profiles are available. Please log in and select a profile.
1: An unknown error occurred: profileArn is required but no profiles are available. Please log in and select a profile.

Location:
crates/chat-cli/src/cli/chat/mod.rs:1647

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
```

Notably, the IDE works as expected. Some key details:

- GitHub-authenticated (non-enterprise) user
- kiro-cli whoami works fine
- kiro-cli chat fails with profileArn is required but no profiles are available
- The IDE works perfectly with the same account
- The IDE stores the profile at ~/Library/Application Support/Kiro/User/globalStorage/kiro.kiroagent/profile.json but the CLI never populates an equivalent

### Steps to reproduce

Log in using GitHub SSO as a non enterprise user. The CLI should throw the listed response.

I am receiving this error after re-authentication, trying to doctor, and reinstalling the cli.

### Environment

```yaml

[q-details]
version = "1.28.2"
hash = "27868a6e6508e32a80d15e6eba2f6adbab6c2aa7"
date = "2026-03-27T00:14:48.847531Z (23h ago)"
variant = "full"

[system-info]
os = "macOS 26.2.0 (25C56)"
chip = "Apple M4 Pro"
total-cores = 12
memory = "48.00 GB"

[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "macOS"
install-method = "unknown"

[env-vars]
PATH = "/Users/USER/.nvm/versions/node/v24.12.0/bin:/Users/USER/.local/bin:/opt/homebrew/opt/openjdk/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/opt/pmk/env/global/bin:/Users/USER/.cargo/bin:/Users/USER/.local/bin:/Users/USER/Library/Application Support/JetBrains/Toolbox/scripts"
QTERM_SESSION_ID = "9d7de98f5d3042a1b0ce438249fd8895"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.28.2"
SHELL = "/bin/zsh"
TERM = "xterm-256color"
__CFBundleIdentifier = "com.apple.Terminal"
```

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Direzione di ricerca

Inizia da crates/chat-cli/src/cli/chat/mod.rs:1647 e traccia il modo in cui gli utenti GitHub autenticati ottengono o selezionano un profilo prima dell’invio delle richieste di chat. Confronta la gestione dei profili della CLI con il percorso profile.json dell’IDE menzionato nell’issue, quindi riproduci il problema con un account GitHub SSO non Enterprise. Il lavoro è completato quando kiro-cli chat funziona dopo l’autenticazione senza l’errore profileArn.

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

Valutazione

Stack tecnologico
rust
Ambito
authentication, cli
Tipo di issue
Bug
Difficoltà
3/5
Tempo stimato
1-2 giorni
Stato di attività
Tranquilla
Chiarezza
Abbastanza chiara
Idoneità per principianti
58/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.