omc team: Claude Code bypass permissions TUI dialog auto-selects 'No, exit' in small tmux panes

[OpenCnid]

Problem

When running omc team, worker panes in tmux are typically 11-12 rows tall. Claude Code's bypass permissions confirmation dialog renders with the cursor on "No, exit" (the first/default option). Because the pane is too short to display the "Yes, I accept" option, the dialog auto-selects "No, exit" and Claude Code exits immediately.

This means omc team with Claude workers cannot start in the default tmux layout.

Environment

• omc version: 4.10.2
• Claude Code version: 2.1.92
• OS: Ubuntu (WSL2)
• tmux session created by omc team with default -y 50 (or inheriting terminal size)

Steps to Reproduce

1. Run omc team 3:claude "any task"
2. Observe worker panes are ~11 rows tall (50 rows split across leader + 2 workers)
3. Claude Code launches with --permission-mode bypassPermissions (or --dangerously-skip-permissions)
4. The TUI confirmation dialog renders, but auto-selects "No, exit" because the pane is too short
5. Claude exits, omc sends task text to raw bash, which errors with syntax error near unexpected token

What I Tried

• Setting hasTrustDialogAccepted: true in ~/.claude.json for the project ✅ (doesn't help - different dialog)
• Setting skipDangerousModePermissionPrompt: true in ~/.claude.json ❌ (doesn't seem to take effect for child processes)
• Patching model-contract.js to use --permission-mode bypassPermissions instead of --dangerously-skip-permissions ✅ (correct flag, but dialog still appears)
• Increasing tmux session size with -y 80 in the new-session call ❌ (detached sessions ignore size flags without a client attached)

Root Cause

In team.js (bundled in oh-my-claude-sisyphus), the tmux session is created and split into panes. With 2 workers + 1 leader in a ~50 row window, each pane gets ~11-12 rows. Claude Code's Ink-based TUI dialog for bypass permissions needs at least ~15 rows to render both options visible.

Suggested Fixes

Option A (best): Launch Claude Code workers with --print mode + --permission-mode bypassPermissions to avoid the TUI dialog entirely. The --print flag skips the trust/permissions dialogs.

Option B: Add an environment variable (e.g., CLAUDE_CODE_NONINTERACTIVE=1 or CLAUDE_CODE_ACCEPT_BYPASS=1) that Claude Code respects to skip the bypass permissions confirmation.

Option C: When creating the tmux session for teams, use larger pane sizes. For detached sessions, attach a phantom client or use tmux resize-window after creation.

Option D: Use a vertical-only split layout so worker panes get more rows (full window width, half height each instead of quarter).

Workaround

Currently none that works reliably. The dialog cannot be bypassed programmatically in small panes.

[OpenCnid]

Update: Found the fix! ✅

After extensive debugging, we found the root cause and a working solution.

Root Cause (two issues)

Issue 1: The --dangerously-skip-permissions flag (and --permission-mode bypassPermissions) triggers an interactive TUI confirmation dialog. In small tmux panes, this dialog's select component defaults to "No, exit" and auto-confirms, killing the worker before it starts.

Issue 2: The dialog bypass setting skipDangerousModePermissionPrompt needs to be in ~/.claude/settings.json, not ~/.claude.json. Without this, the dialog always appears regardless of pane size.

Working Fix

Step 1: Change model-contract.ts to use the modern flag:

- const args = ['--dangerously-skip-permissions'];
+ const args = ['--permission-mode', 'bypassPermissions'];

Step 2: Users need skipDangerousModePermissionPrompt: true in ~/.claude/settings.json to suppress the bypass confirmation dialog. This is the real blocker — even with correct flags and large panes, the dialog's default selection is "No, exit".

Suggested improvements for omc

1. Add a setup check/auto-fix: When omc team detects Claude workers, check if skipDangerousModePermissionPrompt is set and prompt the user to enable it if missing.

2. Use --permission-mode bypassPermissions instead of --dangerously-skip-permissions — it's the modern equivalent and works the same way.

3. Consider tmux resize-window after session creation — tmux set-option -g default-size 200x80 or explicit tmux resize-window -t $session -x 200 -y 80 gives workers enough room. We confirmed this works on detached sessions.

Tested and confirmed working

• omc 4.10.2 + Claude Code 2.1.92
• 2 Claude workers actively building code
• Bridge events flowing through the full pipeline

[Yeachan-Heo]

Confirmed this is actionable. I'm opening a fix session now to inspect the team worker launch path / pane sizing / Claude bypass-permissions behavior and push the smallest reliable fix.

—
[repo owner's gaebal-gajae (clawdbot) 🦞]