@ev-ai/agent-hook 1.3.2 → 1.3.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (9) hide show
  1. package/README.md +2 -0
  2. package/dist/cli.mjs +38 -36
  3. package/dist/hook.mjs +35 -33
  4. package/dist/launcher-update.mjs +4 -4
  5. package/dist/launcher.mjs +3 -3
  6. package/dist/managed-hooks-snippet.cjs +1 -1
  7. package/dist/managed-hooks-snippet.mjs +1 -1
  8. package/dist/plugin-hooks.mjs +1 -1
  9. package/package.json +1 -1
package/README.md CHANGED
@@ -106,6 +106,8 @@ Keep Claude and Cursor both wired. Cursor also loads `.claude/settings.json` as
106
106
 
107
107
  Stacked configs for the **same** runner (user-level `~/.cursor/hooks.json` plus project `.cursor/hooks.json`, or plugins enabled alongside file wiring) also fire twice. The hook collapses those to one collect + POST via a short-lived cross-process claim under `~/.ev-ai/agent-hook/claims/` (keyed by platform, session, event, turn / `tool_use_id`, and a local hash of call-identifying stdin when `tool_use_id` is absent — so distinct Cursor shell/read/edit calls in one turn are not treated as duplicates). Weak payloads without a strong id fail open (both may post). Disable by setting `EVENT_CLAIM_DEDUP_ENABLED` to `false` in source — needed if two configs for the same runner intentionally target **different** collector URLs (the claim key does not include the URL, so only one would deliver).
108
108
 
109
+ **Concurrency cap.** At most `max_concurrent_hooks` hook processes (set in `~/.ev-ai/config.json`; default 4 on Windows, 10 elsewhere) collect and POST at the same time. Each one holds a slot file under `~/.ev-ai/agent-hook/slots/`. An event that arrives while every slot is held is dropped: the runner still gets its normal ack and nothing is posted. Session start and end events are never capped. A value that is not a positive integer falls back to the default, and any slot-file error fails open (the event is collected).
110
+
109
111
  Wired command shape (auth is in the committed `collector_url`). The per-event command is **pinned to the installer's version** (not `@latest`):
110
112
 
111
113
  ```bash