---
name: Claude --dangerously-load-development-channels TTY prompt
description: When claude starts with --dangerously-load-development-channels, it shows a TTY safety prompt that headless mode can't answer, causing restart loops. Recognize and auto-confirm.
type: reference
---

`claude --dangerously-load-development-channels server:<name>` shows a TTY warning before loading:

```
--dangerously-load-development-channels is for local channel development only.
Do not use this option to run channels you have downloaded off the internet.
Please use --channels to run a list of approved channels.
Channels: server:<name>
❯ 1. I am using this for local development
  2. Exit
```

**Symptom when broken:** claude exits ~3 seconds after start (no TTY input), wrapper restarts it, same prompt re-appears → infinite restart loop, MCP never spawns, bun never listens, webhook fails silently.

**Fix in wrapper scripts (e.g. `run-channel.sh`, `run-sendblue-channel.sh`):** poll the tmux pane and inject Enter when the warning is visible. The grep pattern must match the *current* claude version's wording. As of claude 2.1.126 the trigger substrings are `dangerously-load-development-channels is for`, `local channel development only`, and (older) `Loading development channels`. Match with `grep -qE` to support several phrasings.

There's a *second* TTY prompt earlier ("Bypass Permissions" — defaults to "No, exit"): wrapper needs to send `2` + Enter for that one.

**How to apply:** if a sendblue/teams/other dev-channel agent is in a restart loop and bun never spawns, capture the tmux pane — confirm one of the warning substrings is visible — patch the wrapper's grep pattern to include the actual wording, then restart the wrapper. Verified on cloud sendblue-channel 2026-05-20.