Reproduction steps
At the moment, we can't use zed properly with a remote server that requires a proxy. This is typically the case in an Enterprise/Corporate environment.
I posted this in discussion (#43405) initially but I guess it is better here hence reposting.
Current vs. Expected behavior
I've tried different things:
- starting
zed on my host from a shell with defined proxy (in http_proxy, https_proxy and no_proxy environment variables)
- configuring the proxy in my host Settings file (
{ "proxy": "http://..." })
- configuring environment variables in the project Settings file (
{ "env": {"http_proxy": "...", "https_proxy": "...", "no_proxy": "..." } or the same under {"terminal": {"env": {...}})
For 1., 2. and 3., proxy is not inherited by the remote connection. For instance, it fails to download node, codex-acp, etc.
2025-11-24T14:24:37+00:00 ERROR [crates/project/src/prettier_store.rs:151] (remote server) Cannot start default prettier due to its installation failure: prettier & plugins install: fetching latest npm versions: fetching latest npm version for package prettier: failure while downloading and/or installing Zed managed Node.js, restart Zed to retry: error downloading Node binary tarball
2025-11-24T14:26:43+00:00 ERROR [remote::remote_client] (remote server) server:error handling message. type:GetAgentServerCommand, error:fetching Codex latest release: error fetching latest release: error sending request for url (https://api.github.com/repos/zed-industries/codex-acp/releases): client error (Connect): operation timed out
- configuring environment variables in the remote server's
.bashrc.
For 4., I get an error when zed attempts to connect to the remote server:
As you can see in the logs, my .bashrc is showing the environment variables (e.g. env|grep -i proxy in the `.bashrc), so I know they are loaded.
Logs:
% zed
2025-11-24T14:35:35+00:00 INFO [zed] ========== starting zed version 0.212.6, sha 74924bc ==========
2025-11-24T14:35:35+00:00 INFO [crashes] spawning crash handler process
2025-11-24T14:35:35+00:00 INFO [zed] Using git binary path: Some("/Applications/Zed.app/Contents/MacOS/git")
2025-11-24T14:35:35+00:00 INFO [extension_host] extensions updated. loading 1, reloading 0, unloading 0
2025-11-24T14:35:35+00:00 INFO [auto_update] Auto Update: checking for updates
2025-11-24T14:35:35+00:00 INFO [crashes] connected to crash handler process after 100ms
2025-11-24T14:35:35+00:00 INFO [crashes] crash handler registered
2025-11-24T14:35:35+00:00 INFO [workspace] Rendered first frame
2025-11-24T14:35:38+00:00 INFO [remote::transport::ssh] Remote shell discovered:
no_proxy=...
https_proxy=...
http_proxy=...
/bin/bash
2025-11-24T14:35:38+00:00 ERROR [recent_projects::remote_connections] Failed to open project: Prebuilt remote servers are not yet available for "Proxy". See https://zed.dev/docs/remote-development
2025-11-24T14:35:40+00:00 INFO [auto_update] downloaded update. path:"/var/folders/2p/g16q1sfx24z_njrbjgcb241m0000gp/T/zed-auto-updatewIjKFg/Zed.dmg"
2025-11-24T14:35:44+00:00 INFO [auto_update] auto-update check failed: error:failed to copy app: "rsync(9109): error: mkstempat: 'Contents/.Info.plist.7lw4QR7LLu': Operation not permitted\nrsync(9109): error: Contents/Info.plist: utimensat (2): Operation not permitted\nrsync(9109): error: rsync_set_metadata\nrsync(9109): error: rsync_downloader\nrsync(9109): error: rsync_receiver\nrsync(9108): error: unexpected end of file\nrsync(9108): error: io_read_nonblocking\nrsync(9108): error: io_read_blocking\nrsync(9108): error: io_read_flush\nrsync(9108): error: rsync_sender\nrsync(9108): warning: child 9109 exited with status 1\n"
Looking for "proxy" in https://github.com/zed-industries/zed/blob/3281b9077fddb7d40278c0479b27e1fb5f2c9c0f/docs/src/remote-development.md does not give anything useful.
If applicable, attach your Zed log file to this issue.
No response
If applicable, attach your relevant Zed settings to this issue
No response
If applicable, provide details about your model provider
No response
Zed version and system specs
Host: macOS
remote host: Linux
If you are using WSL on Windows, what flavor of Linux are you using?
Arch Linux
Reproduction steps
At the moment, we can't use
zedproperly with a remote server that requires a proxy. This is typically the case in an Enterprise/Corporate environment.I posted this in discussion (#43405) initially but I guess it is better here hence reposting.
Current vs. Expected behavior
I've tried different things:
zedon my host from a shell with defined proxy (inhttp_proxy,https_proxyandno_proxyenvironment variables){ "proxy": "http://..." }){ "env": {"http_proxy": "...", "https_proxy": "...", "no_proxy": "..." }or the same under{"terminal": {"env": {...}})For 1., 2. and 3., proxy is not inherited by the remote connection. For instance, it fails to download
node,codex-acp, etc..bashrc.For 4., I get an error when zed attempts to connect to the remote server:
As you can see in the logs, my
.bashrcis showing the environment variables (e.g.env|grep -i proxyin the `.bashrc), so I know they are loaded.Logs:
Looking for "proxy" in https://github.com/zed-industries/zed/blob/3281b9077fddb7d40278c0479b27e1fb5f2c9c0f/docs/src/remote-development.md does not give anything useful.
If applicable, attach your Zed log file to this issue.
No response
If applicable, attach your relevant Zed settings to this issue
No response
If applicable, provide details about your model provider
No response
Zed version and system specs
Host: macOS
remote host: Linux
If you are using WSL on Windows, what flavor of Linux are you using?
Arch Linux