People keep asking for this w/ Codex, too, and I really regret that both labs seem inclined to listen.
If you ask a thinking/research type question in 'Chat' versus 'Work' mode in these products -- say, something complex about politics, or do a multiturn business strategy, or want to work thru a new concept, you get very different answers.
The harness, steering, etc. in the chat/reasoning products is so much better for this type of question (that doesn't require code as a primary substrate).
Even as someone who mainlines like, 7 coding agents at all times, I regret that productivity fever will mean the regression of think-first-act-later AI UX.
I hope not Chat is still all you can eat and Work uses Codex tokens. I can see why they would want people to think they wanted this without thinking about how it currently works. If Chat starts eating tokens then there is not much reason to use Chat other than most people don't live in the command line like developers. Claude Chat / Cowork already eats tokens either way so not much of a change really. I have never used Work since if I want access to local files the CLI is a much better interface combined with an IDE, but can see the appeal to non-developers.
This is my main reason for not using Work. I was tempted to use a few "scheduled tasks" in ChatGPT, but once I found out they used Codex tokens I stopped creating new ones.
I recommend using Work sparingly because sometimes it is the better choice, but I do ration it. With Claude I simply don't use the web/app chat at all (and I have no idea what Cowork even does ngl, never used it) I think there's a Claude Design? No idea why I would need it (mostly, why I would spend tokens on it lol)
Claude Design is good at making a bunch of UI pages in a single design look consistent, and it's better at making an initial starting UI than just asking Claude Code. Think of it like Anthropic's version of Figma. It honestly works pretty good and I use it often and feel that it saved me a lot of time. It's pretty token heavy though.
I built a terminal control plane and added an MCP server that runs on my Mac. It lets MCP clients create terminal sessions, send messages, read the contents, etc on my Mac.
The terminal sessions are running Luna on XHigh (on Pi) and GPT 6 Pro on ChatGPT.com is the main orchestrator.
Since ChatGPT and Codex have different limits, I can have 6 Pro orchestrate the Luna sessions. Using voice mode to talk back and forth about the software factory is really nice. Will be open-sourcing soon.
Sherveen · · focus · HN ↗
If you ask a thinking/research type question in 'Chat' versus 'Work' mode in these products -- say, something complex about politics, or do a multiturn business strategy, or want to work thru a new concept, you get very different answers.
The harness, steering, etc. in the chat/reasoning products is so much better for this type of question (that doesn't require code as a primary substrate).
Even as someone who mainlines like, 7 coding agents at all times, I regret that productivity fever will mean the regression of think-first-act-later AI UX.
Sn0wCoder · · focus · HN ↗
no_no_no_yes · · focus · HN ↗
I already burn through Codex too fast.
ChickeNES · · focus · HN ↗
sigseg1v · · focus · HN ↗
theturtletalks · · focus · HN ↗
The terminal sessions are running Luna on XHigh (on Pi) and GPT 6 Pro on ChatGPT.com is the main orchestrator.
Since ChatGPT and Codex have different limits, I can have 6 Pro orchestrate the Luna sessions. Using voice mode to talk back and forth about the software factory is really nice. Will be open-sourcing soon.
tekacs · · focus · HN ↗
kcrwfrd_ · · focus · HN ↗