We’ve heard your feedback and we’re working on making it easier to follow everything that’s happening with Claude Code. First, we’re introducing @ClaudeDevs, the official channel to follow for all updates on Claude Code and the Claude platform.

a quick fix if you saw higher rate limit usage in Opus 4.7 today- hope you enjoy trying it out

Opus 4.7 is a model I’ve loved working with in Claude Code. It’s more agentic and instruction following but also incredibly smart and creative. I think it takes a slight adjustment to get used to, but it's so good with auto mode.

I edited the intro because I realized I buried the lede originally- The 1M context window is a double-edged sword. It allows Claude to do more complex tasks but it can also leads to more context pollution if you don't manage your session well. This is how you do that:

Have you tried the new Claude Code renderer? What has your experience been like? If you haven't, you can enable it with: CLAUDE_CODE_NO_FLICKER=1 claude

there's a turbotax connector in Claude Code now, so glad I procrastinated on taxes 😭

New in Claude Code: /ultraplan Claude builds an implementation plan for you on the web. You can read it and edit it, then run the plan on the web or back in your terminal. Available now in preview for all users with CC on the web enabled.

you'll need to explicitly prompt Claude Code to use it, but the Monitor Tool is super powerful e.g. "start my dev server and use the MonitorTool to observe for errors"

I think "prompting" will keep being an incredibly high-leverage skill, like writing or public speaking. It is the skill of talking to agents, mediated by the harness. My main goal is to grow the bandwidth between humans and agents, to help us understand each other better.

I want to do some streams where I work with non-technical people using Claude Code to figure out how they might be able to improve their process. My feeling is that just a few tips could make a big difference in efficiency. Any mutuals interested?

Managed Agents is the first 'agent in the cloud' API that has the right mix of simplicity and complexity. Implementation details like how you manage a sandbox are abstracted, but you have a lot of control over the actual execution of the model.

done about 10 of these calls so far + looked at more transcripts many learnings but one of the biggest is that it's very easy to spend a lot of tokens on open ended verification that doesn't make your output better I'll try and write more on how to do it efficiently

Doing a workshop on my technical writing process in SF in 2 weeks, hosted by friends @MilksandMatcha and @swyx. Would love to see you there! Link below.

I put a lot of heart into my technical writing, I hope it's useful to you all. 📌 Here's a pinned thread of everything I've written. (much of this will be posted on the Claude blog soon as well)

Excited to talk to you tomorrow @ 12pm PT. Adam will be showing off a demo of a new feature we haven't released yet!

I want to do a few more of these calls. If your MAX 20x plan ran out of tokens unexpectedly early and you're willing to screenshare and run some prompts through Claude Code please comment. Trying to figure out how we can improve /usage to give more info.

POV: you're cooking

claim a month of free credits on us, thanks for bearing with us

not an April Fools joke, we rewrote the Claude Code renderer to use a virtual viewport you can use your mouse, the prompt input stays at the bottom, and a lot more small UX wins people have been asking for it's experimental so give us your feedback