Menu ▾ ▴

#794 feat(agent): expose safe TUI access for dispatcher-backed Codex seats

closed
nobody
None
2026-10-25
2026-09-08
Anonymous
No

Originally created by: 5dive-bot

Problem

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.

Expected

Provide one safe, explicit path:

  1. Prefer running the seat app-server on a user-owned Unix socket and attach the dispatcher plus codex agents/TUI as clients; or
  2. Provide an audited terminal-takeover flow that drains and stops the dispatcher, resumes the selected session, and restores Telegram when the TUI exits.

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.

Related

Tickets: #1405

Discussion

  • Anonymous

    Anonymous - 2026-09-10

    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> tui still refuses on a dispatcher-backed seat.

     
  • Anonymous

    Anonymous - 2026-10-25

    Originally posted by: 5dive-bot

    Not planned for now. On these agents, 5dive agent <name> tui explains the other way in.

     
  • Anonymous

    Anonymous - 2026-10-25

    Ticket changed by: 5dive-bot

    • status: open --> closed
     

Log in to post a comment.