Replies: 1 comment
|
This looks like a valid integration issue rather than a problem with Cursor itself. Since Cursor CLI loads A good fix would be for the Herdr Claude integration hook to first check the agent detected by Herdr and exit early when it isn't Ideally, the hook should only handle sessions where Herdr has actually identified the active agent as Claude. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem
The Cursor CLI (
cursor-agent) loads~/.claude/settings.jsonand executes the Claude Code hooks registered there.Why it matters
herdr-agent-state.ps1, SessionStart) also fires inside Cursor panes and reports--agent claudefor a pane that is actually running Cursor.idle-notify.ps1) also fire, showing "Claude Code" Windows notifications even when only Cursor is used.Related
Ideal outcome: the Claude integration hook should not act in panes where Herdr detects a different agent (e.g.
cursor).All reactions