grep tool ignores per-pattern deny permission rules

[CryptoSiD]

Description

Per-pattern permission rules defined under "grep" in opencode.json are not enforced.
Files set to "deny" in the grep rules still return their content when matched. The same pattern-based rules work correctly under "read" and "glob".

Expected behavior: grep should block matches inside files matching denied patterns, showing a permission denied message — the same way read and glob do.

Additional context: "read" and "glob" per-pattern rules work as expected with identical pattern syntax. The file include filter on grep appears to bypass the permission check entirely.

Plugins

None

OpenCode version

1.17.13

Steps to reproduce

1. Create a project with .opencode/opencode.json:
   {
   "permission": {
   "grep": {
   "": "allow",
   "/config.php": "deny"
   }
   }
   }
2. Create config.php with any content
3. Run: grep with "pattern": "any-string", "include": "config.php"
4. The config.php content is returned — no permission block

Screenshot and/or share link

No response

Operating System

Ubuntu 26.10

Terminal

Tabby

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• Granular read permission deny rules don't block file access (patterns never match) #28150: Granular per-pattern deny rules don't block file access for read, glob, and grep tools
• The Read, Glob, and Grep tools do not verify these rules before execution. #29674: The Read, Glob, and Grep tools do not verify permission rules before execution

These issues report the same or closely related behavior where pattern-based deny rules in the permission config are not enforced at the tool level.