aws / aws/amazon-q-developer-cli

Amazon Q terminal integrations: qterm is not running in this terminal, please try restarting your terminal

Open
#3,888 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
2k
Forks
439
PR merge metrics
No merged PRs in 30d

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

### Expected behaviour

It's simple, can use Amazon Q CLI 1.19.7 without fail as I already using Amazon Q CLI 1.15.0. I want to use Amazon Q CLI (Not Kiro).

### Actual behaviour

I'm facing to use q, echo `Q_TERM`, see the output below:

```
echo "Q_TERM=$Q_TERM"
q doctor
Q_TERM=

✘ Amazon Q terminal integrations: qterm is not running in this terminal, please try restarting your terminal

Q_TERM=

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

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

```

### Steps to reproduce

**1. Download Amazon Q CLI**
```
cd ~/Downloads

curl --proto '=https' --tlsv1.2 -sSf \
https://desktop-release.q.us-east-1.amazonaws.com/latest/q-x86_64-linux.zip \
-o q-x86_64-linux.zip
```

**Verify:**

`ls -lh q-x86_64-linux.zip`
**2. Extract**
```
unzip -o q-x86_64-linux.zip
```
**Install correctly**
**Run:**

```
cd ~/Downloads/q
chmod +x install.sh
./install.sh
```

If it asks to modify your shell configuration, choose **Yes**.

**Then reload Bash:**

```
source ~/.bashrc
hash -r

```
**Verify**
```
which q
q --version
```

**Then verify the chat binary:**

```
which qchat
qchat --version
```

**Also:**

`q doctor`

I tried all the possible fixes along with `q integrations reinstall dotfiles` and nothing is helped me..

Thanks in advance..!

### Environment

```yaml

[q-details]
version = "1.19.7"
hash = "b654a1beb880951dd2343120bb867659622eecd9"
date = "2025-11-15T20:13:03.579285Z (270d ago)"
variant = "minimal"

[system-info]
chip = "12th Gen Intel(R) Core(TM) i5-1235U"
total-cores = 10
memory = "15.30 GB"

[system-info.os.linux]
kernel_version = "6.8.0-136-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/Downloads/q"
cli-path = "/home/USER/Downloads/q"
os = "Linux"
shell-path = "/usr/bin/bash"
shell-version = "5.1.16"
terminal = "Gnome Terminal"
install-method = "unknown"

[env-vars]
DISPLAY = ":1"
GTK_IM_MODULE = "ibus"
PATH = "/home/USER/.config/inkscape/extensions/inkstitch/bin:/home/USER/.config/inkscape/extensions/inkstitch/bin:/home/USER/.config/inkscape/extensions/inkstitch/bin:/home/USER/.config/inkscape/extensions/inkstitch/bin:/home/USER/.nvm/versions/node/v20.11.1/bin:/home/USER/.local/bin:/home/USER/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/snap/bin:/home/USER/.dotnet/tools:/home/USER/.local/bin:/home/USER/bin:/opt/sonar-scanner/bin:/home/USER/.dotnet/tools:/home/USER/bin:/opt/sonar-scanner/bin:/home/USER/.dotnet/tools:/home/USER/bin:/opt/sonar-scanner/bin:/home/USER/.dotnet/tools:/home/USER/bin:/opt/sonar-scanner/bin:/home/USER/.dotnet/tools"
QTERM_SESSION_ID = "1688468a23eb415286c8af9c200f9a8b"
QT_IM_MODULE = "ibus"
Q_SET_PARENT_CHECK = "1"
SHELL = "/bin/bash"
TERM = "xterm-256color"
XDG_CURRENT_DESKTOP = "ubuntu:GNOME"
XDG_SESSION_DESKTOP = "ubuntu"
XDG_SESSION_TYPE = "x11"
XMODIFIERS = "@im=ibus"
```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the empty Q_TERM result with q doctor in the documented Ubuntu 22.04 Bash and GNOME Terminal setup. Read the q restart and q integrations reinstall dotfiles entry points, then compare the installed q 1.19.7 behavior with the reported qterm integration state. Done means the terminal integration initializes and q doctor no longer reports that qterm is not running.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash, linux, rust
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.