[furyofantares]

I don't really mind hopping between claude/codex/glm/kimi except I don't know a good way to resume as session across agent harnesses.

Normally I'd just have it write out what it's doing to a file, if I need to transfer context, but if it goes down mid-session that's a no-go.

I think people have built tools for this, and of course you could reasonably vibe one yourself, but I don't really trust something like that to work reliably or in an ongoing manner.

Maybe it should just be a skill.

[alasano]

switch to Pi.dev or any other multi model harness, you can switch between models every message if you feel like it.

Anthropic have blocked usage of your subscription however with third party harnesses.

[furyofantares]

> Anthropic have blocked usage of your subscription however with third party harnesses.

This is the main reason I use different harnesses, but I also expect (could be wrong) codex is better with codex harness (due to training on it's specific tools) than with other harnesses. I use opencode for everything that's not claude/codex.

[philipbjorge]

You might search for a concept like `/handoff` that's in ampcode. I'm sure someone's built a skill for just this.

[OccamsMirror]

That's not going to work if the service is down, however.

[philipbjorge]

Ahh good point -- I've handled this by switching my harness to `pi` but recognize that may not be for everyone and doesn't directly address OP's question.

[serf]

self hosted honcho (or other memory systems) and an api agnostic harness gets you most the way there.

[vx_r]

you never rely on agent's own memory system. create memory system of your own

[datadrivenangel]

kilocode allows you to switch between models mid session!

[furyofantares]

Yeah - it's switching agents (harnesses) that's the hard part!