Summary
A Grok session launched inside Herdr runs both the Herdr-managed Grok SessionStart hook and the Herdr-managed Claude SessionStart hook imported through Grok's Claude compatibility layer.
Environment
- Windows 11
- Herdr 0.9.0 stable, protocol 22
- Grok Build 1.0.30
- Herdr integrations: Grok v1 and Claude v9
- Both providers are installed on the same user profile
Observed
A fresh Grok launch executed:
%USERPROFILE%\.grok\hooks\herdr-agent-state.ps1%USERPROFILE%\.claude\hooks\herdr-agent-state.ps1
Under concurrent startup load, the native Grok invocation took 15.685 seconds and the imported Claude invocation took 14.279 seconds, so both exceeded their generated 10-second timeout.
The commands use different provider-specific paths, so command-string deduplication cannot collapse them. That explanation is an inference from the observed configuration; the exact Grok compatibility merge logic has not been instrumented.
The Claude script may ultimately reject a Grok-shaped payload, but Windows still pays for another PowerShell process and stdin read. Disabling all Claude hook compatibility is not a safe workaround because repositories also rely on non-Herdr Claude-compatible safety hooks. Removing the native Grok hook risks losing the correct herdr:grok session identity.
Expected
When Grok loads Claude-compatible hooks, Herdr should execute one provider-appropriate SessionStart integration and report one herdr:grok session identity.
Possible fixes:
- Deduplicate Herdr integrations by managed integration identity rather than command path.
- Have the Grok integration suppress only the imported Claude Herdr hook.
- Provide a supported compatibility exclusion for a single imported hook.
Reproduction
- Install Herdr integrations for both Claude and Grok on Windows.
- Keep Grok's Claude hook compatibility enabled.
- Launch a fresh Grok with
herdr agent start.
- Inspect the Grok hook log for SessionStart commands.
Related: #3111 tracks the separate Windows 10-second timeout problem.
Summary
A Grok session launched inside Herdr runs both the Herdr-managed Grok SessionStart hook and the Herdr-managed Claude SessionStart hook imported through Grok's Claude compatibility layer.
Environment
Observed
A fresh Grok launch executed:
%USERPROFILE%\.grok\hooks\herdr-agent-state.ps1%USERPROFILE%\.claude\hooks\herdr-agent-state.ps1Under concurrent startup load, the native Grok invocation took 15.685 seconds and the imported Claude invocation took 14.279 seconds, so both exceeded their generated 10-second timeout.
The commands use different provider-specific paths, so command-string deduplication cannot collapse them. That explanation is an inference from the observed configuration; the exact Grok compatibility merge logic has not been instrumented.
The Claude script may ultimately reject a Grok-shaped payload, but Windows still pays for another PowerShell process and stdin read. Disabling all Claude hook compatibility is not a safe workaround because repositories also rely on non-Herdr Claude-compatible safety hooks. Removing the native Grok hook risks losing the correct
herdr:groksession identity.Expected
When Grok loads Claude-compatible hooks, Herdr should execute one provider-appropriate SessionStart integration and report one
herdr:groksession identity.Possible fixes:
Reproduction
herdr agent start.Related: #3111 tracks the separate Windows 10-second timeout problem.