https://manuelfedele.github.io/it/tags/sandbox/Recent content in Sandbox on Git Push and RunHugo -- gohugo.ioit© 2026 Manuel FedeleTue, 14 Apr 2026 22:00:00 +0100https://manuelfedele.github.io/it/posts/running-claude-code-in-a-network-sandbox/Tue, 14 Apr 2026 22:00:00 +0100https://manuelfedele.github.io/it/posts/running-claude-code-in-a-network-sandbox/<div class="lead text-neutral-500 dark:text-neutral-400 !mb-9 text-xl"> Most Claude Code setup guides assume a developer laptop with direct internet access. This is not that guide. I spent a session getting Claude Code to run inside a fully network-isolated corporate sandbox &ndash; no direct internet, all traffic through a controlled gateway, per-binary egress policies enforced at the proxy level. What started as &ldquo;remove sudo from this installer&rdquo; turned into a deep dive into every network call Claude Code makes and what it takes to route all of them through infrastructure you control. </div> <h2 class="relative group">Why Corporate-First Matters <div id="why-corporate-first-matters" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#why-corporate-first-matters" aria-label="Ancora">#</a> </span> </h2> <p>The default Claude Code installer assumes it can reach <code>storage.googleapis.com</code>, <code>api.anthropic.com</code>, and a handful of other Anthropic endpoints freely. In a corporate environment, none of that is given:</p>