Bias towards action. Act quickly to learn faster without being careless. When I'm building products, I try to default to the smallest responsible step that gives me feedback with some guardrails so that mistakes are cheap to fix and have limited blast radius. That's helped me ship to millions of users. I've seen a lot of people stall out on their ideas and its happened to me too. On side-projects, I would keep refining them long after they were good enough to try out - it just "needs one more feature", "to load one second faster" etc. But it's easier to reason about something once it’s real and people start using it. The folks I've seen have the most impact often weren't the smartest in the room. They shipped something small, noticed what broke and shipped a better version as soon as possible. Being wrong early was part of how they learned. Meanwhile there were so many people waiting for certainty that just continued waiting and didn’t ship.

Cloud sessions for Claude Code are now GA! Start a task, close your laptop and it keeps going. Get a one-time $100 credit on Pro or $250 on Max to celebrate. Your sessions spend it before falling back to normal plan use. Claim it: Many of you have already been using cloud sessions and we hope you'll enjoy the extra credit.

Try these in your first Opus 5.5 session: → Hand over a whole task. Define "done" and when to check in. → Drop "think carefully". It always thinks first. → After a long run, check what it needs to go further. Our playbook:

Introducing Claude Opus 5.5! 40% lower cost than Opus 5 with cache reads 60% cheaper. It performs at the level of Claude Fable 5.1 for most tasks. I celebrated with a pelican riding a bike in Three.js.

Reminder: Claude Code can test if a skill or plugin actually improves Claude's answers. > claude plugin eval init Tell Claude what a good result looks like in your plugin's folder and it writes the test cases for you. > run claude plugin eval .

"you are in the reputation-building business, and software is actually downstream of that." Great read if you've started something new and feel pressure to prove yourself. The advice: don't spiral. Be a reliable teammate first & the bigger work will follow.

Projects are rolling out in Claude Code today. A Project is an ongoing conversation that coordinates a stream of related work for you. You describe a goal, Claude splits it into threads, runs them in parallel in the cloud and keeps going after you close your laptop. Starting with select Pro and Max users on cloud sessions.

Claude Design, Claude Slides and Claude Docs also work inside Claude Code now. Ask for a design review deck or a UI mockup and point it at the actual files and RFCs in the repo. Edit it yourself or keep going in the conversation, and share the link when it's ready.

At Anthropic, Claude now writes 80% of our code. Engineers ship 8x more code per quarter. Side effect: Tests grew 10x. CI jobs up 25x in 6 months. Here's what helped us scale:

How I do code reviews these days: more code = more selective human review i.e. don't read all the code. 1. Every PR gets a multi-agent first pass. It should find bugs, verify them, rank by severity, suggest fixes. Approval stays a human call on anything that matters. 2. Low blast radius changes on less sensitive code (there's often a lot!) can skip a deep human review once that review is clean. This helps keep the explosion of PRs manageable. 3. Core / sensitive paths still need an owner and human sign-off. That's where you spend time: verification, constraints and earning trust in what the agents can safely cover. You want to keep recoverability. Agents do the first pass and humans cover blast radius. Great question from @GergelyOrosz!