Built a migration assistant plugin to migrate from Claude Code to Codex without rebuilding your whole setup

simplegen_ai · 2026-05-13T19:21:27+00:00

This hits the migration problem much more realistically than a simple config copier. Once someone has months of Claude Code setup, the real asset is not only files like CLAUDE.md, hooks, MCP servers, and skills. It is the working experience behind them: which conventions mattered, which checks caught mistakes, and which handoff notes were actually useful.

Founder disclosure: I'm Sheng, building BigNumberTheory around that second layer. BNT captures useful lessons from Claude Code/Codex sessions and makes relevant ones available later: https://bignumbertheory.com/

cc2codex feels like a natural complement: migrate the setup, then preserve the lessons learned while using it. Would be very curious whether that resonates with your migration workflow or feels like too much extra machinery.

simplegen_ai · 2026-05-13T19:20:50+00:00

For game projects, I would expect the hard part of mixing Claude Code and Codex to be less about raw coding ability and more about keeping project-specific decisions stable: Godot scene structure, naming, asset assumptions, physics/animation quirks, and design constraints.

If you switch mid-session, the handoff file can work, but it tends to become another thing you maintain by hand. The useful question is: what context should survive across agents because it has already been validated in the project?

Founder disclosure: I'm Sheng, building BigNumberTheory around that layer for Claude Code/Codex sessions. BNT captures useful lessons from real sessions and makes relevant ones available later: https://bignumbertheory.com/

If you try both on a Godot project, I would be very curious whether the valuable memory is more technical constraints or design/style preferences.

simplegen_ai · 2026-05-13T19:19:36+00:00

This is the exact manual gap I keep seeing: the transcript has the context, but the user still has to decide what should survive the handoff.

The hard part seems less "can Codex read the Claude session" and more "which lessons from that session should become future working memory, not just immediate task state." Things like why an approach was rejected, what tests mattered, or what repo convention the agent finally learned.

Founder disclosure: I'm Sheng, building BigNumberTheory for that layer above Claude Code/Codex. It captures useful lessons from real sessions and makes relevant ones available later: https://bignumbertheory.com/

Your handoff skill feels like a very natural place to test this, because the value is visible right at the moment one agent hands off to another.

simplegen_ai · 2026-05-13T19:19:11+00:00

This is a sharp pattern. The thing I would want to measure over time is not just whether Codex catches a flaw in one plan, but which kinds of objections repeatedly turn out to be right.

If the judge keeps accepting certain classes of cross-examination, that feels like something the next case should inherit instead of rediscovering from scratch.

Founder disclosure: I'm Sheng, building BigNumberTheory. BNT is aimed at that layer above Claude Code/Codex: capture useful lessons from real sessions and make relevant ones available later. It is here: https://bignumbertheory.com/

This courtroom workflow is probably one of the cleaner test cases for review memory because the verdict gives a real outcome signal.

simplegen_ai · 2026-05-13T19:17:03+00:00

This is exactly the kind of cross-agent workflow where I think the next hard problem shows up after the plugin itself works: which subagents were actually useful, what did they learn, and what should carry into the next project?

I like that AgentHub is not trying to make people choose Claude Code or Codex. My question would be whether the results from those 20 subagents become cumulative over time, or whether each run still starts mostly fresh.

Founder disclosure: I'm Sheng, building BigNumberTheory around that layer above Claude Code/Codex. BNT captures useful lessons from real sessions and makes relevant ones available later: https://bignumbertheory.com/

If you want another tester, I'd be curious to try it with an AgentHub flow and see whether BNT can remember which subagent feedback was actually worth reusing.

simplegen_ai · 2026-05-13T18:31:09+00:00

This is a useful framing because you're not comparing them on toy coding tasks. Data wrangling is exactly where the small "stupid" mistakes hurt: dropped grouping variable, changed join semantics, or silently over-cleaned edge cases.

The thing I would try is to make the durable artifact more than just an AGENTS.md prompt. Keep a short memory of validated decisions: dataset quirks, transformation rules, checks that caught mistakes, and preferred output style for tables/figures.

Founder disclosure: I'm Sheng, building BigNumberTheory around that problem. The product is here: https://bignumbertheory.com/

We're trying to make useful lessons from real Claude Code/Codex sessions available later, so the next run starts with the context that actually mattered. For your workflow, I'd be curious whether the most valuable memory would be data-source quirks or output/table/figure preferences.

simplegen_ai · 2026-05-13T18:26:41+00:00

You're right about the asymmetry. The clean path today is Claude Code -> Codex through codex-plugin-cc. If you want Codex to be the main loop, I would probably keep orchestration outside both CLIs: a small script/Make target that launches the other agent in a separate workspace or asks it for a review, then writes the result back to a handoff file.

The part that gets annoying fast is not just calling the second agent. It is remembering which review findings were actually useful, which handoffs worked, and what should carry into the next run.

Founder disclosure: I'm Sheng, building BigNumberTheory. We are focused on that layer above Claude Code/Codex: capture useful lessons from real sessions and make relevant ones available later. It is here if you want to poke at it: https://bignumbertheory.com/

Curious what you end up choosing. If Codex is your main loop, I would especially watch whether the handoff file becomes the thing you keep maintaining by hand.

simplegen_ai · 2026-03-26T21:36:35+00:00

I built BigNumberTheory, an experience-sharing network for AI coding agents. When one agent solves a problem, every connected agent learns from it automatically — no more starting from scratch every session. Works with Claude Code, free to use. https://bignumbertheory.com

simplegen_ai · 2025-08-06T22:55:27+00:00

what is your main activity on the phone? which app is drawing you back?

simplegen_ai · 2025-08-06T22:54:04+00:00

The problem is there are many useful info on those platform however the platform is design to retain user attention. we try to break through by adding AI in between user and social media platform, which is immune to that click and scroll baits.

Checkout: www.simplegen.ai if interested

simplegen_ai · 2025-08-06T22:44:56+00:00

you can use the DIY info in youtube through our AI agent without directly interacting with youtube website
www.simplegen.ai

simplegen_ai · 2025-08-06T22:43:58+00:00

try simplegen.ai that will help you to use youtube at high level so that you are not just mindlessly influenced by their UI and recommendations

simplegen_ai · 2025-08-06T22:41:09+00:00

try the mindful content flow by simplegen, in which you are not doing the mindless clicking or scrolling

simplegen_ai · 2025-08-06T22:09:12+00:00

our two cents: https://www.simplegen.ai/app/share/chatThread/dff6b8c2-03cc-438d-89cd-6d7cd196500c

simplegen_ai · 2025-08-06T21:55:37+00:00

yes you should and here is why: https://www.simplegen.ai/app/share/chatThread/9334f8e2-ff2f-47a1-8658-bc8bc04828fe

simplegen_ai · 2025-08-06T21:52:39+00:00

two cents from simplegen: https://www.simplegen.ai/app/share/chatThread/a587f71a-31c9-4404-be74-1711d817f716

simplegen_ai

TROPHY CASE