Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Feature]: Add Support for System/Custom HTTP & SOCKS Proxy Configuration in OpenClaw [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#60035•Fetched 2026-04-08 02:37:11
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
SKYC829SKYC829
Participants
SKYC829SKYC829
Timeline (top)
labeled ×1

OpenClaw currently relies on direct network access for all its external calls (e.g., web search, web fetch, browser automation, plugin APIs). In many corporate or restricted environments users need to route traffic through a proxy—either the system‑wide proxy settings or a user‑specified HTTP/SOCKS proxy.

Adding first‑class proxy support would:

Enable use behind firewalls or corporate networks where direct outbound connections are blocked. Allow per‑session or per‑tool proxy overrides, useful for cases where only certain services (e.g., web search) need to go through a proxy while others stay direct. Improve security and privacy by letting users point traffic to a trusted forward proxy (e.g., a local mitmproxy or corporate forward proxy).

Root Cause

OpenClaw currently relies on direct network access for all its external calls (e.g., web search, web fetch, browser automation, plugin APIs). In many corporate or restricted environments users need to route traffic through a proxy—either the system‑wide proxy settings or a user‑specified HTTP/SOCKS proxy.

Adding first‑class proxy support would:

Enable use behind firewalls or corporate networks where direct outbound connections are blocked. Allow per‑session or per‑tool proxy overrides, useful for cases where only certain services (e.g., web search) need to go through a proxy while others stay direct. Improve security and privacy by letting users point traffic to a trusted forward proxy (e.g., a local mitmproxy or corporate forward proxy).

RAW_BUFFERClick to expand / collapse

Summary

OpenClaw currently relies on direct network access for all its external calls (e.g., web search, web fetch, browser automation, plugin APIs). In many corporate or restricted environments users need to route traffic through a proxy—either the system‑wide proxy settings or a user‑specified HTTP/SOCKS proxy.

Adding first‑class proxy support would:

Enable use behind firewalls or corporate networks where direct outbound connections are blocked. Allow per‑session or per‑tool proxy overrides, useful for cases where only certain services (e.g., web search) need to go through a proxy while others stay direct. Improve security and privacy by letting users point traffic to a trusted forward proxy (e.g., a local mitmproxy or corporate forward proxy).

Problem to solve

Broader adoption in environments with strict outbound policies. Better privacy for users who wish to tunnel traffic through an anonymising proxy. Consistent experience with other CLI tools that already support system proxies.

Proposed solution

ComponentChangeDetails
CLI / ConfigAdd a new top‑level config section proxyjson { "proxy": { "enabled": true, "type": "http_or_socks5", "url": "http://127.0.0.1:7890", "noProxy": ["localhost", "127.0.0.1"] } }
Environment variable fallbackRespect standard variables (HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, NO_PROXY) when proxy.enabled is not explicitly set.This mirrors typical Node.js behaviour.
Agent-level overridesExtend agents.who.environments.proxy or json {"agents":{"who":{"environments":{"HTTP_PROXY":undefined,"HTTPS_PROXY":undefined,"ALL_PROXY":undefined,"NO_PROXY":undefined}}},"list":[{"id":"any","HTTP_PROXY":undefined,"HTTPS_PROXY":undefined,"ALL_PROXY":undefined,"NO_PROXY":undefined}]}Allows per-agent custom proxy without affecting the whole daemon.
Tool‑level overridesExtend tools.web.search, tools.web.fetch, tools.browser, and any future network‑based plugins with optional proxy field.Allows per‑tool custom proxy without affecting the whole daemon.
Runtime loadingIn OpenClaw’s Node runtime, when creating http(s)/net agents, inject the proxy using libraries such as https-proxy-agent or socks-proxy-agent.Works for fetch, axios, Playwright, etc.

Alternatives considered

No response

Impact

Affected: all users with network limitations or those who have high expectations for security and privacy protection Severity: annoying Frequency: always Consequence: delays

Evidence/examples

No response

Additional information

Thank you for considering this feature!

extent analysis

TL;DR

To add first-class proxy support in OpenClaw, implement a new top-level config section proxy and respect standard environment variables for proxy settings.

Guidance

  • Add a proxy config section with enabled, type, url, and noProxy fields to allow users to specify proxy settings.
  • Implement environment variable fallback using standard variables like HTTP_PROXY, HTTPS_PROXY, ALL_PROXY, and NO_PROXY when proxy.enabled is not explicitly set.
  • Extend agents and tools with optional proxy fields to allow per-agent and per-tool custom proxy settings without affecting the whole daemon.
  • Use libraries like https-proxy-agent or socks-proxy-agent to inject the proxy in OpenClaw's Node runtime when creating http(s)/net agents.

Example

{
  "proxy": {
    "enabled": true,
    "type": "http_or_socks5",
    "url": "http://127.0.0.1:7890",
    "noProxy": ["localhost", "127.0.0.1"]
  }
}

Notes

The proposed solution requires careful consideration of the impact on existing users and the potential consequences of delaying the implementation.

Recommendation

Apply the proposed workaround by implementing the proxy config section and respecting standard environment variables to improve security, privacy, and usability for users in restricted environments.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#GPU compatibility#latency issue#model loading#environment variable

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING