It tells ChatGPT Work how to launch a Playwright instance via its Node.js REPL, and tells it to run:
nodeRepl.write(await browser.documentation());
That method returns this text with full details about how to use the browser: https://codex-tool-reference.simonw.chatgpt.site/skills/cont...
I'd love to know why it's defined like that, as opposed to including all of the instructions directly in the skill Markdown file.
Simply loading the browser Skill alone, doesn't always mean a browser is actually necessary (or supported). The user might've want them to control their main desktop browser; or the user might be pointing them toward a read-only HTML file that doesn't need rendering; or the sandbox might prevent network access; etc...
Codex is especially 'keen' to use Skills (especially by comparison to Claude), I often see it load Skills which it doesn't go on to use, because the main Skill content says "when not to use this". So I'm sure this is a product design decision to help with those kinds of circumstances.
Skill file could indicate general instructions for all browsers. This provides guidance for the browser that's about to actually be used.
Honestly, this is one of the things OpenAI does pretty well, I think, these tiny design decisions that you wouldn't notice until it becomes super annoying.
I realize that for some people there is too much LLM-related content and (therefore?) too much by certain authors, but that has always been the case for certain topics and certain authors in HN's history. This is a side effect of the frontpage being the same for everyone, and therefore the scarcest resource.
https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
Someone else submitted my vibe-coded slop site to the front page without any context, and it accumulated enough votes to show up at the top.
I could have linked to my blog post about it, but instead I linked to a Hacker News comment precisely because I anticipated complaints about "spamming" if I linked to my blog.
> I haven’t been involved with Django since leaving the Journal-World back in September, but now that the framework is open-sourced I look forward to contributing to its further development—both in terms of documentation and actual code.
(I think you may be confusing "spam" with "prolific". I write a lot.)
There is just no end or need to rapidly post on every opportunity that involves “AI” or whatever that is related to it.
Or an easier question: how am I gaslighting here? You should be able to spell that out.
(You do understand that the top linked site here was built by me, but has no authorship information on it at all, right? That's why I posted a comment explaining what it is.)
Gaslighting because it’s so OBVIOUS that this is what people are referring to by “spam” that you almost have to be purposely pretending to not understand. Such a prolific writer simply has to be aware of the fine line where promoting your work becomes excessive.
Not taking sides here.
The guy is good but he certainly stretches the limit. I just auto ignore his stuff but I know others enjoy!
ChatGPT Work in the ChatGPT web and mobile app experience is very different.
If you like, you can think of it as a cloud-hosted version of Codex that's skinned to look more like consumer ChatGPT.
Are they following some sort of common guideline?
Scroll down to the "Establish the visual direction" section.
(1) https://www.newyorker.com/magazine/2026/04/13/sam-altman-may... (2) https://thenextweb.com/news/openai-preparedness-team-disband... (3) https://thezvi.wordpress.com/2026/08/29/metr-and-redwood-off...