Claude Code has released a new version, and the notes are heavy on fixes rather than features. The headline is simple: the app now reads AGENTS.md if there is no CLAUDE.md file in a project. That is a small convenience for teams that want to standardize their agent configuration across multiple tools.
The rest of the release notes read like a laundry list of things that were broken. Sessions hung, crashes hit specific values in configuration files, and several commands failed to complete basic tasks.
What Broke First
The update notes open with a new feature and quickly move into the problems. Here is a quick rundown of the major fixes:
- Sessions hung and returned no result after an internal error; they now report the error and exit with code 1
- Conversations failed with “text content blocks must be non-empty” when an earlier assistant turn included an empty text block
- Users were logged out unexpectedly when an older Claude Code build ran alongside the current one on the same machine
- A malformed customApiKeyResponses value in ~/.claude.json caused interactive startup to hang or show an error for ANTHROPIC_API_KEY users
- Update checks errored every 30 minutes, and claude update hung when a proxy returned an invalid version; a malformed minimumVersion is now ignored
- claude update on winget- or apk-managed installs reported “up to date” when the version lookup failed
- claude plugin install broke the installed copy when reinstalling a plugin version in use by another program; an unchanged copy is now left alone
The pattern is consistent: a command fails, an error message appears, and the next version ignores the bad input rather than crashing. That is a sensible approach, though it leaves some questions about how users were supposed to know what was wrong before.
The Fixes Worth Noticing
Not every fix made the notes easy to read. Some of the smaller changes are genuinely useful once you understand what they address.
- The CLAUDE_GATEWAY_PROXY_IS_EGRESS_BOUNDARY=1 flag tells Claude apps gateways to hand outbound requests to a forward proxy instead of resolving hostnames themselves
- An optional headers: map lets users send static headers to a proxy running in front of a provider
- Background tasks now say a panel such as /tasks is waiting for an update when it finishes
- Grep and Glob stopped reporting no matches when the system ran out of processes, memory or file handles; they now return an error instead
- The Write tool no longer ends a turn as a declined permission when the target is an existing directory; it reports a clear error instead
- Escaped backslashes followed by uXXXX text were treated as \uXXXX escapes in the Edit tool; that behavior is fixed
- A crash (“Type error”) opening /mcp or /plugin manage with a malformed claudeAiMcpEverConnected value in ~/.claude.json is gone
These are small wins, but they are the kind of polish that makes an app feel ready for daily use.
The Case for Relief
There is a strong argument that this release notes are a sign of maturity. A product that documents every failure, assigns it a code, and ships a fix is one that knows what it is doing. The notes read like a company tracking its own progress.
The release also includes fixes for remote control, sandboxing, and marketplace policies. Those are enterprise-level concerns, and addressing them in a single patch shows attention to a broader user base than just the core developer audience.
Claude Code now reads AGENTS.md if there is no CLAUDE.md.
That line is the headline, and it is the only feature that actually adds new behavior rather than repairing old damage. It is a small but sensible addition for teams that want a single configuration format across multiple tools.
The remaining fixes are mostly about stability and error handling. They do not add new commands or features, but they remove friction from everyday use.
What Remains Uncertain
The release notes do not say which platforms these fixes apply to. The note about AGENTS.md support specifically excludes Bedrock, Vertex and Foundry, which suggests those platforms are not covered by this release. That is a reasonable gap, but it leaves users on those platforms wondering whether their problems are being tracked at all.
The update checks and plugin install issues also raise a question about how Claude Code manages dependencies across package managers. The notes describe specific behaviors on winget and apk, which implies that other systems may need separate treatment. Whether that is a one-off or a recurring problem is not stated.
The Bottom Line
This release is a relief. The fix notes document a team that has spent time chasing down issues, and the fact that so many issues were documented afterward suggests a product that is getting better at understanding its own limits.
The AGENTS.md support is a nice touch, but it is the quiet part of the release. The real story is the sheer number of things that were broken and are now fixed. For anyone who has hit a crash or a hung command in the past few weeks, this update is worth pulling.
The release notes are worth reading in full, even if you are not a developer. They paint a picture of a product that is still improving.
Source material: “Claude Code now reads AGENTS.md if there is no Claude.md,” claude.com.
Get the Notebook.
The day's best stories and every fresh verdict, in plain English, in your inbox by seven. One email a day, no more.