Fixing Stupid Kiro issues on Linux for Developers.
A collection of practical, user-space fixes for problems that hit Kiro (and other VS Code-based agent IDEs) on Linux.
The Kiro agent runs a command, reports success (exit code 0), but captures no
output — the result is empty or replaced by a blob of shell metadata such as
type=shell;cwd=.... The command actually works (you can see it in the terminal,
and redirecting to a file works), but the agent can't "see" the result.
Root cause: Fedora's /etc/bashrc (and, on systemd v257+, /etc/profile.d/*.sh)
inject terminal escape sequences into every prompt via PROMPT_COMMAND / PS0
(terminal-title OSC 0, and systemd's OSC 3008 context sequence). These corrupt
the VS Code shell-integration markers (OSC 133 / OSC 633) that Kiro relies on to
delimit command output.
Fix: A small guard at the top of ~/.bashrc that gives Kiro agent terminals a
minimal prompt and returns early, before the global config injects competing escape
sequences. Fully user-space — no system files changed, shell integration stays on.
Symptoms / search terms:
Kiro execute_bash no output · Kiro agent command exit code 0 but empty output ·
Kiro terminal not capturing output Linux · Kiro command output empty Fedora ·
Kiro agent can't see terminal output · Kiro garbled output type=shell;cwd ·
start=...;machineid=...;bootid=...;type=shell;cwd=... leaking in terminal ·
Kiro shell integration broken Fedora · VS Code OSC 133 / OSC 633 markers corrupted ·
systemd OSC 3008 context sequence PROMPT_COMMAND · /etc/bashrc PROMPT_COMMAND
escape sequence · Kiro run command returns nothing · agent terminal output blank ·
Fedora 44 · bash 5.3.9 · Kiro 1.0.165
Found another Linux-specific Kiro issue and fix? Add a Markdown file under fixes/
and link it here with clear symptoms and search terms so others (and agents) can
find it.