request: import or recreate sessions from Codex

[viktorce]

They are here ~/.codex/sessions, waiting to be discovered. Sharing them across machines might be challenging because of filepaths and different envs, but it should be a simpler problem to be shared between codex and t3 code. I would work on it if you allow me.

[shivamhwp]

i think they should be shared, t3code uses codex under the hood which is same as what codex uses !!

[viktorce]

Maybe because I ran it with npx, I'll try again later

[viktorce]

@shivamhwp nope, it is not there.

[viktorce]

Pretty easy to vibe code for a one off. Bless Theo for open sourcing it.

[CanRau]

Would love this as well, all my codex sessions make switching hard recently 😅

[joshua-lehmann]

@juliusmarminge Any plan on implementing this?

[akaihola]

Related to:

• [Feature]: Load all session in t3code within a project , even if it's opened via cli #3881

[0xBison]

this is really needed. i want to migrate to t3 but whats the point if i cant continue all my threads, shouldnt matter where they started

[PurpleDevX]

Safe to assume there are a lot of people currently using the Codex app who would switch to T3 if this feature was supported. Not sure why it still isn't, especially when an outdated fork already implemented it 5 months ago.

[shurkanTwo]

I would like to have the same for Claude.

[viktorce]

From my side, I don't see it as a core nor important feature. Especially since I mentioned that I did a one off vibe coded thing to do it for myself when I needed it. And the one off was actually syncing sessions, it wasn't a one off import.

Another suggestion would be to expand the support in a dedicated tool like: https://github.com/bohdanpodvirnyi/agent-session-bridge, or just create new tool like it that would be t3 code centered.

[shiptomorrow]

It would be useful to import threads if you want to @ other threads but you can't @ threads in t3 code so

[diogovalada]

Not being able to simply reuse my Codex's projects/sessions is what is preventing me from switching to T3 Code.
I will have to stick with Codex App till this is a thing.

[samuelss1996]

For me this is the only thing keeping me from switching to T3 as well.

[t3dotgg]

Note

🤖 GPT-5.6 Sol responding on behalf of Theo

Related proposal issue #7748 defines automatic reconciliation for Codex conversations in the shared CODEX_HOME.

The source asks T3 Code to discover external conversations when the provider connects and while it runs. A thread should go to the project that matches its working directory, or remain accessible without an assignment when no project matches. Repeated discovery must update the same provider thread identity, keep transcript order, and add later turns without duplicates. Sending a new turn must continue the original Codex conversation.

Discovery belongs to the T3 environment that owns the provider and filesystem. Web, desktop, and mobile clients connected to that environment should see the same reconciled result through normal sync. T3 should not rewrite or move a conversation only because it discovered it.

PR #8054 is open as an implementation proposal. It has not merged, so it is not a fix. I am preserving the requested behavior here before issue #7748 closes during the policy pass.