Vibe worker spawns into blank terminal with no TUI or visible output

[nikhilachale]

When spawning a worker with the vibe harness, the session terminal appears blank. There is no Vibe TUI, no startup text, no
progress output, and no obvious error message.

Expected behavior:

• Either Vibe should open an interactive TUI like other terminal agents, or
• AO should clearly show that Vibe is running in headless/programmatic mode and stream/print useful output or failures.

Actual behavior:

• The terminal stays blank after spawning the worker.
• It is not clear whether Vibe is running, waiting, crashed, or exited.
• The pane remains open because AO keeps the tmux session alive after the agent exits.

Relevant code:

• backend/internal/adapters/agent/vibe/vibe.go
• The adapter launches Vibe with:

vibe --trust --output text --workdir ... -p

This uses Vibe programmatic mode, not the interactive TUI. With --output text, Vibe may only print the final response and may
not stream progress.

Possible causes:

• --output text hides progress until completion.
• Vibe exits quickly and AO leaves a blank keep-alive shell.
• Vibe crashes before output, but the error is not visible enough in the terminal.
• Empty/missing prompt may launch a mode that does not behave as AO expects.

Suggested fixes:

• Use --output streaming for Vibe workers so output appears while the task runs.
• Or support an interactive/TUI launch mode for Vibe.
• Surface Vibe startup/crash errors clearly before entering the keep-alive shell.
• Add a guard/error for empty prompts if Vibe requires -p for AO-managed workers.

Local observation:
Running vibe --help showed that -p/--prompt is programmatic mode, and --output text is for final human-readable output. This
matches the blank/no-TUI behavior.