Files
orca/config
Brennan Benson 8ea5dd80c3 fix(antigravity): install a PreToolUse status hook without deciding tool permissions (#14701)
* fix(antigravity): install a PreToolUse status hook without deciding tool permissions

Antigravity is the only supported agent with no pre-tool signal, so its panes
show a bare "Working" spinner for the whole tool call instead of the live
"Working - <tool>(<input>)" readout every other agent gets.

The consumer side already handles it — extractAntigravityToolFields and
normalizeAntigravityEvent parse PreToolUse (including the `waiting` state for
ask_question/ask_permission) and are covered by tests. Only the installer was
missing the event.

PreToolUse was installed originally and removed in a480e6b7 (#2501) because the
observational `{}` response violates Antigravity's schema and is read as a deny
(#2426). Re-add it with the one documented decision that defers to the user's
permission config rather than overriding it:

- `ask` — "Prompts the user, but respects 'Always Allow' settings."
- `allow` — "Automatically allows the tool execution." (would silently
  auto-approve every tool call Orca observes)

The hooks.json guard for a missing managed script previously drained stdin and
printed nothing, which is exactly the #2426 deny. Gate events now emit their
response from the guard too, so a swept ~/.orca cannot brick tools on a host
whose ~/.gemini/config/hooks.json survives.

Fixes #12898

* fix(antigravity): list posix-hook-command.ts in the CLI typecheck project

The CLI project enumerates its main-side files explicitly, so the extracted
module needs an entry alongside its sibling runtime-home-hook-command.ts.
2026-08-18 00:44:56 -07:00
..
2026-08-05 12:09:24 -07:00