Claude docs changes for November 15th, 2026 [diff]

Executive Summary

  • New "Work with Jupyter notebooks" docs: NotebookEdit clears a replaced cell's saved output and execution count, so re-run the cell, and save the notebook before asking for an edit.
  • Data residency docs now include Console steps for setting allowed and default inference geos, plus Admin API details.
  • The workspaces docs now spell out Default Workspace behavior and Workspace Limited Developer Console limits.
  • Claude Platform on AWS docs now list the new Agents overview page and say Admins can set workspace spend limits.
  • The self-hosted Managed Agents docs add a note for organizations that already have access.

New Claude Code versions

No new versions in this update.


Claude Code changes

Changed documents

ide-integrations [Source]

  • New "Work with Jupyter notebooks" section. Replacing a code cell clears its saved output and execution count. No kernel restart is needed, because NotebookEdit only writes the file. Re-run the edited cell and any cells that depend on it. [lines 605-618] [Source]
  • Save a notebook before asking for an edit, because the autosave setting doesn't save before NotebookEdit. The autosave description now says it saves before the Read, Edit, and Write tools run. [line 750] [Source]

monitoring-usage [Source]

  • When a mod from outside the official marketplace and built-in bundle calls $.model, api_request events carry marketplace.name. It is redacted to "third-party" unless OTEL_LOG_TOOL_DETAILS=1 is set. The api_error event points to this note. [line 871] [line 895] [Source]

tools-reference [Source]

  • New section: replacing a cell with NotebookEdit clears its execution count and saved outputs. Re-run the cell and its dependents to get the output back. [lines 449-452] [Source]

vs-code [Source]

  • New "Work with Jupyter notebooks" section covering cleared outputs after cell edits, no kernel restart needed, and saving the notebook before an edit. [lines 605-618] [Source]
  • The autosave setting now saves before the Read, Edit, and Write tools run. [line 750] [Source]

API changes

Changed documents

claude-platform-on-aws [Source]

  • Console pages table: a new Agents overview page (session counts, error rates, active time) does not go through the AWS gateway, except for its list of agents. The Agents page's Observability tab also bypasses the gateway. Pages that bypass the gateway reach Anthropic directly and skip IAM action checks. [lines 809-832] [Source]
  • Spend limits: with the Admin role you can set organization and workspace limits in US dollars at list prices. The Console steps are updated (Organization limit and Workspace limits sections). Tier-cap failures are documented as HTTP 429. A new list says who gets an email notice depending on what stopped the requests. [lines 860-880] [Source]

data-residency [Source]

  • Requests with a disallowed inference_geo return a 400 error. default_inference_geo must be one of the allowed geos. [lines 260-261] [Source]
  • New step-by-step Console instructions for setting the allowed and default inference geos, and Admin API guidance. Both fields go inside the data_residency object of a Create or Update Workspace request, and an update keeps any field you leave out. [lines 263-272] [Source]

self-hosted [Source]

  • New note: if your Claude Console organization already has access to self-hosted Managed Agents, sign in to the Console, switch to that organization, and reload the page. The same note was added to the self-hosted subpages (agent-identity, call-the-api, configuration-reference, configure, console, differences, inference-provider, kubernetes, quickstart, upgrade) and to self-hosted-data-and-access. [line 9] [Source]

workspaces [Source]

  • The Default Workspace behavior is now spelled out. Responses carry its ID in the anthropic-workspace-id header. List Workspaces includes it only with include_default=true. The Usage and Cost Analytics API reports it under that ID, while the legacy Usage and Cost API shows null. An API key bound to it carries the ID in its scope field. [lines 21-26] [Source]
  • Workspace Limited Developer limits apply only to the Console interface, not the API. In the Console they cannot open or start Managed Agents sessions, open memory stores, or manage deployments. They also cannot download or delete files on the Files page. [lines 47-58] [Source]
  • Admin API endpoints reject keys scoped to a single workspace. List examples now document auto-pagination, where limit sets the page size rather than the total. The PHP and Ruby samples now use auto-paging iterators. [lines 241-347] [Source]
  • Resource scoping: organization-level requests such as Admin API calls are exempt from the one-workspace rule. MCP tunnel details were added: the cap of 10 active tunnels is organization-wide, managing tunnels needs the Manage tunnels permission, and developers can view tunnels but not change them. [lines 816-834] [Source]

webhooks [Source]

  • Small clarifications to the Console workspace picker and to how non-2xx responses are handled. A 3xx disables the endpoint immediately, and other failures are retried. [line 336] [Source]