Live data from Hacker News

Understanding ChatGPT Work

simonwillison.net

31–40 of 216 posts

Re: Understanding ChatGPT Work

#31

Codex in ChatGPT Desktop + 5.6Sol is my daily driver for non-coding things, and it's great. FWIW, I've not explored what differentiates Codex and Work modes- Simon notes that Work 'feels more like regular Codex re-skinned'. OpenAI seems to say that they're 'optimized' for SWDev and general knowledge work respectively, but reading between the lines- I suspect that yes, this boils down to a reskin. I have been of the o…

I agree on the shotgun marriage of the various modes. It was super disconcerting, as a Claude desktop user, to get a sudden redesign and push to something I will never use on my personal laptop.

Also Big +1 that they need to do a clean launch, marketing push, etc. Even if it is just a reskin, having dedicated branding, a strong privacy promise, random vague-posted fluff around "enterprise-ready", and a "Contact Us" pricing that gets you SSO for $150/u/mo. There is too much baggage with the chat app.

I feel the same using Claude Code on mobile. Or Claude Design, which has to go through mobile safari. Give me an app whose interface is optimized for product/dev. Yes, I should be able to do anything on each, but I have specific needs in different contexts. That's what "products" are.

Re: Understanding ChatGPT Work

#32

Earlier quoted context omitted.

Less bureaucracy should be the focus of AI marketing, rather than global superintelligent robots or smut generation

Bureaucracy is a major part of many corporate leader’s roles. That might not be the best sales line

And that is exactly why AI marketing touts ability to replace programmers, when in reality it is much better suited to replace middle management between client and programmers...

Re: Understanding ChatGPT Work

#33
I recently figured out that I could use ChatGPT Work on my Pixel Phone to build native Android apps. It builds the app and you can then directly download/install the APK. So now I just build small utility apps on-the-go whenever I need them :)

Re: Understanding ChatGPT Work

#35

  > OpenAI could make this a lot less confusing
  > Figuring this all out took way more work than it should have.
Welcome to a generic large corporation, where they spend billions on making a product, and $0 on checking if the product makes any sense to a real user.

Re: Understanding ChatGPT Work

#36
> My lethal trifecta model warns about the risks inherent in any agent system that combines access to private data with exposure to untrusted content and a way to communicate stolen information back to an attacker.

> ChatGPT Work combines all three!

The ChatGPT Work model would actually feel safer to me if they created a privacy boundary between the container-managing agent (browser operator/VM manager/code runner/etc) and the chatbot agent. Instead of me not typing privacy-sensitive things to the chatbot to avoid having them in my history, the chatbot would keep my history private from the container agent except on a need-to-know basis. That would remove the "access to private data" from the container's trifecta.

Not perfectly safe of course, just safer. Particularly if I could review the logs between the two agents.

Re: Understanding ChatGPT Work

#37

[flagged]

If it makes you feel any better, I have just upvoted every submission made by your account.

I mean he is kind of speaking truth. Anything Simon posts seems to get upvoted and this article is nothing special or interesting. It's like a tutorial for a feature of a ChatGPT subscription.... Cool.

Re: Understanding ChatGPT Work

#39

> OpenAI could make this a lot less confusing > Figuring this all out took way more work than it should have. Welcome to a generic large corporation, where they spend billions on making a product, and $0 on checking if the product makes any sense to a real user.

[dead]

Re: Understanding ChatGPT Work

#40
post #30

It’s been part of the strategy from both OpenAI and Anthropic to split users into “devs” and “knowledge workers”. Hence Codex and Work (or Claude Code vs Cowork), and Chat is stuck in between. Codex can do everything Work can do and most non devs I know use Codex - from sales ppl doing weekly prioritisation of pipelines and customised email reach outs, to project managers using it as a living LLMWiki of all the proje…

What's the point of this split?
Post reply on HN