Hacker News

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.

Two sources of truth, if playwright updates?

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.

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.

I'm guessing, but can be because then the skill will always fetch the latest docs.

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.

[flagged]

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.

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.

In this case they really are, and you can read the guidelines that helped create the site on the site itself in the skills: https://codex-tool-reference.simonw.chatgpt.site/skills/site...

Scroll down to the "Establish the visual direction" section.

Because most AI generated websites are from people who don't know much and as such cannot even articulate the look they want

I keep seeing comments like this, and having messed around and generated a few (non-public) websites myself they all looked completely different?

Mind you I don’t spend a lot of time on ai generated websites or the kinds of places you might find those. Well except for HN but you get my point.

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.

Which provider currently lives up to your moral code?