这是什么

This week, Anthropic shipped version bumps across six client SDKs (Python 1.2.0, TypeScript 0.122.0, Go 1.68.0, Java 2.59.0, Ruby 1.67.0, C# 12.44.0), moving Files and Skills entry points from the beta path to the stable path. On the surface, it's a routine upgrade. But the migration guide hides a critical caveat we think every integrator needs to register: Workspace (the shared storage layer) is not tenant isolation, and an API Key is not a user identity.

Translated into everyday language: imagine an office building where all tenants share one property management account — each company swipes its own badge to enter, but a badge only proves you got into the building, not which office you're allowed to walk into. The Files API stores documents in this shared Workspace layer, and the mapping of "which user can read which file" must be maintained by the calling application. No file_id (file identifier) coming from the front end can be trusted on its own.

行业怎么看

Supporters argue that explicitly writing "beta Header (legacy interface flag) defaults to off" into the release notes at least returns informed consent to developers and forces enterprises to think through their authorization model — a good thing in the long run, in their reading.

But the criticism is sharper. Identity security teams we track point out that Anthropic shipped a stable interface without any built-in tool for user-level resource isolation — every "SaaS (Software as a Service, i.e., subscription-based online software) + Claude" integration already in production now ships with an audit blind spot by default: a request passing authentication ≠ the user is authorized to read that file. Engineering leads we spoke with are blunter: the official docs blur the line between Workspace sharing and user isolation in the same paragraph, which is a migration trap. Any framing that treats Workspace as a natural security boundary will fail in a compliance audit. On top of that, the old Header can still be forced to return beta shapes — if your middleware (the software layer that centrally handles network requests) appends that Header, your code can silently drift back to legacy fields, raising the probability of production incidents.

对普通人的影响

  • For enterprise IT: before you feed company contracts or customer lists into Claude, audit "who uploaded with which key, where is the file stored, and who has read rights." That job is no longer automatic.
  • For working professionals: you don't need to memorize the terminology, but remember this — when an AI tool that touches sensitive documents is proposed, asking "where are the files stored, and who can see them" is now baseline literacy.
  • For the consumer market: consumer-side (C-end) AI assistants are unaffected in the short term; consumer products ride on the platform's built-in account system and don't expose the Workspace layer. But on enterprise AI procurement checklists, "permissions model" shifts from a nice-to-have to a required question.