With DevDay tomorrow, everyone’s understandably wondering what the next Codex will look like 👀 But the speed of model releases is making me think about a different problem. If I have an agent working on a project for weeks: accumulating context, decisions, unfinished tasks, preferences, mistakes: why should all of that be conceptually attached to Claude Code, Codex, or any particular model? Ideally I’d want the opposite: project stays, worker identity stays, memory stays, model changes. New Codex is better? Swap it in. Claude is better for a particular task? Use Claude. Something else wins six months from now? Fine. The weird thing is that today switching models still often feels like handing a project to a new employee with a folder of notes. I’m curious whether people actually want this separation, though. If you could upgrade/swap the model underneath your coding agent without changing anything else about the “worker”, would you? Or is there something genuinely valuable about the worker being Claude/Codex-specific? submitted by /u/Disastrous-Radio-732
Originally posted by u/Disastrous-Radio-732 on r/ClaudeCode