Skip to content

Codex is not able to access its own background processes after compactation #16580

@iblue

Description

@iblue

What version of Codex CLI is running?

codex-cli 0.118.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.4

What platform is your computer?

Linux 6.12.[redacted].x86_64 x86_64 [redacted]

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

xfce4-terminal

What issue are you seeing?

Codex started a long running process (takes about 30 min to complete). After compaction, it is not able to access it. Then gaslights me that no background process is running. After questioning explains that it needs the session_id of the terminal to access the background processes and that that go lost. Tells me, it is a tooling issue.

What steps can reproduce the bug?

Uploaded thread: 019d4eab-adfa-7b30-92dd-ffe43e6d596f

What is the expected behavior?

Codex should not require a session_id to access its background jobs, should be able to list background jobs it started and query them OR session_id should survive compaction in any case.

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    agentIssues related to the core agent loopbugSomething isn't workingcontextIssues related to context management (including compaction)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions