Skip to content

fix: exempt DIFC/cli-proxy host from proxy routing in isolation mode #6438

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lpcox merged 2 commits into from
Jul 20, 2026
Merged

fix: exempt DIFC/cli-proxy host from proxy routing in isolation mode #6438

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b00ee44
fix: exempt DIFC/cli-proxy host from proxy routing in isolation mode
lpcox Jul 20, 2026
5206b3d
fix: use parseDifcProxyHost to correctly extract host for NO_PROXY
Copilot Jul 20, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions src/services/agent-environment/proxy-environment.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,12 @@ export function buildProxyEnvironment(params: ProxyEnvironmentParams): void {
if (config.topologyAttach) {
noProxyHosts.push(...config.topologyAttach);
}
// The DIFC/cli-proxy host is addressed by proxy-aware clients directly and
// must bypass Squid even when it isn't listed in topologyAttach. Strip any
// ":port" suffix since undici matches NO_PROXY against the hostname only.
if (config.difcProxyHost) {
noProxyHosts.push(config.difcProxyHost.split(':')[0]);
}
}

// The MCP gateway is served on the network gateway (e.g. 172.30.0.1). In
Expand Down
Loading