aws / aws/amazon-q-developer-cli

bug: CLI integration not working after autostart until manual restart

Open
#2,070 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

### Operating system

Linux 6.8.0-60-generic - Ubuntu 24.04.2 LTS

### Expected behaviour

When Amazon Q starts automatically via ~/.config/autostart/amazon-q.desktop, the CLI integration should work immediately, allowing `q` command with tab completion and proper shell integration in terminal.

### Actual behaviour

After system boot with Amazon Q autostart:
1. Amazon Q GUI appears in system tray and desktop
2. CLI command `q` with tab completion doesn't work in terminal
3. Shell integration is not active
4. After manually quitting Amazon Q from tray (Quit Amazon Q) and restarting it, CLI integration immediately starts working

The autostart process initializes the GUI but fails to activate shell/CLI integration components.

### Steps to reproduce

1. Set up Amazon Q autostart via ~/.config/autostart/amazon-q.desktop
2. Reboot the system
3. After boot, Amazon Q appears in tray and desktop
4. Open terminal and try `q ` + Tab or `q --help` - no completion/response
5. Right-click Amazon Q in tray → "Quit Amazon Q"
6. Restart Amazon Q manually (via desktop icon or appimage)
7. Try `q ` + Tab in terminal - now works perfectly

Note: Amazon Q automatically manages its .desktop file and removes any custom flags/parameters.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.