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.
The fact that it doesn't work well today doesn't invalidate the user need. Not everyone wants a terminal style interface. Traditional UX makes more sense especially if say you are accessing existing plugins and say kicking off a scheduling task - no way would I want to do that via a chat interface if I have the option.
Agree, and it allows ordinary users to have a taste of both worlds, instead of being like: "eww, what is this black box and why doesn't my mouse work"
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.
Tactical45 · · focus · HN ↗
sudo_cowsay · · focus · HN ↗