Unverified50% confidenceReleaseExact time
On macOS, the first OpenCode task used to stall waiting for a human response on "access external directory /tmp"; now OpenCode's first run authorizes only its own private scratch directory, and the bootstrap instructions also send temporary files there, while other paths outside the workspace still prompt.
1
Sources
50%
Confidence
Short-term (~14 days)
Relevance
10/17/2026
First Seen
Valid until: 10/31/2026
Sources
Related Entities
Related Claims
UnverifiedIn the OpenCode official documentation, both the .env protection example and the company.guard example register an execute.before hook only for the read tool, and do not intercept the behavior of reading files via shell commands (such as cat).58% similarUnverifiedResolving the Missing X-OpenCode-Session error requires adding the session header in the custom request headers section of the configuration file, with the Session value needing to be generated locally58% similarUnverifiedOpenClaw在Windows环境下后台启动需要使用 Start-Process -WindowStyle Hidden -FilePath "openclaw" -ArgumentList "gateway" 命令56% similarUnverifiedOn macOS, the permissions dialog and attachment checks no longer read /.vol, /.nofollow, or /.resolve paths before approval.56% similarUnverifiedWhen OpenCode 2 refuses to load a v1 plugin, it does not report an error, but leaves only a WARN message in the log, and startup proceeds as usual.56% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1053666API
curl https://kongchang.com/api/v1/knowledge/claims/1053666MCP
get_claim(id=1053666)