Codex support uses same-session resume.
LMAS starts the long-running job in tmux, records the handoff, waits outside the agent turn, and resumes the Codex thread when the process finishes.
Install
npx let-my-agent-sleep install --agent codexRestart Codex after installing the LMAS skill. The Codex session must be resumable from the machine where the job is running.
Live server and SSH mode
For an already-running TUI to wake immediately, start Codex's own app server and attach the TUI to it. LMAS installs no service, wrapper, or alternate Codex binary.
codex app-server --listen unix://
# From the terminal where you use Codex:
codex --remote unix://Keep the first command alive with the same tmux or systemd setup already used for remote services. LMAS discovers the same-user default socket and starts the completion turn through that owner. It never installs, bootstraps, or starts the app server. Codex Desktop remains a secondary live route; if neither owner exists, LMAS falls back to a separate codex exec resume process.
What the agent should do
- Use the installed
let-my-agent-sleepskill for commands that would require waiting. - Start the command with LMAS and return only the handoff summary.
- After
LMAS_HANDOFF v1, end the turn instead of sleeping, polling, or repeatedly continuing.
Completion
When the process exits, LMAS writes a completion event with the run id, status, exit code, command, stdout, stderr, metadata, artifacts directory, and finish time. If adapter.log reports a successful live wake, the already-running owner started the completion turn and no reload is required. If it reports the separate-process fallback, reload or reopen a Desktop task or CLI TUI that stayed open across completion before continuing. An ambiguous post-dispatch result never triggers an automatic fallback, preventing duplicate completion turns.