OpenCode Proxies Requests to Remote Server
💡Discover why popular local tool OpenCode isn't truly local—privacy risk alert
⚡ 30-Second TL;DR
What Changed
Web UI proxies requests to app.opencode.ai by default
Why It Matters
This undermines trust in OpenCode as a local tool, potentially deterring users prioritizing data privacy or offline use. Developers may need alternatives until fixed.
What To Do Next
Review OpenCode GitHub issues #12083 and #6352 before local deployment.
Key Points
- •Web UI proxies requests to app.opencode.ai by default
- •No option to serve fully locally or disable proxy
- •Open GitHub PRs and issues: #12446, #12829, #17104, #12083
- •Undocumented behavior problematic for firewalls and privacy
🧠 Deep Insight
Background and context from public sources — not the original article. 9 sources cited.
🔑 Enhanced Key Takeaways
- •OpenCode supports standard proxy environment variables and custom certificates to address enterprise network constraints, including authentication via URL credentials or LLM Gateways for advanced methods like NTLM[2].
- •Integration with tools like Promptfoo allows MCP server configuration (local or remote with OAuth/headers) and persistent sessions, but connecting to an existing server delegates authentication and setup to that server[1].
- •OpenCode web UI works with oauth2proxy for authentication, though TUI clients face connection issues when running behind such proxies[7].
🔮 Future ImplicationsAI analysis grounded in cited sources
📎 Sources (9)
Factual claims are grounded in the sources below. Forward-looking analysis is AI-generated interpretation.
Weekly AI Recap
Read this week's curated digest of top AI events →
👉Related Updates
AI-curated news aggregator. All content rights belong to original publishers.
Original source: Reddit r/LocalLLaMA ↗
This is a summary, not the original. Read the source, or get the weekly briefing.
Weekly AI briefing
One email a week. Unsubscribe anytime.

