Anthropic did not drop a SKU. It dropped a URL.
The official Claude developers account posted that claude.dev is the new home for people building with Claude: engineering deep dives, Claude Code and API guides, tips from the teams that ship the product, and easter eggs. The clip that went with it racked up on the order of 1.1 million views. Boris Cherny, who public-posts Claude Code work, reposted it.
If you already follow explainx.ai's Claude coverage, you have been linking into claude.dev for days without treating the domain as news. Lance Martin's eval-design and hillclimb piece lives there. The Sonnet 5.5 building guide lives there. The announcement is Anthropic pointing at the pile and saying this is the index.
TL;DR
| Question | Answer |
|---|---|
| What shipped? | A developer publication at claude.dev |
| What did not? | New weights, new API, new price |
| Vs docs? | Docs = contract. claude.dev = how the team actually works |
| How old is the writing? | Homepage dates run from spring through late September 2026 |
| Easter eggs? | Site terminal /plushies and /stickers — not CLI merch |
| What to do? | Bookmark it. RSS or weekly pass. Keep docs for flags |
What claude.dev actually is
The masthead is plain: technical writing for people building with Claude. Subhead: tips, tricks, and POVs from Anthropic's developers.
The homepage is a feed, not a product console. Recent titles include:
| Piece | Why a builder opens it |
|---|---|
| Automating eval design and hillclimbing (Lance Martin, Sep 28) | How not to lie to yourself about agent quality — our write-up |
| Building with Claude Sonnet 5.5 | Routing, effort, when not to spend Opus |
| Using Claude Code: Spending your effort | Budget the human, not just the tokens |
| What a task costs on Opus 5.5 | Cache and effort as the real invoice |
| How we made claude.ai 3x faster in two weeks | Internal loop: Claude in every Slack thread, 3,000+ merges |
| Lessons from building Claude Code: How we use skills (Thariq Shihipar) | Nine internal skill types, gotchas, marketplaces |
| A harness for every task | Dynamic workflows — pair with the harness guide |
| Prompt caching is everything | Why cache hit rate is a product feature |
| Seeing like an agent (video) | How Claude Code designs tools |
Videos sit next to posts: Ramp, DoorDash, "the future of work with Claude." Treat those as customer narrative, not API spec.
This is the same split other labs already run: a docs host plus a engineering magazine. Anthropic just gave the magazine a memorable domain instead of leaving it as a subdirectory nobody bookmarks.
How to use it without mixing up the stack
| Surface | Job | Open when |
|---|---|---|
| claude.dev | How Anthropic builds and how they want you to | Evals, skills craft, cost stories, sprint postmortems |
| docs.claude.com | API, Messages, tool use, safety | You need a field name |
| code.claude.com/docs | Claude Code CLI, plugins, hooks | You need a flag |
| Cookbooks | Runnable notebooks | You need a copy-paste cell |
| ClaudeDevs on X | Limits, incidents, resets | Something broke today |
| explainx.ai | Practitioner translation + corpus links | You want the claim checked against last month |
If you only add one habit: after every model launch, search claude.dev for the team's own "how we use this" post before you rewrite CLAUDE.md. The Sonnet 5.5 guide is the template. The hillclimb post is the template for "we shipped an agent, now prove it."
What to read this week (ranked)
- Eval design / hillclimb if you run Claude Code in production. Two commands on the claude-api skill, four rules, overfitting warning. We already unpacked it.
- Internal skills taxonomy if you maintain a skills library. Shihipar's nine buckets (library reference, verification, data, process automation, scaffolding, review, CI, runbooks, infra) are a better audit than "we have 40 SKILL.md files." Verification skills are the ones he says moved quality the most.
- claude.ai 3x faster if you care about harness loops. Two-week sprint, Claude Tag (beta) on an internal model they liken to Opus 5.5, human approval on every change, "no customer-facing incident." Steal the ratchet, not the Slack folklore.
- Prompt caching if your bill is input tokens. Pair with Opus 5.5 task cost.
- Harness for every task if you still paste one mega-prompt. That is loop engineering, Anthropic-flavored.
Do not start with the DoorDash video unless you are pitching a rollout. It will not tell you the effort parameter.
Easter eggs, crabs, and /stickers
The launch post promised fun. Replies immediately ran /stickers and /plushies, argued crab vs octopus, and claimed Apple tagged the site as adult. Here is the grounded version:
- Site terminal ≠ Claude Code. The
/plushiesand/stickerstricks described around the launch live in claude.dev's own TERMINAL UI. They are toys. Search (S) and "press R to load more" are the same class of detail. - Claude Code
/stickershas a separate history: it has opened a merch flow, and Anthropic has said they charge to cover production and shipping. Do not expect the hub easter egg to mail you vinyl. - Safe Browsing / "adult site" is a reply, not an Anthropic advisory. If Safari nags, try another browser and check the URL is
https://claude.dev. Do not treat a filter false positive as a product category.
The mascot debate is content. The docs map is the post.
What this does not change
- No new model ID. Do not add
claude-devto your router. - No new MCP or plugin protocol. MCP and Claude Code commands stay where they were.
- No replacement for changelog discipline. Limit resets still land on ClaudeDevs first.
- No geographic product. The site is public English writing. API residency is still a docs/API question.
If your team already subscribed to Anthropic's engineering RSS under another path, you may already have these posts. The win is one canonical origin you can paste in Slack: "read it on claude.dev, then our recap."
What to do this week
- Bookmark https://claude.dev.
- Skim the last four posts. If you missed hillclimb or Sonnet 5.5, start there — we already translated them.
- Put claude.dev in the same browser folder as docs, not in the same folder as claude.ai chat.
- If you author skills, print Shihipar's nine types next to your marketplace and mark gaps (especially verification).
- Ignore the plushie until the eval loop is boring.
What people are asking
Is this a new Claude product I have to migrate to? No. There is no claude-dev model string, no new MCP transport, and no new Claude Code binary. The URL is a table of contents for writing Anthropic already published under more forgettable paths.
Why announce it with a 30-second video if the posts are old? Because teams were still citing X threads and screenshots as the source of truth. A domain you can paste in Slack (read it on claude.dev) is the actual ship. The 1.1 million views are for the pointer, not a weights drop.
Do I need an Anthropic login? The public feed is readable without a console session. Treat anything that looks like a TERMINAL on the site as a toy, not as your org's Claude Code.
How should a team RSS this? Bookmark the homepage, then subscribe however your reader handles the feed if one is exposed. Until then, a Monday pass over the last four titles is enough. Pair each post with the explainx.ai recap so you do not re-litigate evals or Sonnet routing from memory.
What if my company already blocked new domains? File claude.dev next to docs.claude.com. Blocking the magazine while allowing the docs host is how people keep shipping on last quarter's prompting folklore.
Copy-paste for an internal #ai-tooling channel:
claude.dev is Anthropic's engineering magazine, not a new model.
Docs stay at docs.claude.com / code.claude.com.
This week: hillclimb evals, Sonnet 5.5 building guide, internal skills taxonomy.
Site /stickers and /plushies are easter eggs — not Claude Code merch.
If you already distilled those posts into CLAUDE.md, you do not need to rewrite the memory file. You need a source of record when a teammate pastes a screenshot of a six-month-old tweet. Point them at the live article, then at the explainx.ai recap if they want the practitioner translation.
The same split applies to videos. A DoorDash or Ramp clip on the hub is customer narrative. It will not tell you the effort parameter, the /claude-api hillclimb train/test split, or whether /model sonnet now maps to Sonnet 5.5. Watch the clip after you have the routing table, not instead of it.
Related reading
- Claude Code build-eval and hillclimb
- Claude Sonnet 5.5 building guide
- What are agent skills?
- What is an agent harness?
- Claude Code commands reference
- Loop engineering for coding agents
- Opus 5.5 vs Sonnet 5.5
- Official hub: claude.dev
- Official docs: docs.claude.com
Hub contents and post dates follow claude.dev as of October 1, 2026. The developer-account announcement is the naming event; older articles were already live. Easter-egg behavior can change without a model release. Verify CLI commands in current Claude Code, not in a website terminal.