Files
orca/src/shared/program-status
Dongho LeeandKelvin Amoaba 828e5bd0c9 fix(kiro): keep the Kiro session when kiro-cli reports status over OSC 7501 (#40568)
* fix(kiro): keep the Kiro session when kiro-cli reports status over OSC 7501

kiro-cli's TUI reports its state over OSC 7501 as `app=kiro-cli`, while
Orca's Kiro hooks, resume records and cold restore all use the agent id
`kiro`. The projector passed the app id through unmapped, so one Kiro pane
was tracked as two agents:

- a `kiro-cli` report that followed a finished `kiro` hook row took the row
  over as a different program and dropped its provider session;
- while a `kiro-cli` row was live, `kiro` hooks were treated as a nested CLI
  and their session id was not recorded.

`kiro-cli` is not a resumable agent id, so no resume record was kept and a
restarted Orca reopened Kiro tabs as plain shells instead of running
`kiro-cli --resume-id <id>`.

Map the app id to `kiro`, as `claude-code` and `grok-build` already are.

* docs(agent-hooks): list Kiro as an OSC 7501 sender reporting as kiro-cli

---------

Co-authored-by: Kelvin Amoaba <97001695+AmoabaKelvin@users.noreply.github.com>
2026-11-11 05:09:17 +00:00
..
…