docs(opencode): external_directory also fires on paths the BRIEF NEVER NAMES - #985
Open
ZacxDev wants to merge 1 commit into
Open
docs(opencode): external_directory also fires on paths the BRIEF NEVER NAMES#985ZacxDev wants to merge 1 commit into
ZacxDev wants to merge 1 commit into
Conversation
…R NAMES
Four dispatches died on 2026-08-28 in two shapes that failure mode 1's stated
closures do not cover, because preflight scans the brief's TEXT and both paths
are produced at runtime:
(a) a TOOL's own output path — `browser screenshot` with no argument writes into
the system temp dir, and reading it back was auto-rejected. Fixed in the
brief by passing an explicit path under --dir, NOT by widening the config: a
screenshot is a pixel-perfect image of an authenticated view, the filename
prefix is fixed and the directory is shared, so an allow would let any
dispatch read captures left by any session.
(b) a SKILL's reference/ files resolved against ~/.claude/skills/<name>/ rather
than the carved-out ~/.config/opencode/skills/**. Preflight printed
"skill reference/ : readable" — a false all-clear for this shape.
Also records that preflight refuses a brief that merely MENTIONS an external
path in prose: a warning reading "it writes to /tmp" blocks at rc 3.
The headline correction is to "Closed two ways" — a clean preflight is not
evidence a run is safe from an external_directory auto-reject.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs(opencode): external_directory also fires on paths the BRIEF NEVER NAMES
Four dispatches died on 2026-08-28 in two shapes that failure mode 1's stated
closures do not cover, because preflight scans the brief's TEXT and both paths
are produced at runtime:
(a) a TOOL's own output path —
browser screenshotwith no argument writes intothe system temp dir, and reading it back was auto-rejected. Fixed in the
brief by passing an explicit path under --dir, NOT by widening the config: a
screenshot is a pixel-perfect image of an authenticated view, the filename
prefix is fixed and the directory is shared, so an allow would let any
dispatch read captures left by any session.
(b) a SKILL's reference/ files resolved against ~/.claude/skills// rather
than the carved-out ~/.config/opencode/skills/**. Preflight printed
"skill reference/ : readable" — a false all-clear for this shape.
Also records that preflight refuses a brief that merely MENTIONS an external
path in prose: a warning reading "it writes to /tmp" blocks at rc 3.
The headline correction is to "Closed two ways" — a clean preflight is not
evidence a run is safe from an external_directory auto-reject.
Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com