ClaudeCodeChanges

New version Docs only
S M T W T F S
1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
31

Claude docs changes for May 2nd, 2026 [diff]

Executive Summary

  • Claude Managed Agents sessions are now visible in the Console with a timeline view, tool execution details, and debugging tips
  • Claude Managed Agents does not support the inference_geo parameter and is not covered by Zero Data Retention (ZDR)
  • The agents field in the plugin manifest now accepts an array instead of a directory string, enabling more granular agent file targeting

Claude Code changes

Changed documents

Desktop [Source]

  • Clarified that on Linux, users should use the CLI instead of the desktop app, with a direct link to the CLI quickstart. [line 19] [Source]

Desktop Quickstart [Source]

  • Clarified that on Linux, users should use the CLI instead of the desktop app, with a direct link to the CLI quickstart. [line 19] [Source]

Environment Variables [Source]

  • Expanded CLAUDE_CODE_SHELL_PREFIX description to clarify it wraps Bash tool calls, hook commands, and stdio MCP server startup commands (not just bash commands). [line 137] [Source]

Plugins Reference [Source]

  • The agents field in the plugin manifest now takes an array of file paths (e.g. ["./custom/agents/reviewer.md"]) instead of a directory string. [line 352] [Source]

API changes

Changed documents

API and Data Retention [Source]

  • Added clarification that Claude Managed Agents is not covered by Zero Data Retention (ZDR): sessions are stateful resources, transcripts can be deleted manually but there is no automatic deletion. [line 32] [Source]

Data Residency [Source]

  • Added note that Claude Managed Agents does not support the inference_geo parameter, but respects the workspace geo configured in the Console. [line 12] [Source]

Events and Streaming [Source]

  • Added a new "Console observability" section describing the visual timeline view for agent sessions in the Console, including session list, tracing view (for Developers/Admins), and tool execution details. [lines 221-230] [Source]
  • Added a "Debugging tips" section with guidance on checking session events, reviewing tool results, tracking token usage, and using system prompts for reasoning visibility. [lines 232-238] [Source]