aws / aws/amazon-q-developer-cli
Kiro CLI --v3: clipboard paste broken, context limit kills session, compaction hangs
- 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.17.0-35-generic - Ubuntu 24.04.4 LTS
### Expected behaviour
1. Ctrl+V / /paste inserts image from clipboard (works fine without --v3)
2. When context limit is reached — ability to save/export transcript before session ends
3. Compaction doesn't hang CLI, can be interrupted
4. Text color in --v3 UI should have sufficient contrast for readability
### Actual behaviour
1. --v3: Ctrl+V and /paste → "No image in clipboard". Without --v3 — works. 100% reproducible.
2. ~60% context usage → agent refuses to work, demands new session. No way to save history.
3. Auto-compaction → CLI hangs, unresponsive to Ctrl+C, have to kill process.
4. --v3 UI text color has very poor contrast (gray on dark background) — hard to read.
### Steps to reproduce
1. Copy screenshot to clipboard → kiro-cli --v3 → Ctrl+V or /paste → "No image in clipboard"
Then exit, run kiro-cli (without --v3) → Ctrl+V → image pastes fine
2. Work in --v3 session until ~60% context → agent refuses to continue
3. Work until auto-compaction triggers → CLI becomes unresponsive
4. Launch kiro-cli --v3 → observe low contrast text color in the UI
### Environment
```yaml
[q-details]
version = "2.10.0"
hash = "a5da029503141c8033a11d7ee6569583d915cd90"
date = "2026-06-25T20:04:08.842604Z"
variant = "minimal"
[system-info]
chip = "Intel(R) Core(TM) Ultra 7 155H"
total-cores = 16
memory = "62.26 GB"
[system-info.os.linux]
kernel_version = "6.17.0-35-generic"
id = "ubuntu"
name = "Ubuntu"
pretty_name = "Ubuntu 24.04.4 LTS"
version_id = "24.04"
version = "24.04.4 LTS (Noble Numbat)"
[environment]
cwd = "$HOME"
cli-path = "$HOME"
os = "Linux"
shell-path = "$HOME/.local/share/kiro-cli/node"
install-method = "unknown"
[env-vars]
DISPLAY = ":1"
PATH = "$HOME/maven/default/bin:$HOME/.local/lib/nodejs/default-nodejs/bin:$HOME/.npm-global/bin:$HOME/jvm/default-java/bin:$HOME/.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/.local/bin"
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
Research direction
Start by reproducing each of the four failures with kiro-cli --v3 on the reported Ubuntu environment, comparing clipboard behavior with the non-v3 command and recording where context refusal, compaction, or rendering becomes unusable. Done would require separately verifying image paste, transcript preservation at the context limit, interruptible compaction, and readable UI text.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100