Summary
kiro-cli (AWS's agentic CLI at kiro.dev) does not expose a Claude Code-compatible statusLine command API. Like Codex CLI (#184), there's no mechanism to pipe session JSON to an external process for rendering.
Research findings
- No statusline plugin point: kiro-cli settings (
~/.kiro/settings/cli.json) have no statusLine field. The terminal UI has a built-in progress indicator but no external plugin hook.
- Hook system exists but insufficient: kiro-cli fires
preToolUse/postToolUse JSON-stdin hooks (docs), but these aren't a replacement for a persistent statusline command.
- Upstream demand exists: kirodotdev/Kiro#6929 requested a status bar showing credit usage (closed as duplicate, so the team is tracking it).
- Closed source: The kiro-cli binary is not open-source — we can't add the API ourselves.
- Usage data accessible via workaround:
kiro-cli chat --no-interactive "/usage" returns ANSI-formatted credit usage (as documented by CodexBar), but this isn't a real-time statusline feed.
Blocked on
kiro-cli shipping a statusLine command interface (or equivalent) that pipes session context JSON on stdin to an external process — the same mechanism Claude Code uses today.
Related
Summary
kiro-cli (AWS's agentic CLI at kiro.dev) does not expose a Claude Code-compatible
statusLinecommand API. Like Codex CLI (#184), there's no mechanism to pipe session JSON to an external process for rendering.Research findings
~/.kiro/settings/cli.json) have nostatusLinefield. The terminal UI has a built-in progress indicator but no external plugin hook.preToolUse/postToolUseJSON-stdin hooks (docs), but these aren't a replacement for a persistent statusline command.kiro-cli chat --no-interactive "/usage"returns ANSI-formatted credit usage (as documented by CodexBar), but this isn't a real-time statusline feed.Blocked on
kiro-cli shipping a
statusLinecommand interface (or equivalent) that pipes session context JSON on stdin to an external process — the same mechanism Claude Code uses today.Related