Earlier quoted context omitted.
What's the point of this split?
I suspect it's mostly marketing. People think "I don't want code so I won't use Codex" so they get the same thing but labeled Work.
Understanding ChatGPT Work
51–60 of 216 posts
Re: Understanding ChatGPT Work
#52Re: Understanding ChatGPT Work
#53Earlier quoted context omitted.
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.
Occam's Razor would suggest that's because Simon posts good content. You can check his domain history to confirm that not everything Simon posts gets upvoted. https://news.ycombinator.com/from?site=simonwillison.net
Re: Understanding ChatGPT Work
#54I think most people are sleeping on the ChatGPT Work/Codex computer use feature. It's incredibly useful. I can remote in from the app, voice it instructions, then let it work in the background. When I tell it "draft a reply to this email (which it has access to thru the gmail connector) and attach the latest docs" or "fill out this multistep immigration electronic travel authorisation form using my passport files sav…
Maybe for the occasional something. If I had an actual workflow i'd prefer a dedicated tool over the newest chatgpt "do everything" app.
So many tasks I need to do once, or just a few times ever, but they build up. While I'm not sure I'd use it for immigration forms specifically, that's the kind of task that's tedious and done rarely, so a dedicated tool doesn't help because who would be familiar with that tool and have it handy?
Re: Understanding ChatGPT Work
#55The right fix is to set real boundaries and limit agents access. We should never trust it won’t touch forbidden places.
Basically I find this naming work local vs work cloud confusing, users won’t know if it’s touching their files in the sandboxed cloud or a local one
Re: Understanding ChatGPT Work
#56Missing from here is the marketing position. Claude _very_ rapidly gained traction in the business/enterprise space earlier this year with Claude Cowork leading that drive. So successful it was, it lead to Microsoft licensing the Claude Cowork IP and white labelling it as Copilot Cowork (has anything like that ever happened before?!). ChatGPT Work was, imo, largely driven by a panic at OpenAI that they were haemorrha…
Re: Understanding ChatGPT Work
#57I think most people are sleeping on the ChatGPT Work/Codex computer use feature. It's incredibly useful. I can remote in from the app, voice it instructions, then let it work in the background. When I tell it "draft a reply to this email (which it has access to thru the gmail connector) and attach the latest docs" or "fill out this multistep immigration electronic travel authorisation form using my passport files sav…
Maybe for the occasional something. If I had an actual workflow i'd prefer a dedicated tool over the newest chatgpt "do everything" app.
Re: Understanding ChatGPT Work
#58Re: Understanding ChatGPT Work
#59I just updated the article to link to this site: https://codex-tool-reference.simonw.chatgpt.site/ Which I created using this prompt in a fresh Work session: > Build a site that lists every one of your tools - nearly grouped into categories - and for each one explain what it does. Try to exactly duplicate arguments and tool descriptions where possible. Design aesthetic should be technical docs, minimal flare UPDATE:…
You can get it to run scripts direct from the prompt.
Try...
Run the script below in your sandbox
message="I'm running in a bash sandbox"
printf '\n' "$message" printf ' \ ^__^\n' printf ' \ (oo)\_______\n' printf ' (__)\ )\/\\\n' printf ' ||----w |\n\n'
printf 'User: '; whoami printf 'Host: '; hostname printf 'System: '; uname printf 'Folder: '; pwd printf '\nWorkspace:\n' tree
I have some more examples here -> https://bionic-gpt.com/architect-course/ai-computer/sandboxe...