Model Releases
if you bounce between claude code and codex, that’s completely normal. the models are good at different things and everyone's workflow is dy…
if you bounce between claude code and codex, that’s completely normal. the models are good at different things and everyone's workflow is dynamic but you’re also paying multiple subscriptions, constan
if you bounce between claude code and codex, that’s completely normal. the models are good at different things and everyone's workflow is dynamic but you’re also paying multiple subscriptions, constantly rebuilding your context, and susceptible to any of the providers randomly nerfing your experience according to "business needs." switching models is easy when everything is stateless, but agents aren't stateless. the harness owns the context, memory, preferences, compaction, tools, workflows, etc therefore instead of asking the question "what model are you using?" , we should ask "who owns the harness around the model?" i think the winning agent UX is model-agnostic, lets you choose the best model for the job, and gives you more control over your context instead of trapping it with one provider
Related
- if you don't own your harness, you don't own your memory this is so true. even though Codex is an open source, it generates an encrypted com…
- With closed agent platforms like Claude Managed Agents, your agent's memory belongs to them, not you. It's locked behind their API. Agent in…
- For AI agents, when you want every last bit of what is possible, open source is turning out to be the only way
- Hot take: I can't see any startup building their critical core operations on Claude Managed Agents or any proprietary harness as investable.…
- Deep Agents Deploy: an open alternative to Claude Managed Agents
- if you want claude's managed agents w/o model provider lock in, this is the path!
deepagents deploylets you deploy an agent built on our …
Source: Harrison Chase (X) | 2026-04-12