harden: explicitly disable opencode share, autoupdate, and OpenTelemetry#2
Open
figitaki wants to merge 1 commit into
Open
harden: explicitly disable opencode share, autoupdate, and OpenTelemetry#2figitaki wants to merge 1 commit into
figitaki wants to merge 1 commit into
Conversation
Defense-in-depth for the sandbox opencode config. None of these are enabled by default in our setup, but making them explicit prevents an upstream default flip from silently sending data off-box: - share: disabled — prevents /share from uploading conversations to opencode.ai (default is 'manual', i.e. user-initiated only) - autoupdate: false — image versions are pinned via Modal, so the upstream version-check ping is unnecessary - experimental.openTelemetry: false — explicit opt-out (default off) Code and prompts continue to flow directly from opencode to the configured LLM provider (Anthropic/OpenAI/Google) via API keys; no data routes through opencode.ai servers.
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.
Summary
Defense-in-depth for the sandbox
opencode.json. None of these flags change current behavior — they pin already-safe defaults so an upstream default flip can't silently send data off-box.share: \"disabled\"— prevents/sharefrom uploading conversations to opencode.ai (upstream default is\"manual\", i.e. user-initiated only).autoupdate: false— image versions are pinned via the Modal sandbox image, so the upstream version-check ping is unnecessary.experimental.openTelemetry: false— explicit opt-out (default is off, but the experimental section is documented as unstable).Code and prompts continue to flow directly from opencode to the configured LLM provider (Anthropic / OpenAI / Google) via API keys — no data routes through opencode.ai servers either before or after this change.
Context
Triggered by a question about whether opencode could read our data without us being on their enterprise plan. Short answer: no, given our config. This PR makes that posture explicit in the file rather than implicit in the defaults.
References:
Test plan
start.shlogs)/shareis rejected / disabled when invoked from inside a session