Claude Code to Codex: Same Context, Zero Setup, One Asset I Own

The context was not in the model.

It was not in the tool.

It was an asset I owned.

Today I ran a test that I consider a real benchmark for the ICM methodology.

I built a folder structure for Curiositas: one set of files designed to hold state, routing, identity, organizational knowledge, operating context, and the way we work.

First, I asked Claude Code to pick up the work.

Correct response. Right context. Correct identity. Current state of the work recognized.

Then I opened Codex.

I had never used it before. Zero setup. Same exact question.

It read the right files by itself, understood the routing, and returned the same context: identity, state, open tasks, and direction of the work.

Different words. Same content.

Everything is documented in the video.

Then I asked Claude to evaluate the result. The screenshot says: “solid result... this is basically a clean pass on the portability test.”

And that is the point.

This is real portability.

This is real persistence.

It means building something that does not belong to the platform, the model, or the AI tool I happen to open that day.

It belongs to the structure underneath.

It belongs to the asset I am building.

I had already tried to solve this problem before finding ICM.

I saw AI tools as fragmented by nature: a new tool every day, context scattered everywhere, work spread across different places, and nothing that truly remained mine.

My answer had been to build my own framework.

It taught me a lot. But in the end, it was becoming as fragmented as the problem it was trying to solve. I was working a lot, but the result kept moving further away.

ICM is the layer I was missing.

You are no longer designing inside the tool or inside the model.

You are designing the structure that survives both.

Jake Van Clief describes this as the future of how we will build software: a new way of communicating with machines.

After this test, I understand why.

I worked on this Curiositas lobby for half a day.

From now on, I will improve it every day. I will make it more efficient and more tailored to me, to my way of working, to my processes, and to my company.

Once I have done it for myself, I will be able to do it for others: clients, teams, builders, and people who want to use AI without losing control of their work.

That is where I see the real value.

Not in the single output.

In the system that allows you to build, remember, improve, and restart every day from the same point.

Stay curious 🫡

17 comments

Claude Code to Codex: Same Context, Zero Setup, One Asset I Own