Remote phone session appends to same thread while open CLI/TUI does not ingest remote events

Open 💬 3 comments Opened May 16, 2026 by monitz87

What version of Codex CLI is running?

0.130.0

What subscription do you have?

Max (200)

Which model were you using?

gpt-5.5 (high reasoning)

What platform is your computer?

Darwin 25.2.0 arm64 arm

What terminal emulator and version are you using (if applicable)?

cmux 0.64.6 (86) [2f96c15c2]

Codex doctor report

not available

What issue are you seeing?

I had a Codex CLI/TUI session open on my machine. I opened the same session
from my phone. The phone session appended user messages and agent work to the
same thread. The CLI/TUI remained open the whole time, but did not receive or
integrate those remote events into its live context. When I continued typing
in the CLI/TUI, it appended a second continuation from stale in-memory context
to the same JSONL transcript.

What steps can reproduce the bug?

Uploaded thread: 019e199a-3d58-7863-b06e-c84a99bd9a87

What is the expected behavior?

Expected:
If a remote client attaches to an existing live CLI/TUI session, remote events
should either:

  • stream back into the CLI/TUI and update its live context, or
  • be rejected/locked/forked explicitly so two clients cannot append divergent

continuations to one linear transcript.

Actual:
Both paths were appended to the same transcript file linearly, but the CLI-
side model context did not include the phone-side segment.

Additional information

_No response_

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗