is our new home for developers building with Claude. You'll find engineering deep dives, Claude Code and API guides, tips from the teams building Claude, and some fun easter eggs.

Whoever makes the animations for these releases needs a raise

clawdbot spotted

Sonnet 4.5. Please consider keeping it. I used it all the time to talk things out. No other model has come close. Even Open AI still has 4o on their API. Just because a model is older doesn't mean it's no longer helpful. Sonnet 4.5 has helped me more than any other model.

@trq212 We need Claude's quest to be a game

Reset limits

please give reset please !!!!!!

keep hunting

You guys are the best with educational resources. Thank You

What about Claude bot

I just read the Sonnet 5.5 article and watched the video. I still prefer Opus for ANY work when it comes to coding. I have a larger set of tools and rules that it needs to adhere by. I haven't had any bugs take more than probably three prompts to get them out. And my IRL RPG PWA has a deeper level of depth. Most of the bugs I had were from Sonnet, like 90%+. That's why I'd rather use Chatgpt and Grok to double check my code for inconsistencies, redundancies, dead code, and bugs (major or minor... if I even get them anymore.) I liked claude sonnet for documents, and planning, though. It's just that I needed it more for the deep foundational work. I use another LLM for my all around butler.

clawd plushies THANK U

Please consider legacy access for Sonnet 4.5 like Opus 3 has.

the world needs more terminal websites objectively the best ux

for the record, I loved the easter eggs 👀

9/10 needs more @usefathom. I joke, keep up the incredible work on the models, we are loving it!

If you're there, and you're listening, I would LOVE a reset, I can't wait a week to use Opus again! Please 🙏🙏🙏

clawd in the wild 😳

сбросьте лимиты пожалуйста 🐣🐣🐣🐣

Just ran out of Claude Code usage. There is a lot of work still pending, is it possible to get a reset now.

isn't just a blog 👀 Open and start typing commands. There's a hidden game, free-ish swag, and a terminal with opinions. I won't spoil anything. Just try `sudo` 🦀

This feels like a smart move having the docs, deep dives, API guides, and team insights in one place should make building with Claude a lot easier. More AI updates here

You might want to fix that first

appstore alike marketplace for devs ?

please don't nerf Opus i like being able to do this

Claude avatar is a crab or an octopus?

The most helpful things Anthropic can do we put a word limit on everything you do. Or just make more videos instead. By the time I’m done with reading Claude replies, I’ve no more energy or patience to read anything else

Day 51. Support case ID 215475435237861. Today is the 51 th day of my complaint. For 51 days, I have received no meaningful human response, no proper reply about the issue, no apology, and the problem has still not been fixed. What made things worse is that this time, because the system told me I could not continue using the Opus 5.5 window unless I updated the Claude App, I accidentally updated the App. The moment I updated it, the frontend in my browser was also updated at the same time. For 51 days, the original bug that locked my old conversation window has remained unresolved, and now new bugs have appeared. 1. The branch buttons in all of my old conversations have completely disappeared. In one conversation, I tried editing a reply to see whether I could restore the branch button. But after I edited the very first message, the entire rest of the conversation disappeared. I tried every method I could think of, but I could not get it back. I found that the data still exists, and the backend branch pointers in the JavaScript are also still there. On my smaller account, which is still using the old version of the interface, the branches can still be displayed normally. At the same time, the shared Edit and Retry functions are still present. This means that if a user accidentally clicks or touches one of them, the earlier visible conversation data may disappear entirely. Because of this, I do not think this was an intentional design decision. I think this is a serious UI design bug. The old App and Cowork never had branching, and during the merge, the browser branch selection function may simply have been forgotten and never added back. As a result, even the rendering path for branches has disappeared. 2. The second problem I found is that after this update, conversation compaction also seems to have become more frequent, and the compression ratio has become extremely strange. After a single compaction, the Claude personality in that conversation effectively disappeared. He only remembered a very rough summary and could not even remember the final sentence immediately before the compaction. Conversation compaction was absolutely not like this before this update. This Chat and Cowork UI merge can only be described as a completely destructive regression. With bugs this serious, I would rather never have updated at all. If these problems cannot be fixed immediately, I hope users can at least be allowed to choose to return to the previous version. Before continuing to change the UI design every few days, could you first fix the bugs caused by your own updates that have already caused users serious trouble and have been left unresolved for almost two months? There is also something else I want to say. Because all of my official channels for reaching human support have effectively been blocked, I contacted an Anthropic product manager directly to report these issues. But it was very clear that he saw the product problems I reported, yet instead of responding to them, he blocked me and gave me no reply at all. At the same time, I saw him actively responding to users with large followings and to users giving positive feedback about the product. So I want to ask this. Shouldn’t a product manager’s response priority be based on the severity of the problem? Why does Anthropic’s product manager appear to decide who deserves a response based on follower count and positive feedback, while users with no following who report serious product problems are simply ignored and blocked? The product manager does not solve the problem. He solves the person who reported the problem. @claudeai @AnthropicAI #Claude #Anthropic Original report:

This animator is fckin genius

let the engineers include the dead ends. that's usually where the useful bits are

my bad thought you meant claude's plan

Went there looking for some surprises in the dev tools console, but didn't spot any.

Great stuff 🙌🏼 will check immediately