The pattern across Claude Code, Codex and Cursor does seem to be converging: gather context, make a plan, execute, then verify.

What feels less standardized is how much control the user gets between those stages. Settings like showClearContextOnPlanAccept and disableAutoMode are interesting because they expose that boundary between “agent decides” and “human reviews before execution.”

That seems like the part where different coding agents will continue to feel very different in practice.

As costs come down, these dials will shift too. There are many configs which give control simply for the sake of saving tokens.

> Is anyone collecting and writing on how to understand this architectural style?

Are we on the same site? Is anyone writing about anything else?

The blog post this discussion is for is one of the first in depth discussions I've seen of how these coding agents work. Most posts cover how to use them, not their internals and how they operate.