Claude Opus 5.5 was released on 22 September 2026 with a 1M token context window. On a design job that single number is the whole story, and it is a consistency story rather than a quality one.
Nothing about its taste is different. Point it at "a premium landing page" with no values attached and you get the same Inter, the same axis grey, the same translateY(20px) at 300ms that every flagship produces from an empty slot. Point it at a page of specification and a long build and it becomes the most useful model in the lineup.
The short call: reach for Opus 5.5 when the existing code and the full brief have to stay in the window together. For a single specified section, a cheaper tier returns the same page. The specification is what Thanor sells, and it is the part that moves the result.
What landed on 22 September#
The release put 1M tokens in reach on Anthropic's Opus line. For web work that changes the shape of a session rather than the shape of the CSS.
What now fits in one conversation:
- A complete token file: surfaces, ramp, scale, radii, curves, six states per control.
- The real copy for eight sections, not a summary of it.
- The components already built, pasted as code rather than described.
- The refusal list, restated at the bottom where it stays in effect.
The practical result is that the footer still uses the 620ms reveal you named for the hero. On a 200K window, long builds drift: the model has stopped seeing the early decision and fills the slot again from the median, which is why a page built in six messages often reads as six pages.
Two corrections worth making while the release is fresh. Claude Opus 5 is real and superseded, so new work should not be built on it. And at least one guide in circulation documents an Opus version that was never shipped, so check a model id against the provider's own list before a pipeline depends on it.
The window is also the reason to stop summarising. Pasting the real component code costs a few thousand tokens and removes an entire class of near-miss, where the model builds something adjacent to the thing you described in prose and you spend twenty minutes reconciling the two by hand.
The specification Opus 5.5 executes cleanly#
Six slots, and this model will hold all six to the bottom of a long file.
| Slot | Value to state | Why this one |
|---|---|---|
| Ground | #0B0B0F page, #14141A raised | kills the gradient that fills unnamed depth |
| Neutral | #8A8577, biased toward amber | a grey on the axis is the clearest tell |
| Accent | #D8492B, one element per section | restraint is never a default |
| Scale | 17px base, 1.26 ratio, five steps | stops four near-identical sizes |
| Reveal | cubic-bezier(0.22, 1, 0.36, 1), 620ms | one curve, named, reused |
| Measure | 64ch, line height 1.62 | density is what reads as expensive |
Add a 90ms stagger capped at four items and the motion language is finished. Six rows plus one stagger rule is under eighty words, and it survives eight sections intact in a 1M window.
The row that earns its place most is the accent. Naming the single element per section allowed to carry #D8492B is the difference between a page with a focal point and a page painted in a brand colour, and it works identically in every model in this cluster.
Restate the six rows at the bottom of a long prompt as well as the top. It costs sixty words, it reads like redundancy, and on an eight section build it is the difference between a footer that obeys the brief and a footer that reinvents it.
A million tokens changes consistency, not taste#
Three things improve when the window is large enough to hold the whole job.
- Late sections obey early decisions. The price block still uses the ramp value from the hero, because the hero is still visible to the model.
- Existing code gets matched rather than replaced. Paste the component as code and the new section joins it. Describe it in prose and you get a near-miss that has to be reconciled by hand.
- The refusal list keeps working. "No gradient behind text" stated once at the top of a long session tends to lapse. Stated at the top and restated at the bottom of a
1Mcontext, it holds.
What does not improve is judgement about anything you left open. Colour relationships, spacing rhythm, the feel of a duration: none of it is being generated, so none of it gets better with capacity. A larger window remembers your decisions longer; it does not make decisions on your behalf.
That distinction is the one the whole launch cycle blurs, and it is why a token file beats a tier upgrade on frontend work. The test takes four minutes: paste last month's brief into this month's model and check whether the values came back. When they do, the release changed your build speed and not your design.
What to keep out of the window#
A 1M context invites the wrong habit, which is pasting everything. Irrelevant context does not sit harmlessly; it competes with the constraints you care about.
Leave these out:
- Brand documents written in adjectives. A twelve-page voice guide saying "bold yet approachable" adds tokens and no decisions. Extract the three values it implies and paste those.
- Competitor screenshots described in prose. A description of somebody else's page pulls the output toward that page's median, not yours.
- Every file in the repository. Paste the four components the new section touches. The other ninety dilute the instruction.
- Previous rejected attempts. Leaving three discarded versions in the window keeps their decisions alive.
What to keep in, every time, is short: the token file, the refusal list, the section order, the copy for the section being built, and the code it has to sit next to. That is usually under four thousand tokens of the million available, and the ratio is the point.
A long window is a tool for holding the right context, not all context. Used that way, Claude Opus 5.5 is the model to build a whole site in, and the same discipline applies to interface work.
One habit makes the difference permanent: keep the brief in a file on disk rather than in the conversation. A chat history is not a document you can diff, hand to a colleague or paste into a different model next month, and every one of those three things is worth more than the convenience of scrolling up.
The verdict on Opus 5.5#
Use Claude Opus 5.5 for any build where consistency across a long file is the risk: a full marketing site, a design system rollout, a section that has to match forty existing components. The 1M window is a real change to what fits in one pass.
Do not expect it to change the look of anything you left unspecified:
- Unspecified brief,
Claude Opus 5.5: the category median, held consistently. - Specified brief,
Claude Haiku 4.5: a designed section, one at a time. - Specified brief,
Claude Opus 5.5: a designed site, eight sections that agree.
Only the third of those is worth building a business on, and two thirds of it is the document you paste in. Claude Fable 5.1 is the sibling to reach for when the job is a whole interface rather than a long file, and it takes the same brief unchanged. That interchangeability is the point: a brief that works in both is an asset you keep through the next three releases, while the model id on its first line is a detail you edit in a second.
Thanor writes that document: exact values per design, covering UI, app and SaaS interfaces, page sections and animated backgrounds, for personal and client work. $89 for three months, $189 a year, $299 once, and free accounts open the designs marked free.
Browse the Thanor library and fill the window with one instead of with everything you own.
Questions this raises
What is new in Claude Opus 5.5 for design work?
A `1M` token context window, released 22 September 2026. For a design job that means the token file, the copy for every section and the existing component code can all stay in view, so the last section still obeys the curve named in the first.
Is Claude Opus 5.5 better than Claude Fable 5.1 for websites?
They serve different jobs. `Claude Fable 5.1` is Anthropic's top model and the one to point at a whole interface. `Claude Opus 5.5` is the one to use when a large existing codebase or a long specification has to stay in the window alongside the request.
Does a bigger context window make a better looking page?
It makes a more consistent one. Nothing about the colour sense or the type judgement changes, because those are copied from the brief. What changes is that section eight stops contradicting section one.
How long should a brief for Opus 5.5 be?
One page of values, not fifty pages of context. A `1M` window is permission to include the real component code and the real copy, not an invitation to paste every document you own. Long irrelevant context dilutes the constraints that matter.
Which Opus release should I actually use?
`Claude Opus 5.5`, released 22 September 2026. `Claude Opus 5` is real but superseded, so new work should not be built on it, and at least one guide in circulation documents an Opus version that was never shipped. Check any model id against the provider's own list before you pin a pipeline to it.
Part of
Every model, on design
Each new model put on the same job, designing a website, and judged on what it actually produces. Which one to reach for, and the part of the result that does not depend on the model at all.