{"version":"2.1.321","anchor":"gh-jq-pre-validated-before-sending","canonical_anchor":"gh-jq-pre-validated-before-sending","heading":"gh commands with --jq are checked before anything is sent to GitHub","tier":"notice","area":"Bash","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/gh-jq-pre-validated-before-sending","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### gh commands with --jq are checked before anything is sent to GitHub\n\nA bad --jq filter on a gh command now stops it before the request is sent, and Claude Code warns if a rerun would repeat a change\n\n**What**\n\n`gh` is GitHub's command-line tool, and its `--jq` option filters the reply with a small query language called jq. When a `gh` command uses `--jq`, Claude Code now checks the filter first. If the jq on your machine cannot read it, the command stops and no request is sent.\n\nIf a request that changes something on GitHub was already sent and the filter then fails, Claude Code warns that running the command again will send that request again. Before, a filter problem showed up only after the request had been made.\n\n**Why**\n\nThis avoids accidentally repeating a change, such as creating the same comment or issue twice, just because the output filter was wrong.\n\n- Area: Bash\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}