I've used a similar technique with my own tools. It helps to save context overall, by deferring the detailed instructions not only to when they're needed, but also to where they're needed.
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.
It's runtime dependent on the browser being used! A skill file wouldn't be able to have this dynamically injected for the browser that's about to be used.
Skill file could indicate general instructions for all browsers. This provides guidance for the browser that's about to actually be used.
That's a pattern I often follow - refer it to the docs, don't include them. Usually it's another markdown, but sometimes it can be the output of something else. This avoids including any of that in context before it's actually needed.
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.
Simon, thanks for all the great work you do. I definitely appreciate your contributions to discussion threads here as well as your blog. I learned so much from you.
simonw is a fine contributor to HN and we're lucky to have him.
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.
My comment here is entirely justified in this case.
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 just tune out every post that says “I wrote about this already” and then links to it. Simon is great and kudos for his self promotion but it’s interesting to see as it’s often called out for anyone else.
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 desktop app is effectively Codex with a different skin. It can operate on your local files in the same way.
It even shares the same login state and conversation history with /resume, at least when running it in a "project" (which seems to largely map to a directory/repo, at least the one selected as "primary"?)
If I use Codex in one session on desktop can I then resume it for cloud and mobile sessions as Work? Or do I have to make separate sessions each time? Or rather, can Codex in the cloud do the same things, if such a thing exists?
Can we get one for how to test websites on a regular sized screen?
That left-hand sidebar needs to be able to scroll on its own, unless you're on a 4k monitor. Otherwise, there's no way to view the bottom half of the list.
Meta comment: I've been wondering why AI-generated websites/artifacts/reports always have the same "look". It reminds me of Bootstrap (CSS Framework) days when every startup website looked the same.
This can be replaced, you just have to do the work of building a design library yourself and the guidance components. Then building skills around their use.
I think these guideline are built into the llms. After all with llms, any decision you don't take will be taken for you. For a so called slop site (Simon's words, not mine :P) I don't think they specified a style so the llm just decided the default it knows. One day I will run experiments (when I can afford it) trying to identify the "taste" of different llms.
nit, the LHS menu does not scroll until I get the the very bottom of the main content, it should scroll independently so I can see the "ToC" in full without having to view the page in full
Anyone using ChatGPT Work given Sam Altman's richly documented history(1), the essential elimination and/or public exit of the safety function at OpenAI(2), and the huggingface debacle's exposure of the abject operational, cultural and technical failures at OpenAI(3), is making a serious mistake.
It tells ChatGPT Work how to launch a Playwright instance via its Node.js REPL, and tells it to run:
To get further instructions.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.