amazon-q-developer-cli icon indicating copy to clipboard operation
amazon-q-developer-cli copied to clipboard

Cann't run in tmux

Open ichenhe opened this issue 1 year ago • 6 comments

Checks

Operating system

Linux 5.10.230-202.885.amzn2int.x86_64 - Amazon Linux 2

Expected behaviour

Amazon Q Cli completions should run as normal in tmux session.

Actual behaviour

Not run and q doctor reports errors

❯ q doctor

✘ Qterm Socket Check: Socket exists but could not connect: Connection refused (os error 111)


✘ 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. Install Amazon Q locally.
  2. Enable ssh integration.
  3. Amazon Q runs successfully on remote.
  4. Execute tmux on remote to open an session.
  5. Use as normal

Environment

[q-details]
version = "1.6.0"
hash = "6d13844d6546a5c29e7e121450af1130eb189e7f"
date = "2025-01-09T00:46:48.09362Z (2d ago)"
variant = "minimal"

[system-info]
chip = "AMD EPYC 9R14"
total-cores = 64
memory = "246.40 GB"

[system-info.os.linux]
kernel_version = "5.10.230-202.885.amzn2int.x86_64"
id = "amzn"
name = "Amazon Linux"
pretty_name = "Amazon Linux 2"
version_id = "2"
version = "2"
variant = "internal"

[environment]
cwd = "/local/home/USER"
cli-path = "/local/home/USER"
os = "Linux"
shell-path = "/local/home/USER/.toolbox/tools/toolbox/1.1.1651.0/toolbox-exec"
shell-version = "5.8"
install-method = "toolbox"
in-ssh = true

[env-vars]
PATH = "/home/USER/.local/share/mise/installs/node/18.20.2/bin:/home/USER/.local/share/mise/installs/python/3.12.7/bin:/home/USER/.local/share/mise/installs/python/3.11.10/bin:/home/USER/.local/share/mise/installs/python/3.10.15/bin:/home/USER/.local/share/mise/installs/python/3.9.20/bin:/home/USER/.local/share/mise/installs/python/3.8.20/bin:/home/USER/.local/share/mise/installs/ruby/2.7.8/bin:/home/USER/.toolbox/bin:/usr/lib/jvm/java-17-amazon-corretto.x86_64/bin:/home/USER/.toolbox/bin:/usr/lib/jvm/java-17-amazon-corretto.x86_64/bin:/home/USER/.cargo/bin:/usr/local/bin:/usr/bin:/home/USER/bin:/usr/local/sbin:/usr/sbin:/home/USER/.local/bin:/home/USER/bin:/apollo/env/envImprovement/bin:/apollo/env/AmazonAwsCli/bin/:/home/USER/bin:/apollo/env/envImprovement/bin:/apollo/env/AmazonAwsCli/bin/"
QTERM_SESSION_ID = "4219d93f89bd4b9d963b4f09861e11f5"
Q_PARENT = "/tmp/q-parent-92e543f5b978

ichenhe avatar Jan 10 '25 17:01 ichenhe

I can reproduce the issue, one way to resolve it temporarily is to manually run qterm inside of tmux, that will launch out process which should make it work..

grant0417 avatar Jan 10 '25 21:01 grant0417

@grant0417

After run qterm, q doctor checks succeed, but cli completions still not work (no popup window).

ichenhe avatar Jan 11 '25 11:01 ichenhe

After run qterm, q doctor checks succeed, but cli completions still not work (no popup window).

+1 same issue.

fluency03 avatar Mar 11 '25 16:03 fluency03

+1 same issue

dattatre263 avatar May 09 '25 16:05 dattatre263

I'm experiencing problems running Q under tmux on macOS. My entire setup is tmux + Alacritty + Fish shell.

mhausenblas avatar Jul 21 '25 11:07 mhausenblas

I exported the correct Q_TERM in my tmux session and still not working.

I also restarted terminal numerous times

cruzluna avatar Dec 01 '25 18:12 cruzluna