feat(cli): relay Stop, PostToolUse and PreToolUse to Antigravity (agy), not only SessionStart

Ouverte
#1,194 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
44/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript
Domaine
cli

Piste de recherche

Start with cli/src/contexts/tools/domain/profiles/antigravity/antigravity-hooks.ts and its MAPPED_EVENTS, then read tool-paths.md and the prior hook work in #890, #511, and #978. Verify how the profile maps event names, matchers, and hook outputs against the observed agy contracts, including PostInvocation context injection. Done means the acceptance criteria pass, including a guarded Stop continuation and an allow response for empty PreToolUse output.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Problem

On next, the Antigravity profile relays only SessionStart (cli/src/contexts/tools/domain/profiles/antigravity/antigravity-hooks.ts, MAPPED_EVENTS), with the reason "Claude and agy name their tools differently". tool-paths.md lists PreToolUse, PostToolUse and Stop as supported by the host. A hook on any of those three does nothing on agy.

Measured on 2026-11-11 with agy -p (1.5.x, the binary auto-updated from 1.5.1 to 1.5.5 during the test), project file .agents/hooks.json, disposable folder:

  • SessionStart, PreToolUse, PostToolUse, Stop all fire. agy also has PreInvocation and PostInvocation. It has no UserPromptSubmit, SubagentStop or SessionEnd.
  • Tool names differ: write_file (args Path, Content) and run_command (args CommandLine), not Write and Bash.
  • Output contract differs from the framework's scripts: a Stop hook continues the agent with {"decision":"continue","reason":...}. An empty output from a PreToolUse hook is a denial, so a script that prints nothing blocks every tool call. {"decision":"allow"} is required.
  • PostToolUse could not inject context (documented as {} only). PostInvocation injected it with {"injectSteps":[{"systemMessage":{"systemMessage":"..."}}]}.
  • In -p, tools are refused unless permissions are skipped, which matters for CI.
  • Not tested: --settings, subagent hooks. One run per test, small model.
Scope
  • Relay Stop and PostToolUse (and PreToolUse once its output contract is handled) to agy, with matchers translated (Bash to run_command, Write and Edit to write_file).
  • Translate the hook output (block to continue, an empty PreToolUse output to allow), or document that scripts must handle it.
  • Decide how PostToolUse context injection works on agy (PostInvocation).
Acceptance criteria
  • A Stop script that blocks once continues the turn on agy, with a guard that stops the loop.
  • A PostToolUse script runs after write_file and run_command.
  • A PreToolUse script that prints nothing does not deny every tool call.
  • Events the profile does not relay produce a warning at build time (today: the unmapped event message already exists for the profile).
Prior art in this repo
  • antigravity-hooks.ts (MAPPED_EVENTS = {"SessionStart"}), #890 (hooks are read from hooks.json, not settings.json), #511 (Antigravity as a flat host), #978 (verified tool compatibility).
Out of scope

Telling agy to relay UserPromptSubmit or SessionEnd (they do not exist). The Antigravity IDE.

Langage dominant
TypeScript
Étoiles
481
Forks
45
Merge moyen
1 j 13 h
PR mergées (30 j)
91

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de ai-driven-dev/framework

Toutes les issues de ai-driven-dev/framework

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.