Artifacts in Claude Code have been life changing. Excited to expand to Pro and Max!

Now that Fable 5 is ready to build (again), we've reset everyone's 5-hour and weekly rate limits.

Agree

You asked, we listened. Claude Desktop on Linux is here! Download link: code.claude.com/docs/en/desk…

Claude in Microsoft Foundry is now generally available, hosted on Azure. Azure customers get Claude Opus 4.8 and Claude Haiku 4.5, with Azure authentication, billing, and commitment retirement.

In the next version of Claude Code: subagents run in the background by default, so you can keep talking to Claude while your subagents work If you want your agent to run in the foreground, just tell Claude

As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes: 1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship 2. Builder: quickly turns a prototype/idea into production-grade product/infra 3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance 4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit 5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS. A healthy team needs a mix of these, depending on the product: - A product that is new and pre-PMF needs people that are strong at 1 2 3 - A product that is growing and has found PMF needs 2 3 4 and some 5 - A product that has strong PMF needs 3 4 5 and some 2 Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?

I tag Claude many times a day to write PRs, address user feedback, investigate incidents, do data analyses, summarize information, etc. Use it as your company's search engine. "What's the status on X?" "Who owns this service?" It answers your questions instead of just returning links. It’s been a huge unlock for onboarding new teammates.

We’ve worked hard to make it secure at every level. 1/ At the model training stage, 2/ the classifiers on top of our models and things like auto mode, 3/ we protect what Claude has access to (websites it can access and it can’t see the credential secrets it uses), and 4/ respecting channel/workspace boundaries

Claude is really proactive with Claude Tag. You don’t need to prompt it to do work, it can do work proactively based on your instructions. It has excellent memory and access to your data, so it can behave differently per channel

Cool way to use Claude Code: deciphering Linear A, a 3500 year old written language from Crete aiclambake.com/clamtakes/lin… Hope this holds up in peer review! 🤞

I've been using Artifacts in Claude Code for everything: visual explanations of tricky code, system diagrams, quick previews of a few animation options, data analyses and dashboards I share with the team. They are a game changer for how I work with Claude. Can't wait to hear what you think!

New in Claude Design: it stays on brand with your design system across projects, lets you edit directly on the canvas, syncs with Claude Code, and connects to more of the tools you already use.

/goooooal ⚽

claude fable 5 has solved CAD I asked it to make a model of a V8 engine It came back to me with a fully working model in under 10 minutes