Is it possible to use proxy?

Question

Is it possible to use proxy server as gasket between opencode and Internet?

This issue might be a duplicate of existing issues. Please check:

Support HTTP_PROXY & HTTPS_PROXY for millions of users who are behind fire walls in some regions and some organizations. #531: Support HTTP_PROXY & HTTPS_PROXY for millions of users who are behind fire walls in some regions and some organizations
v1.0.119: nothing to see in an environment with a proxy #4823: v1.0.119: nothing to see in an environment with a proxy
acp-command unhandled rejection #3989: acp-command unhandled rejection (proxy-related crashes in v1.0.35)
socket connection error with ProxyChains from v1.0.0 #4284: socket connection error with ProxyChains from v1.0.0
Different proxies for different providers? #1711: Different proxies for different providers?
AWS Bedrock Provider doesn't seem to respect proxy #2446: AWS Bedrock Provider doesn't seem to respect proxy
Use local SSL trust store #1694: Use local SSL trust store (proxy with self-signed SSL certs)

Feel free to ignore if none of these address your specific case.

I think there is a bug w/ HTTP_PROXY and HTTPS_PROXY, looking into them

It works fine with HTTPS_PROXY, but if you provide HTTPS_PROXY and HTTP_PROXY it will crash, at list on my NixOS machine.

It works fine with HTTPS_PROXY

socks proxy?

why not just add proxy support via golang.org/x/net/proxy?

This isn't a go codebase my guy

This isn't a go codebase my guy

ok 😄
but in other languages too there are stable libraries for proxying everywhere
and what about your fork? 😉

ill figure out what the problem is but for now set:

NO_PROXY=localhost,127.0.0.1

ill figure out

but is it possible to use socks5 and socks5h proxies as ALL_PROXY?

Fix available in PR #10856

Yes, proxy support is now implemented in PR #10856!

Quick setup:

export HTTPS_PROXY=http://your-proxy:8080
export NO_PROXY=localhost,127.0.0.1
opencode

Important: Always set NO_PROXY=localhost,127.0.0.1 to prevent internal server communication from being routed through the proxy.

For corporate proxies with custom certificates:

// opencode.json
{
  "proxy": {
    "https": "http://proxy:8080",
    "tls": {
      "ca": "/path/to/corporate-ca.pem"
    }
  }
}

Note on SOCKS5: Not supported yet (Bun limitation). Use a SOCKS-to-HTTP bridge as workaround.

The fix replaces all fetch() calls with a proxyFetch() wrapper that properly handles proxy configuration and NO_PROXY patterns.

Note on SOCKS5: Not supported yet (Bun limitation). Use a SOCKS-to-HTTP bridge as workaround.

the sad fact 😕

To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.

Navigation Menu

Repository navigation

Is it possible to use proxy? #4924

Question

Fix available in PR #10856

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Is it possible to use proxy? #4924

Description

Question

Activity

github-actions commented on Nov 30, 2025

rekram1-node commented on Dec 2, 2025

khrore1 commented on Dec 2, 2025

anpic commented on Dec 3, 2025

anpic commented on Dec 3, 2025

rekram1-node commented on Dec 3, 2025

anpic commented on Dec 4, 2025

rekram1-node commented on Dec 8, 2025

anpic commented on Dec 8, 2025

Thesam1798 commented on Jan 27, 2026

Fix available in PR #10856

anpic commented on Jan 28, 2026

github-actions commented on Mar 30, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions