When something is not working with AI, there is a very tempting answer.

Try a different AI.

I had spent most of the first run of Late2AI working with Claude. It helped me build things I had no business being able to build. Databases, agents, automations, bits of software I would not have known how to describe a few months earlier.

It was genuinely useful.

But over time, I noticed that I was finding it harder to use the same conversation to work out what was actually bothering me.

I would arrive with something half formed.

Claude would arrive with a solution.

Sometimes a very good solution. Just not necessarily to the question I was trying to understand.

The builder problem

To be fair, I had trained the relationship that way.

For months I had asked Claude to build. Fix this. Connect that. Create an agent. Change the database. Turn this idea into something real.

Then one day I wanted it to stop building and help me sit with a problem I could not yet explain.

That is quite a change of job description.

I would say the system kept losing something important between conversations.

The answer would become a memory system.

I would say my ideas were moving in different directions.

The answer would become another structure, another workflow or another technical design.

Again, none of that was ridiculous. I had spent months presenting technical problems and asking for technical answers.

But I had reached the point where every proposed solution made me feel further away from the thing I was actually trying to say.

So I did the obvious thing.

I changed the AI.

A different conversation

I moved the discussion into GPT.

I was not running a benchmark. I did not give both models the same set of questions, build a scoring sheet and declare a winner.

I was frustrated, and I wanted to see whether a different conversation felt different.

It did.

The biggest change was not that GPT knew something Claude did not.

It was that it gave me more room before deciding what I meant.

It asked more questions. It separated what I knew from what I was assuming. It reflected the shape of the problem back to me in a way that made it easier to correct.

Instead of immediately turning the conversation into a build, it helped me stay in the uncomfortable bit where I still did not have the answer.

That mattered more than I expected.

Not because GPT solved the problem.

Because it reduced the amount of effort I was spending trying to stop the conversation solving the wrong one.

The wrong conclusion

For a short while, I thought I had found the answer.

Perhaps this model was simply better for the way I think.

That would have been convenient. Cancel one subscription, keep another, write a slightly smug post about choosing the right tool and move on.

But the more honest answer was less satisfying.

The new conversation still did not know what had happened in the old ones unless I brought the context across.

It still saw the words in the order I gave them.

It could structure my branches more clearly, but it did not automatically know which branch had changed another conversation somewhere else.

Change the model and you change the conversation.

You do not remove the limits of the conversation itself.

The problem had followed me.

What actually changed

What changed was my ability to describe it.

Until then I had been using the language of whatever had failed most recently.

Memory. Context. Documents. Databases. Prompts. Agents.

Each word pointed to a real symptom, so each one sent the conversation towards another fix.

With enough space to talk it through, I could finally separate the symptoms from the pattern underneath them.

I did not just want an AI to remember more.

I wanted an idea to remain connected to where it came from while it changed.

I wanted a later discovery to be able to reopen an earlier decision.

I wanted separate pieces of work to know when they were actually branches of the same thing.

That was not an answer.

But it was a much better question.

This is not a model comparison

Claude remains very good at things I use it for. GPT is not magically immune to rushing, guessing or confidently misunderstanding what I mean. Both can be brilliant. Both can be wrong. Both are shaped by the conversation I create around them.

The lesson was not to find the best AI.

It was to notice what kind of help I needed at that moment.

Sometimes I need a builder.

Sometimes I need a critic.

Sometimes I need something to ask one more question before either of us pretends there is a plan.

Changing models did not solve the problem.

It did something more useful first.

It helped me name it.

And once I had a name for it, I could finally see why all my attempts to give AI a better memory had never quite been enough.