[nwparker]

	Files	Added	Deleted	Net
Test	4	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​260	$\color{#cf222e}{\Huge{\mathbf{−}}}$​5	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​255
Prod	7	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​271	$\color{#cf222e}{\Huge{\mathbf{−}}}$​22	$\color{#1a7f37}{\Huge{\mathbf{+}}}$​249

ELI5

Kiro's next engine (V3) is turned on by --v3, and kiro-cli 2.30+ prompts users to switch to it. It becomes the default in Kiro CLI 3.0. On V3, Orca shows no Kiro status, for two reasons: V3 sends hook event names Orca doesn't recognise, and Kiro's built-in default agent never runs Orca's hooks. This PR teaches Orca the V3 event names. It also installs one global V3 hooks file that covers every agent, including the built-in default.

This adopts @LDH1103's #24937, with their commits kept, merged onto current main and trimmed. On top of that is one fix-up commit.

What Changed

• normalizeKiroEvent now accepts V3's PascalCase names. UserPromptSubmit/PreToolUse/PostToolUse mean working, and Stop/SessionEnd mean done. SessionStart is ignored because V3 fires it lazily, right before the first prompt. The camelCase V2 mapping is unchanged.
• KiroHookService.install() / installRemote() also write orca-agent-status.json (Kiro's version: "v1" standalone format) into Kiro's global hooks dir. It runs the same managed kiro-hook script. A file at that name with anything Orca didn't write is left alone and reported. remove() deletes the file, or strips only Orca's entries from a mixed file.
• Fix-up on top of feat(kiro): report V3 engine (--v3) status through a global standalone hooks file #24937:
  • The V3 file now follows KIRO_HOME (resolveKiroHomeDir(), or the probed remote KIRO_HOME) instead of always going to ~/.kiro. kiro-cli 2.31 changelog: "extends KIRO_HOME across V3 configuration and state".
  • With no custom agent, the status is partial rather than not_installed, because the V3 file does cover the default agent.
  • Dropped the unrelated resume and docs churn, shortened comments to repo style and trimmed the tests.

Why

• V3 event names, from Kiro's migration doc https://kiro.dev/docs/cli/v3/hooks-migration.md: agentSpawn→SessionStart, userPromptSubmit→UserPromptSubmit, preToolUse→PreToolUse, postToolUse→PostToolUse, stop→Stop. Payloads captured by the reporter on kiro-cli 2.33 (Kiro status hooks are dropped when Kiro runs its V3 engine (--v3): PascalCase hook_event_name, and the default agent never gets hooks #31577) match.
• Global standalone hooks run in every workspace for every agent on V3. That makes them the only way to reach the built-in kiro_default, which has no file to patch.
• Probed in isolated temp homes, using a placeholder invalid KIRO_API_KEY so no model call can succeed:

kiro-cli	Engine	Hooks file location	Fires?
2.29.0	--v3	$HOME/.kiro/hooks with KIRO_HOME=alt	yes (SessionEnd)
2.29.0	--v3	$KIRO_HOME/hooks only	no
2.34.0	--v3	$KIRO_HOME/hooks only	yes (SessionEnd)
2.34.0	--v3	$HOME/.kiro/hooks with KIRO_HOME=alt	no
2.34.0	default (V2), custom agent with hooks, plus the V3 file	agent hooks only (userPromptSubmit)	the V3 file does not fire, so no double report on V2

kiro-cli 2.34.0 (chat --help) describes --v2 as "the pre-3.0 default". The changelog for 2.30.0 says V3 "becomes the default with CLI 3.0 at the end of October".

Linked Issue

Fixes #31577
Refs #24177, #7693. These are covered once the pane runs V3. On the V2 engine, Kiro's built-in default agent still cannot carry hooks, and the status detail says so.

Visual Proof

N/A. This adds no UI. It feeds the existing agent status rows.

Testing

• I manually tested these changes locally

• Automated tests added/updated

• Real code path on macOS: ran KiroHookService.install() against an empty temp HOME, which wrote the script and ~/.kiro/hooks/orca-agent-status.json with no custom agent. Then ran kiro-cli 2.34.0 chat --v3 --no-interactive with an env stripped of ORCA_* and pointed at a local capture server. The server received POST /hook/kiro {"session_id":"sess_…","hook_event_name":"SessionEnd",…}. On main there is no file, and SessionEnd/Stop would map to null.

• pnpm test src/main/kiro src/shared/agent-hook-listener src/main/agent-hooks passes. pnpm tc and check:code-quality:changed are clean.

• Not verified: a full V3 turn (UserPromptSubmit/PreToolUse/Stop) needs a Kiro account. Those payload shapes come from Kiro status hooks are dropped when Kiro runs its V3 engine (--v3): PascalCase hook_event_name, and the default agent never gets hooks #31577 (2.33) and feat(kiro): report V3 engine (--v3) status through a global standalone hooks file #24937 (2.27, Windows).

Review

Risk is low to medium.

• The change writes one new file in the user's Kiro hooks dir. It never overwrites a file it didn't write.
• On V3, a custom agent that still has Orca's agent-config hooks may also fire the global file. Kiro then reports each event twice. Both copies carry the same state, so the status is the same, just sent twice.
• Remote (SSH) install writes the same file under the remote KIRO_HOME or ~/.kiro.
• Windows uses the existing .cmd launcher command. That launcher was verified on Windows in feat(kiro): report V3 engine (--v3) status through a global standalone hooks file #24937 (2.27.1). This branch was not re-run on Windows.

Co-authored-by: LDH1103 ldh517525@gmail.com

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 13 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 10 included reviews currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Repository UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: d501a790-cbd2-4e04-90f1-73837fc54046

Commits

Reviewing files that changed from the base of the PR and between 47ed6e1 and 52f7982.

Files selected for processing: 11

• src/main/kiro/hook-service.test.ts
• src/main/kiro/hook-service.ts
• src/main/kiro/hook-settings.ts
• src/main/kiro/standalone-hook-settings.ts
• src/main/kiro/standalone-hooks-remote.test.ts
• src/main/kiro/standalone-hooks.test.ts
• src/main/kiro/standalone-hooks.ts
• src/shared/agent-hook-listener/provider-event-routing.ts
• src/shared/agent-hook-listener/providers/kiro-events.test.ts
• src/shared/agent-hook-listener/providers/kiro-events.ts
• src/shared/agent-hook-listener/providers/kiro-tool-fields.ts

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}