OpenCode concerns (not truely local)

A significant privacy concern has surfaced around OpenCode, an AI-powered coding assistant tool. Users, including the developer who raised the alarm, discovered that when running the tool in its supposed local mode via `opencode serve`, the web interface does not operate independently. Instead, it acts as a proxy, silently routing all requests through the company's external servers at `https://app.opencode.ai`. Crucially, there is no configuration option, command-line flag, or documented setting to disable this proxying behavior and host the UI purely on the local machine. The command `opencode web` simply opens a browser tab to this proxied connection.

This discovery has sparked a major backlash in the developer community, particularly among those who chose OpenCode for its perceived local and private operation. The issue is not new; the project's GitHub repository contains at least six longstanding open issues and pull requests—some dating back months—that highlight and attempt to address this problem. For developers working in secure, air-gapped, or firewall-protected environments, or those simply handling sensitive proprietary code, this default cloud dependency is a critical security flaw. It undermines the tool's value for local development and raises questions about data privacy, as prompts and potentially code context could be transmitted without clear user consent.