Read permission doesn't look to match when the agent uses ../.. paths

Description

I have the following in my global config

  "permission": {
    "read": {
      "/Users/dcapwell/.config/opencode/skills/**/*": "allow",
      "/Users/dcapwell/.config/opencode/skills/*": "allow",

The reason for this change is I created a skill that comes with docs/resources, and needs to search and read the files in the skill. The issue I am seeing is that the agent asks to read

Read ../../../../../../.config/opencode/skills/my-skill/references/AGENTS.md

This then pops up a permission prompt.

I then tried a simple prompt, show absolute path and asked it to read the file, and made sure to put the exact path in the read permissions; same issue.

"/path/to/file": "allow"

and prompt: read "/path/to/file" and tell me what it says

In this cases its also doing the ../.. read pattern and correctly detecting that its reading outside of the current directory and asked for permission.

Plugins

No response

OpenCode version

1.1.21

Steps to reproduce

No response

Screenshot and/or share link

No response

Operating System

No response

Terminal

No response

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

Bug: permission pathing crossplatform #7279: Bug: permission pathing crossplatform - Path matching fails with relative path resolution
Permission check for tool-output directory never matches, causes hang in headless mode #7876: Permission check for tool-output directory never matches - Similar pattern matching issue with wildcards
Agent Permission not work as expected #9927: Agent Permission not work as expected - Permissions configuration not being respected
Split external_directory permission into read vs write #5395: Split external_directory permission into read vs write - Related feature request about read permissions
skill can't find scripts path #6900: skill can't find scripts path - Skills unable to locate files with relative paths
An agent is able to read all filesystem outside a project directory in Plan mode #7504: An agent is able to read all filesystem outside a project directory - Comprehensive permission bypass issue

The core issue appears to be that permission rules are not matching when paths are normalized to relative formats (with ../..) instead of being resolved to absolute paths. Feel free to ignore if your specific case differs from these.

I have tried the following, but don't see any difference (tried with and without *)

    "allowed_paths": {
      "/Users/dcapwell/.config/opencode/skills/**/*": "allow",
      "~/.config/opencode/skills/**/*": "allow"
    },

Still asking for read permission

Access external directory ~/.config/opencode/skills/my-skill/references

ok found the doc on this: https://opencode.ai/docs/permissions#external-directories

Using that and the permissions are fixed!

Navigation Menu

Repository navigation

Read permission doesn't look to match when the agent uses ../.. paths #11059

Description

Plugins

OpenCode version

Steps to reproduce

Screenshot and/or share link

Operating System

Terminal

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Read permission doesn't look to match when the agent uses ../.. paths #11059

Description

Description

Plugins

OpenCode version

Steps to reproduce

Screenshot and/or share link

Operating System

Terminal

Activity

github-actions commented on Jan 28, 2026

dcapwell commented on Jan 29, 2026

dcapwell commented on Jan 29, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions