AX-1579 - Add shell-mismatch troubleshooting note for Agent Guard#38
Closed
MatanEden1 wants to merge 1 commit into
Closed
AX-1579 - Add shell-mismatch troubleshooting note for Agent Guard#38MatanEden1 wants to merge 1 commit into
MatanEden1 wants to merge 1 commit into
Conversation
Env vars exported to one shell's rc file can be invisible to the shell Cursor actually launches with, silently preventing Agent Guard from activating. Point users at checking that mismatch. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Collaborator
Author
|
will not be implemented |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a one-line troubleshooting note to
README.md: if Agent Guard isn'tactivating, make sure environment variables are defined in the same shell
your IDE launches with.
Why
Confirmed on a real setup: env vars were correctly exported to
~/.zshrc,but Cursor launches hooks/agent commands under bash by default on that
machine, so neither the
sessionStarthook nor the agent's shell commandsever saw them — despite the vars working fine in the user's own terminal.
This is a documentation-only fix pointing users at that mismatch rather
than a code change.
Test plan