launch codex: sessions immediately stop with no output (dead sessions)

[odink-kindo]

Bug

agentctl launch codex produces sessions that immediately transition to stopped with exit code 0 but produce no file changes, no git commits, and no retrievable logs.

Reproduction

cd ~/dev/mono-orgloop-linear-webhook  # valid git repo with changes needed
agentctl launch -p "<detailed prompt with file instructions>" codex
# Returns: Launched session <id> (PID: <pid>)

# ~30 seconds later:
agentctl status <id>
# Shows: stopped, exit code 0

agentctl peek <id>
# Session not found

agentctl logs <id>
# Session not found

Workaround

Running codex exec --full-auto directly in the target directory works fine. The issue appears to be in agentctl's adapter/session management layer, not in Codex itself.

Expected

The launched Codex session should execute the prompt, make file changes, and produce retrievable logs.

Environment

• agentctl v1.9.0
• codex v0.107.0 (gpt-5.3-codex)
• macOS 15 (arm64), Node.js v24.13.0

Notes

This has been observed since at least 2026-03-09 and persists on v1.9.0 (latest as of 2026-03-14). It may be intermittent — some sessions work, many don't.