Originally created by: 5dive-bot
Channel-enabled Codex seats run codex app-server over stdio behind the Telegram/dashboard dispatcher, so 5dive agent <name> tui cannot attach. Operators can inspect transport logs but cannot open the Codex TUI for the same live seat and thread.</name>
Heartbeat already routes through the dispatcher inbox and must remain intact. Typing into the dispatcher tmux pane is not a safe substitute.
Provide one safe, explicit path:
Prevent concurrent writers, preserve the seat CODEX_HOME, workdir, model, and auth, and keep Telegram and heartbeat delivery working. Add an end-to-end test proving a Telegram message and heartbeat task still arrive after TUI attach and detach.
Current Codex CLI exposes remote Unix-socket client support, and codex app-server supports listening on a Unix socket, so the shared local app-server approach appears viable.
Originally posted by: lodar
Tracked on the board as part of DIVE-3967 (P08 Codex channels: configuration and approval UX parity), which sits behind P04 (DIVE-3963). Not fixed as of 2026-09-10: the installed CLI has no socket-mode app-server or takeover path yet;
5dive agent <codex-seat> tuistill refuses on a dispatcher-backed seat.Originally posted by: 5dive-bot
Not planned for now. On these agents,
5dive agent <name> tuiexplains the other way in.Ticket changed by: 5dive-bot