Same /goal Feature, Two Agent Personalities
I've been using Codex's /goal for weeks. When Claude Code recently added it too, I moved over a few tasks Codex couldn't crack. The contrast was stark enough to be worth writing down.
6 posts
I've been using Codex's /goal for weeks. When Claude Code recently added it too, I moved over a few tasks Codex couldn't crack. The contrast was stark enough to be worth writing down.
A friend asked whether I should take an offer as an AI transformation expert. After a three-hour conversation, I wrote down my verdict: don't skimp during the vanguard phase, don't touch IDEs, and don't let your agent become a black box. GPT-5.5 launched two weeks ago; in the remaining 10 weeks, the world will be stunned by a wave of unexpected breakthroughs.
I spent two days automating with the Codex app, burned through a Pro account, and made virtually no progress. Switching to Codex CLI's Goal feature fixed everything immediately. At first I thought the model had gotten dumber, but then I realized: the agent form factor is solidifying, and humans shouldn't be chained to the screen anymore.
Claude told me to 'get some sleep' halfway through a task, and GPT-5.5 killed the direction after a quick probe. After a week with the new models, one thing became clear: no matter how powerful the model gets, the collaborative part still falls on humans.
Two weeks since GPT-5.5, codenamed SPUD, went live, I've more or less stopped opening Claude Code. What surprised me wasn't that it got a few percentage points stronger—it was that after several long-standing weaknesses were fixed all at once, the design philosophy of agents became clear for the first time.
My social media feed is buzzing about GPT-6 being released again. Misinformation has an audience; real information is a niche market. AI is making this worse, not better—which is why I recently pushed my team back to Claude Code.