docs(troubleshooting): document jq fail-closed guard deadlock on fresh setup - #106
Merged
Conversation
…h setup omind setup checks for jq but does not install it; the '*' OMI-compliance guard (omi-guard.sh) fails closed when jq is absent, blocking every tool call and creating a bootstrap deadlock. Document the symptoms, root cause, recovery (edit settings.json -> install jq -> restore), and the real fix. Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
CryptoJones
pushed a commit
that referenced
this pull request
Jul 20, 2026
…4.0.0)' (#106) from feat/ai-token-usage into main
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
1 participant
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 troubleshooting section documenting a bootstrap deadlock: on a machine without
jq,omind setupwires the"*"OMI-compliance guard (omi-guard.sh), which fails closed whenjqis absent. Because the matcher is"*", the very next tool call — and every one after — is blocked, including theBashcall needed to installjq.Why
omind setupchecks forjqbut does not install it, and on a clean boxjqis usually missing. The fail-closed behavior is deliberate (per CHANGELOG) and correct for safety, but nothing documents how to recover once wedged, and the block message doesn't name the fix.Contents (
docs/troubleshooting.md)omi-guard: jq not found … BLOCKINGerror; note that"*"blocks all tools, not just Bash.git-fresh-base.sh,omi-guard-hermes.sh)."*"/omi-guard.shblock → installjq→ restore the block →omind doctor.setupshould installjqwith the guard (as it bootstrapsuv/Python), or refuse to install the fail-closed guard whenjqis absent, or at minimum make the block message name the recovery.Docs-only; no code changes.
🤖 Generated with Claude Code