ai coding

Every AI coding tool, Claude Code, Cursor, Copilot, Cline and the rest, raises the same proxy question, and the answer is always two answers. The tool's own connection to its model rarely needs a proxy, and never to hide you. The code and agents you build with it often do. This explainer draws the line once, so the per-tool guides can skip it.

Proxies for Claude Code split into three questions. The big one is the code it writes for you, scrapers, crawlers, monitors and browser agents, which needs residential proxies to run at scale. The second is routing Claude Code itself through a proxy, which it documents with HTTP(S)_PROXY (no SOCKS) for corporate networks and reachability. The third is everything a proxy never does.

Cline is unusual among AI coding agents: it has a built-in browser tool, so it browses the web itself, and it builds automation that does the same. Both meet the walls a proxy solves. This covers where the proxy goes for the code Cline writes, the reachability angle of its bring-your-own-key model access, and the honest limits.

Cursor is an agent-first IDE, and its agents write and run the scrapers, crawlers and automation that need proxies. This covers the residential-proxy layer for what Cursor builds, Cursor's own VS Code proxy settings for corporate networks, and what an IP never does for the editor itself.

GitHub Copilot's proxy story is mostly the corporate one: it documents proxy settings per IDE, basic and Kerberos authentication, and custom certificates for TLS-inspecting networks. That is your company's proxy, not a residential one you buy. The residential proxy belongs to the scrapers and agents you build with Copilot, and this covers both.

An MCP server that fetches the web, a scraper, a search tool, a price checker, hits the same bot walls and per-IP limits as any client, so it needs residential proxies. One that talks only to a private API does not. This covers which MCP servers need a proxy, where it goes in the server, and how to wire it in the common runtimes.

The Claude Agent SDK is Claude Code as a library, so the agents you build with it browse the web through built-in and custom tools. This guide shows where a proxy goes: in the custom tools and subprocess code that fetch sites, and the process-level HTTP(S)_PROXY for reachability, with the honest note that the SDK's own model calls do not want one.