You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 605dcff
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): reply once to full-access OpenCode asks and name the auto-reply path
OpenCode stores "always" grants per directory, not per session. On a shared
external server an "always" from a full-access thread would silently widen
what a supervised thread on the same directory is allowed to do, so reply
"once" instead. Every ask in full access is auto-answered anyway.
Also extract the full-access branch into autoReplyFullAccess so the id
bookkeeping has a name and a boundary, add an emitUnsafe sibling next to
emit for the one publish that must not yield after its terminal check,
collapse the two identical auto-approve tests into one parameterized case,
and note the upstream ruleset quirk in the provider internals doc.
Co-Authored-By: Claude Fable 5.1 <[email protected]>
Copy file name to clipboardExpand all lines: docs/internals/providers.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,7 +125,8 @@ attachment to the provider adapter. Each adapter decides what its provider inges
125
125
Claude receives the attachment directory as an allowed additional directory. Codex keeps its
126
126
configured sandbox policy, so access depends on that policy and the selected runtime mode. OpenCode
127
127
allows all paths in full-access mode and requests approval for directories outside the workspace in
128
-
restricted modes. Cursor and Grok use their own provider permission rules.
128
+
restricted modes. Upstream OpenCode evaluates doom-loop and subagent asks against the agent ruleset
129
+
only, ignoring the session ruleset T3 sends, so the adapter answers those asks itself in full access. Cursor and Grok use their own provider permission rules.
129
130
130
131
The server does not copy attachments into a project or bypass provider approval rules. If an agent
131
132
cannot read an attachment, the user must approve the access or select a runtime mode that permits it.
0 commit comments