1. Managers: those who generally know what needs to be done, and want it done faster, so they provide a lot of instructions and context (where many developers fall)
2. Executives: those who vaguely know the end goal, but are clueless about the process, and are willing to burn resources and cycles on a black box to get the result
Same. I suspect they'll get better at taking in terrible prompts over time though... Maybe that's what Fable does better, reminds me of Sora 2, it would take my crappy prompt and expound upon it. I told it once to generate a video of someone working at some company that changed its name, but the old name had historic relevance, it referred to the new company name without me telling it to, by virtue of me wanting a video of TODAY with a 90s icon.
It’s far more careful than opus and puts far more effort into testing and validating by default.
Switching back to opus at work was a downgrade. Similar requests felt more clunky and needed far more hand holding.
If they know much of what the tool is used for, they can customize prompts to "do that usage right" even if the user doesn't know exactly how to ask for it.
If your tasks are well defined and don't require a very large number of steps -- e.g. you're asking for small, clearly defined changes to the code -- you're fine with grok-4-fast. (Well, you would be fine if they hadn't killed it.)
I work in both of these modes, and I find that the latter actually benefits from dumber models, because smaller models are faster. The work shifts from async to realtime/interactive. So you can stay alert, keep track of what they're doing and iterate, instead of alt-tabbing, getting a coffee, and then spending extra time resynchronizing your mental model later.
The responses I get from pro don't feel like ensembles. They are often very one directional.
> We generally treat GPT-5.5’s safety results as strong proxies for GPT-5.5 Pro, which is the same underlying model using a setting that makes use of parallel test time compute. As noted below, we separately evaluate GPT-5.5 Pro in certain cases because we judge that the setting could materially impact the relevant risks or appropriate safeguards posture.
https://deploymentsafety.openai.com/gpt-5-5/model-data-and-t...
There have been multiple podcasts with people from OpenAI which have confirmed this.
Any idea what that means exactly? I vaguely remember that ChatGPT Pro was originally called "deep thought", just like Geminis "deep thought" feature (or "deep think"?), so it seems likely they are using the same approach.
Its widely accepted[1] that it runs the same query through the model in parallel and then has a model that either selects the best answer or synthesizes an answer from the multiple ones generated.
I believe most people think it runs 6 sub-models, but I think that is based on the pricing.
It's a pity that OpenAI doesn't publish details like this.
Pro is quite limited on the web UI I reckon. This approach can be highly effective for reasonably verifiable task, for example, write comprehensive unit tests pointing out a tricky bug, get multiple agents to swarm at it.
It's unclear how they would do this when there is no signal that provides an objective ground truth.
const audits = await pipeline(found.files, file =>
agent(`Audit ${file} for missing authentication checks.`, { label: file }),
)
Apparently in the web chat (and also in Claude Code?[0] Though I haven't tried yet) they can call the Anthropic API and your subscription key gets auto-magicked into the requests somehow.
Those are two separate things of course (aside from the key-injection) but I guess there's no reason it couldn't run completely in the front-end... hmm...
To what effect I don’t know… I thought subagents were useful because they were explicitly single purpose and bound to a narrow context
If you don't mention it directly, it's 50/50 whether any given request will invoke a subagent.
The same with tools, skills, etc. No matter how smart these LLMs appear, they rarely do thinking as you expect.
So basically: learn how the harnesses operate, and know the names of the tools they have.
Hopefully, 5.6 will automatically spawn sub-agents without needing to ask.