After some time with it...

It has a tendency to do things without asking, a trait I'd associated more with the Claude Opus & Sonnet models than with Codex & GPT in the past. Specifically I've seen it go and update e.g. README.md files filling it with recenty-biased gibberish that means nothing to the user (e.g. very specific technical notes related to what it was currently working on) or staging and adding design/spec documents that were meant to just be working documents. In general it tends to behave more aggressively with git, if you let it get its hands on it. It has stronger "opinions" on that stuff, that don't always agree with me.

I'm going to have to update my prompts, I think. But I'm not used to this kind of thing in Codex, which in the past has been much more explicit and cautious, and one of the reasons I've preferred it over Claude.

It is very "smart." It also has a tendency to yak-shave things. Producing huge volumes of correctness and regression tests and nitting over e.g. very minor variances.

One thing that is "entertaining" is letting two separate instances review each other's code. They will endlessly find things to nit at.