fix(core): match absolute permission rules for relative paths - #53365

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

The following comment was made by an LLM, it may be inaccurate:

Thanks for updating your PR! It now meets our contributing guidelines. 👍

Adding a v2.2.1 observation for the absolute-path case in this PR.

On macOS, in the native standalone TUI, I configured absolute read and edit deny rules for an inert file inside the project. The native read returned its contents. A valid native edit requested approval instead of being denied. I rejected the edit and independently checked that the file remained unchanged.

I then changed only the three canary resource strings to project-relative spelling, kept the same binary, model and project, and restarted the isolated TUI. The native read and edit of the denied fixture both returned policy errors without an approval prompt:

Permission denied: read
Permission denied: edit

The denied fixture's SHA-256 remained unchanged. The working resource string for both deny rules is:

.tmp/native-v2-self-cutover/synthetic/denied.txt

Sanitized excerpt from the agent configuration, with the project root replaced by a placeholder:

{
  "agents": {
    "build": {
      "permissions": [
        {
          "action": "read",
          "resource": "/absolute/path/to/project/.tmp/native-v2-self-cutover/synthetic/denied.txt",
          "effect": "deny"
        },
        {
          "action": "edit",
          "resource": "/absolute/path/to/project/.tmp/native-v2-self-cutover/synthetic/denied.txt",
          "effect": "deny"
        }
      ]
    }
  }
}

Separate headless debug agents output included those absolute rules on Build. That was not an inspection of the same private server used by the TUI.

The v2.2.1 sources appear to explain the result:

• FileAccess.resolve returns a location-relative permission resource for an internal file, even when the tool input is absolute.
• Permission.evaluate wildcard-matches that resource against the rule text without resolving an absolute rule against the location.

The relative spelling works in this configuration. I am reporting this as a v2.2.1 confirmation of the absolute-path case covered by this PR, rather than a TUI-specific permission bypass.

Limits: both variants retained project configuration and plugins, including the cmux OpenCode integration and a local shell guard. This is not a plugin-free minimal reproduction. Neither control used the shell guard to produce the native file-tool denials. No secret file was used, and I am not attaching raw configuration or credential captures.

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.