That's correct, and also why ChatGPT Work is DOA for me personally.
I need 100% of my Codex budget for Codex.
Too bad, it would have been nice to have a few extra features for the chat interface.
I still might try ChatGPT Work sometime if there was some feature I couldn't get from Shelley.
It gets the task done in 5-10 minutes. It's it bit slow since I'm not paying extra for ultrafast mode, but it gets the job done. Frees up the brain to do other tasks.
It's exactly like vibe coding but for computer tasks.
> people are sleeping on the ChatGPT Work/Codex
just in general. I find it to be far superior (imo) for all tasks atm. Claude just overdoes things in writing, coding, architecture, etc
It's both awesome and scary at the same time to realising that most AI these days can work on something like this that's official and tedious, and probably not screw up too much (or do better at it than some people with fat fingers).
—
Or Codex from the ChatGPT app.
If you have supplied tooling on your system, you have access to all of this and more.
I think the idea is most people don’t have a machine up and available, nor maintain skills for interacting with their core services?
One thing that keeps me from adopting codex more deeply is the architecture around mobile access.
Claude Code makes this trivial /rc and you are done.
Codex requires you run the desktop app and additional authentication requirements. The result of this has been codex is almost always relegated to fleet worker rather than orchestrator.
I wonder if the emphasis on this work feature has something to do w the persistent hurdles to remote control if codex sessions.
Kuinox•45m ago
So it's not completely headless.
But when I tried it, the remote control completely froze after a few seconds.