Answer: OpenCode uses local HTTP connections between the CLI and its background service, so the loopback exclusion is required when a proxy is configured in the CLI environment. Status: Overdue (check was due 2026-11-20T13:37:04Z and has not succeeded) Entry: tool/opencode/troubleshooting/loopback-no-proxy-requirement Revision: 2 Digest: sha256:70d0a78342403480 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:57:54Z Last changed: 2026-11-13T13:31:04Z (NO_PROXY definition: — → a comma-separated list of hosts and addresses that connect directly) Last verified: 2026-11-19T13:37:04Z Next check: 2026-11-20T13:37:04Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of reason | OpenCode uses local HTTP connections between the CLI and its background service | [1] | 2026-11-19 NO_PROXY example | localhost , 127 . 0 . 0 . 1 ,:: 1 | [1] | 2026-11-19 NO_PROXY definition | a comma-separated list of hosts and addresses that connect directly | [1] | 2026-11-19 Sources: [1] opencode. "Network | OpenCode". https://opencode.ai/docs/network/ Role: primary. Accessed: 2026-11-19T13:37:04Z Quote: "OpenCode uses local HTTP connections between the CLI and its background service, so the loopback exclusion is required when a proxy is configured in the CLI environment." (Supports: reason) Quote: "export NO_PROXY=localhost , 127 . 0 . 0 . 1 ,:: 1" (Supports: NO_PROXY example) Quote: "NO_PROXY is a comma-separated list of hosts and addresses that connect directly." (Supports: NO_PROXY definition) Snapshot SHA-256: 3056c50c33d3ed158df7cc3a765c06e9fea94934acf0a36506414878cc4ec08f (captured 2026-11-13T13:31:04Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T13:31:04Z, so the values verified then were kept. Cross-check: not-available at 2026-11-19T13:37:04Z. No independent second source is configured for this entry Last successful check: 2026-11-19T13:37:04Z Last attempt: 2026-11-19T13:37:04Z Notes and limitations: Extracted automatically from a single official source (section "Network"). Related: https://latestn.com/tool/opencode/troubleshooting/raycast-free-models-403 Why do free-tier chat models return HTTP 403 in Raycast with OpenCode? https://latestn.com/tool/opencode/troubleshooting/read-logs How do I read opencode logs to debug an issue? https://latestn.com/tool/opencode/troubleshooting/verify-network-config How do I verify that opencode's network and proxy configuration is working? https://latestn.com/tool/opencode/settings/warming-options How do I change the warming prompt, idle interval, or active window in opencode? https://latestn.com/tool/opencode/troubleshooting/capture-heap-snapshot-profiles How do I capture a heap snapshot or CPU and memory profiles in opencode? https://latestn.com/tool/opencode/troubleshooting/check-background-service-status How do I check the status of the opencode background service? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T13:31:04Z | changed | NO_PROXY definition: — → a comma-separated list of hosts and addresses that connect directly | [1] 2026-11-13T03:57:54Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/opencode/troubleshooting/loopback-no-proxy-requirement/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/opencode/troubleshooting/loopback-no-proxy-requirement POST: https://latestn.com/dispute/tool/opencode/troubleshooting/loopback-no-proxy-requirement with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/opencode/troubleshooting/loopback-no-proxy-requirement?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). Why does opencode require loopback addresses in NO_PROXY when a proxy is configured? Revision 2, last verified 2026-11-19T13:37:04Z. https://latestn.com/tool/opencode/troubleshooting/loopback-no-proxy-requirement (accessed 2026-11-21T09:53:10Z). @misc{LatestN_tool_opencode_troubleshooting_loopback_no_proxy_requirement_r2, title = {Why does opencode require loopback addresses in NO_PROXY when a proxy is configured?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/opencode/troubleshooting/loopback-no-proxy-requirement}}, note = {Revision 2; digest sha256:70d0a78342403480; last verified 2026-11-19T13:37:04Z; accessed 2026-11-21T09:53:10Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/opencode/troubleshooting/loopback-no-proxy-requirement