Repository navigation
Non-git projects use "/" as worktree, breaking permission path resolution #24694
Description
Description
Problem
When running in a non-git directory, Project.fromDirectory sets:
worktree: "/"
sandbox: "/"
This causes permission path resolution to break.
Example:
path.relative("/", "/home/.../artifacts/dry_run/file.md")
→ "home/.../artifacts/dry_run/file.md"
This does not match patterns like:
artifacts/dry_run/*
Impact
Even with a typical ruleset like:
edit:
"": "deny"
"artifacts/dry_run/": "allow"
the allow rule never matches, because the evaluated path becomes:
home/.../artifacts/dry_run/...
So the final result is a deny, even though the config is correct.
Expected behavior
Non-git directories should treat the current directory as the project root:
worktree: directory
sandbox: directory
Plugins
None
OpenCode version
1.14.28
Steps to reproduce
Steps to reproduce
-
Create a non-git directory (no
.gitfolder) -
Create an opencode config with path-scoped permissions, for example:
edit:
"": "deny"
"artifacts/dry_run/": "allow"
-
Start opencode in that directory
-
Attempt to create a file:
Create artifacts/dry_run/test.md
- Observe that the operation is denied
What happens
The evaluated path becomes:
home/.../artifacts/dry_run/test.md
instead of:
artifacts/dry_run/test.md
So the allow rule does not match and the deny rule applies.
Expected
The file should be created successfully because it matches the allow rule.
Screenshot and/or share link
No response
Operating System
Debian GNU/Linux 13 (trixie)
Terminal
Konsole Version 25.04.2
Activity
github-actions commentedon Apr 28, 2026
This issue might be a duplicate of existing issues. Please check:
Project.fromDirectorysetsworktree: "/"for non-git directories instead of using the actual directory. That issue focuses on the UI symptom (recent projects showing "/"), but the fix would address the same underlying bug you're hitting.worktreebeing/in non-git projects, with the samepath.relative("/", ...)problem and similar suggested fix.If either of those captures your issue, please consider adding a comment there rather than opening a new one. If your report covers a distinct aspect not addressed in those issues, feel free to leave this open and clarify the difference.
BennD commentedon May 10, 2026
Opened #26694 for this. Adds a
workspaceRoot(ctx)helper next tocontainsPath(same file, sameworktree === "/"sentinel) and uses it everywherepath.relative(instance.worktree, …)was anchoring on the worktree, including the file tools,tool/lsp.ts, andagent.ts'sreferencePath. Approach is similar to #18761 but consolidates the helper at the project layer rather than undertool/, and matches each test file's existing style instead of mixing patterns.fix(permission): worktree-relative paths fall back to directory in no…
mattcoleanderson commentedon Jun 22, 2026
The PR for this was closed automatically. Commenting for attention to this since opencode should never automatically get full privileges of my systems root directory without the user explicitly giving it
github-actions commentedon Aug 22, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
dimon222 commentedon Aug 22, 2026
Reopen please, thus should never be fallback behavior
gwerbin commentedon Sep 4, 2026
+1, I was really surprised when I saw this. What can be done to help?