GitHub Issuesdemand signalby robreevesbuilt with AIheuristic score

anthropics/claude-code: Sandbox: allow outbound connections to localhost

Opportunity

AI-buildable

Traction

Creativity

The take

effort: ~1-2 weeks

Heuristic estimate (AI scoring not configured). anthropics/claude-code: Sandbox: allow outbound connections to localhost shows 51 engagement on ghissues. Buildability is inferred from the description; add an AI gateway key for a tailored read.

Deliver it

A starter prompt for Claude Code, what you'll need, and how to reach them.

Build a minimal version of "anthropics/claude-code: Sandbox: allow outbound connections to localhost". Read the original at https://github.com/anthropics/claude-code/issues/28018 for the exact requirements, then scaffold a Next.js + Tailwind app, implement the smallest valuable slice first, and ship it. (Enable AI scoring for a tailored, detailed prompt.)

Prerequisites — cost & what to learn

Node.js + a Vercel accountFree · Free (hobby tier)✓ in your stack
Part of the operator's house stack.
Any APIs/data the find depends onFree tier · Varies — enable AI scoring for a real cost read.📚 needs study
Depends on the find — enable AI scoring for specifics.
Learn it: Search getting-started ↗

Setup steps

How you'd build it

1Open the project and list its 3-5 core user-facing features.
2Scaffold a Next.js + AI Gateway app and rebuild the smallest valuable slice first.
3Wire any external data/APIs it depends on; stub what you can't access.
4Ship a thin public version and measure whether the demand signal reproduces.

Risks & moats

Traction may be launch-day spike rather than durable demand.
Heuristic scoring can't judge true novelty or competition — verify manually.

Original context

## Problem The sandbox blocks outbound TCP connections to localhost/127.0.0.1/::1 even when these are listed in `sandbox.network.allowedDomains`. The `sock.connect()` syscall gets `EPERM` (Operation not permitted). This makes it impossible to run integration tests against local Docker services (e.g. `http://localhost:8000`) from within the sandbox. ## What I've tried In `settings.json`: ```json "sandbox": { "enabled": true, "network": { "allowLocalBinding": true, "allowedDomains": [ "localhost", "127.0.0.1", "::1" ] } } ``` None of these settings allow the outbound connection. The only workaround is either `dangerouslyDisableSandbox: true` on every bash call, or adding the command to `excludedCommands`, both of which defeat the purpose of the sandbox. ## Requested feature A sandbox setting that allows outbound TCP connections to loopback addresses, e.g.: ```json "sandbox": { "network": { "allowLocalhostConnections": true } } ``` Or have `allowedDomains` with `localhost`/`127.0.0.1`/`::1` actually allow the TCP connection, not just DNS resolution. ## Use case Running integration tests against services in local Docker containers. For exampl