aws / aws/amazon-q-developer-cli

kiro-cli-term is not running in this terminal, please try restarting your terminal

Offen
#3,534 3 Kommentare 5 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
Vorherrschende Sprache
Rust
Sterne
2k
Forks
439
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

### 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.8.0-87-generic - Ubuntu 22.04.5 LTS

### Expected behaviour

kiro-cli doctor command gives output:
✘ Kiro CLI terminal integrations: kiro-cli-term is not running in this terminal, please try restarting your terminal

✘ Doctor found errors. Please fix them and try again.

If you are not sure how to fix it, please open an issue with kiro-cli issue to let us know!

Basically the process kiro-cli-term is not getting run

### Actual behaviour

in .profile file kiro cli pre block is at the top of file, and when I try to add export PATH="$HOME/.local/bin:$PATH" above it, its moved below it in new terminal.

### Steps to reproduce

Remove q from /usr/bin/q, then ran kiro-cli using curl -fsSL https://cli.kiro.dev/install | bash

### Environment

```yaml

[q-details]
version = "1.21.0"
hash = "dc54efd85f411d6b4347d192733ff40650d38dfb"
date = "2025-11-26T22:30:26.062904Z (12d ago)"
variant = "minimal"

[system-info]
chip = "Intel(R) Xeon(R) W-2295 CPU @ 3.00GHz"
total-cores = 18
memory = "125.48 GB"

[system-info.os.linux]
kernel_version = "6.8.0-87-generic"
id = "ubuntu"
name = "Ubuntu"
pretty_name = "Ubuntu 22.04.5 LTS"
version_id = "22.04"
version = "22.04.5 LTS (Jammy Jellyfish)"

[environment]
cwd = "/home/USER"
cli-path = "/home/USER"
os = "Linux"
shell-path = "/usr/bin/bash"
shell-version = "5.1.16"
install-method = "unknown"
in-ssh = true

[env-vars]
DISPLAY = "localhost:12.0"
PATH = "/home/USER/.pyenv/shims:/home/USER/.pyenv/bin:/home/USER/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/opt/puppetlabs/bin:/home/USER/bin:/home/USER/report_tool/utilities/tools/collector/debian-scripts/report/"
SHELL = "/bin/bash"
TERM = "xterm"
XDG_SESSION_TYPE = "tty"
```

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Reproduziere die Installation unter Ubuntu, indem du q aus /usr/bin/q entfernst, das curl-Installationsprogramm ausführst und die generierten Einträge in .profile überprüfst. Führe q doctor und q restart in einem neuen Terminal aus; fertig ist es, wenn kiro-cli-term startet und die Überprüfung der Terminalintegration keinen Fehler mehr meldet.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
bash, rust
Bereich
cli, developer-experience
Issue-Typ
Bug
Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Aktivitätsstatus
Ruhig
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
52/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.