Can't resume threads made from a profile with another model

Resolved 💬 1 comment Opened May 14, 2026 by RodriMora Closed May 14, 2026

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

0.130.0

What subscription do you have?

Pro

What platform is your computer?

Linux 7.0.3-arch1-2 x86_64 unknown

What issue are you seeing?

I can start a session using a profile with another model/provider set up, eg:
codex --profile test --yolo

Then i start a thread as usual with a promt

If I exit that thread and start another session without a profile, eg

codex --yolo

And try to /resume to the previous thread, it won't show. But, I can codex resume xxxx to force to resume the previous thread if i have the id. So it's clearly possible, but the /resume UI does not allow it.

What steps can reproduce the bug?

The same happens the other way around, starting a thread without a profile and then switching to a profile:

codex --yolo
prompt anything, exit codex
codex --profile test --yolo
/resume > previous thread does not appear
codex --profile test --yolo resume xxxxxx does work to resume to it

What is the expected behavior?

/resume should list all the threads made with other profile, or at least have a toggle, similar to "all/cwd" to allow from current profile or all profiles, as it's clearly possible to do it if you force it via codex resume threadid

Additional information

_No response_

View original on GitHub ↗

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