[BUG] jq -f always prompt for permissions

Resolved 💬 4 comments Opened Feb 16, 2026 by Izeren Closed Mar 17, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Description

jq -f <filter-file> <input-file> is blocked by the permission system even when explicitly allowlisted.

What Should Happen?

Expected Behavior

jq -f ... should match against Bash(jq *) or the more specific Bash(jq -f ...) pattern and auto-approve without prompting.

Actual Behavior

  • jq -f ... shows a reduced approval prompt (Yes/No only, no allowlist option).
  • jq '.' <file> works fine and matches Bash(jq *).

Environment

  • Claude Code CLI
  • macOS

Error Messages/Logs

Steps to Reproduce

Steps to Reproduce

  1. Add the following to settings.json permissions allow list:

``json
"Bash(jq *)",
"Bash(jq -f ~/projects/myproject/.tmp/* ~/projects/myproject/.tmp/*)"
``

  1. Ask Claude to run:

``bash
jq -f ~/projects/myproject/.tmp/filter.jq ~/projects/myproject/.tmp/data.json
``

  1. The approval prompt is shown, but only offers "Yes" or "No" — without the usual option to allow similar commands or the specific command.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.44

Platform

Google Vertex AI

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

_No response_

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗