[BUG] Sandbox network prompt missing "No" option — causes infinite loop with retrying subprocesses

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Sandbox network prompt missing "No" option — causes infinite loop with retrying subprocesses

Description

The "Network request outside of sandbox" prompt is missing a standard "No" option. Every other permission prompt in Claude Code offers a simple "No" where you can tab to provide instructions. The sandbox network prompt only offers Escape to decline, which is inconsistent and creates an inescapable loop when a subprocess retries the connection.

Steps to Reproduce

1. Enable sandbox mode
2. Run a command that uses a tool with telemetry (e.g. Dolt, which phones home to eventsapi.dolthub.com)
3. The sandbox prompt appears:

Network request outside of sandbox

  Host: eventsapi.dolthub.com

  Do you want to allow this connection?
  > 1. Yes
    2. Yes, and don't ask again for eventsapi.dolthub.com
    3. No, and tell Claude what to do differently (esc)

1. Press Escape to select option 3
2. Before you can type any instructions, the prompt immediately reappears because the subprocess retried the connection
3. Infinite loop — no way to break out

Expected Behavior

Add a standard "No" option consistent with all other Claude Code permission prompts:

  > 1. Yes
    2. Yes, and don't ask again for eventsapi.dolthub.com
    3. No
    4. No, and don't ask again for this host

Options 3 and 4 should allow tabbing to provide instructions, the same way every other permission prompt works. This also solves the infinite loop: "No, and don't ask again for this host" would prevent the prompt from reappearing on retry.

Workaround

Kill the subprocess externally, or disable the tool's telemetry before enabling sandbox. In this case: dolt config --global --add metrics.disabled true and restart the Dolt server.

Environment

• Claude Code CLI
• macOS

What Should Happen?

Add a standard "No" option consistent with all other Claude Code permission prompts:

  > 1. Yes
    2. Yes, and don't ask again for eventsapi.dolthub.com
    3. No
    4. No, and don't ask again for this host

Error Messages/Logs

Steps to Reproduce

Try to use Beads issue tracker inside a container.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.81

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_