Transport failed: Space limit exceeded: Message too long

Open 💬 1 comment Opened Jun 22, 2026 by int19h

What version of the Codex App are you using (From “About Codex” dialog)?

0.141.0

What subscription do you have?

Max

What platform is your computer?

Linux 6.17.0-35-generic aarch64 unknown

What issue are you seeing?

When trying to attach to a long-running Codex session from the CLI app using /resume, I get:

■ Failed to resume session from /home/int19h.linux/.codex/sessions/2026/06/09/rollout-2026-06-09T22-34-02-019eb005-f975-74c0-a3e9-0254240768a8.jsonl: thread/resume failed during TUI bootstrap: thread/resume
transport error: remote app server at `unix:///home/int19h.linux/.codex/app-server-control/app-server-control.sock` transport failed: Space limit exceeded: Message too long: 156619224 > 134217728
ERROR: remote app server at `unix:///home/int19h.linux/.codex/app-server-control/app-server-control.sock` transport failed: Space limit exceeded: Message too long: 156619224 > 134217728

It should be noted that the session is still active - it has the Codex macOS desktop app remote-connected to it, and while the latter is lagging very badly when this chat is opened, it can nevertheless function well enough that I can monitor it. So I would expect the CLI to be able to do so at least as well, or failing that, give a clearer error message.

What steps can reproduce the bug?

Session ID: 019ea5e9-f1bb-7be3-a5e0-b7eaec39501e

What is the expected behavior?

So I would expect the CLI to be able to do so at least as well, or failing that, give a clearer error message.

Additional information

The session in question is indeed very long - the JSONL for it is 478,823,661 bytes, and it's about a week worth of the agent iterating non-stop on a work item. I can share the full logs if needed.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗