Repository navigation
Feat: Load existing Codex threads available via codex resume #330
Description
It'd be nice to resume existing threads from pre-t3-code. Loading them all doesn't seem right, so I'd suggest an 'import thread' option when right clicking a project. Input a thread id or select from a list and it adds it.
"Add the ability to import existing Codex threads by thread id. This should be an option on the project right click drop down menu. Use a dialog to show an input for thread ID and a list of recent threads not in the sidebar already."
Reacted by Houssam Elbadissi, Ben Lewis, Tanner Polley, Garrett Hopper, Amine D., Domenic Muskulus, tomotomo, Mario Kiefer, Ricky Winata, Obinna and 14 more
Reacted by Souren Khetcho, Florian Karner and deej-minerva
Activity
timm-u commentedon Mar 9, 2026
Additionally, it would be great if I could import threads from the Codex app into T3 Code, rather than just resuming them. It feels counterintuitive to start from scratch when I already have an extensive conversation history.
siraht commentedon Mar 9, 2026
100% - this is crucial if I'm going to switch to T3 as my daily driver
thorizer commentedon Mar 20, 2026
can't migrate to t3 without resume (too many existing sessions )
tomocrafter commentedon Apr 2, 2026
I also would love to see this feature with claude code
dtown123 commentedon Apr 24, 2026
This app would pretty much be the only thing I ever use if I could resume my existing claude/codex sessions like I can in IDEs/console
0xpaperhead commentedon Apr 28, 2026
I was initially working on just creating that implementation before starting to see other similar issues (such as this one) are already created and it seems like contribution is tightened (for obvious reasons previously outlined by Theo)
I think both providers persist sessions on disk in a stable location, as I reseached:
~/.claude/projects/<encoded_cwd>/<uuid>.jsonl~/.codex/sessions/<YYYY>/<MM>/<DD>/<uuid>.jsonlSessions should also be project scoped.
regardless, both also expose native resume via
claude --resume <id>andcodex resume <id>. The data and the entry point already exist.Layers/ProviderSessionDirectory.tsabstracts session storage on disk.Layers/ProviderSessionReaper.tsmanages session lifecycle.Layers/ClaudeAdapter.tsandLayers/CodexAdapter.tsare the seams for each provider.0xpaperhead commentedon Apr 28, 2026
I made it in my fork
dtown123 commentedon Apr 29, 2026
YES ALMOST THIS EXACTLY. That list should literally appear under the project folder in the side nav instead of the current managed chats. Right where it says "No threads yet"
0xpaperhead commentedon Apr 29, 2026
yep! exactly my change. I tested it and it works. Gonna push to my fork soon.
Also I find myself reusing certain prompts so I am also adding a canned prompts feature
dtown123 commentedon Apr 29, 2026
Please do! One my biggest problems with the current "AI meta" is "prompt hunting" where you remember something you did a few weeks ago, but you don't remember -where- you did it.
Was it codex? cursor? oh wait, maybe it was claude in the home directory?
I love the direction of T3 code, but I don't want it to become another disparate bucket that I have to check. I would prefer it to be the opposite; a one stop shop for any and all of your AI interactions no matter where they began.
0xpaperhead commentedon Apr 30, 2026
yep exactly!! hunting for sessions and where you mentioned what!
I was thinking of adding semantic search across sessions. I like t3code
btw im the dev behind agentgrid.sh :
demo: https://www.tella.tv/video/organize-your-ai-coding-workflow-with-agent-grid-42t5
I even added a master-worker interface within agentgrid where you can talk to any of the workers but also let the orchestrator run your agentic engineering loop (build -> review -> audit -> loop -> PR ->etc...)
0xpaperhead commentedon Apr 30, 2026
@dtown123 it works!
materemias commentedon May 9, 2026
definitely needed also for claude code
dtown123 commentedon May 10, 2026
I took a stab at this, or at least what I thought I wanted. This era of development has made me more brave to attempt things I don't understand, and it seemed like a decent vehicle to fw electron. Well, I got it working.
After all of that, I reached the "polish" phase, and realized something. Yeah, it works, but what am I really gaining here? I get to run all my agents in a single spot, regardless of where I started them, but in a limited mode that will constantly have to be updated in parallel with the existing engine that's already superior.
My original problem was that I want to easily find old sessions, and I converted it in to some quest to have a "single source of truth" when I don't even care about that. I abandoned cursor 6 months ago, and I have scoured cursor for old prompts exactly zero times. That's when I realized I don't even care about old sessions, I just want to find the last one I was working on so I can continue a thought and keep working.
That brings me back to this issue request. I still think it's important, and importing actually seems mostly easy. I do think it should be coupled which some kind of "search" engine where T3 asks to look in your .claude folder (or codex or cursor) for existing chats to search and import.
Amazing job on the codebase T3 team - I learned a lot on this side quest and gained a new level of appreciation for this project. This feels like the next natural evolution in agent management.
flamboh commentedon May 14, 2026
Yeah, it's interesting. I made this issue very early into T3Code being public, but to be honest, I would have barely used this resuming atp. I still think it'd be great to add, but certainly not as relevant as I'd imagined (especially with how much worse long sessions on 5.5 are).
I think loading existing threads would be best as part of a "new user" flow, that's why I wanted it - to try doing something on a codex thread I'd been working on earlier in the day.
I think this issue request still applies, but differently than I imagined initially.
beejsbj commentedon Jun 2, 2026
This could be incredibly powerful too if the conversations being imported are "connected"
Such that you could start a conversation in Codex, continue it in T3 and then continue it again in Codex.
so if it so happens theres a specific ui feature, or you just wanna change flavors. you can.
juliusmarminge commentedon Jun 9, 2026
Closing as a duplicate of #207. Both request importing or resuming existing Codex sessions in T3 Code.
fix(server): new Forgejo issues open and delegate again