A new file-reading capability is offered only when policy allows it
Claude Code can now offer a read_file as_written capability, but never to HIPAA organizations or before usage policy is known, and only when switched on
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
AgentsArea: what it touches
Internal ChangesKind: in v2.1.307,
Internal ChangesSection of the release
Unclear It is not clear what the read_file as_written capability lets a connected client do.
What
Claude Code now decides whether to offer a capability called read_file as_written to the session. A capability is a feature the session announces as available to whatever is connected to it. It is listed next to another new capability that passes along the progress of commands.
The capability is not offered when:
The organization is marked as a HIPAA organization
Claude Code has not yet received the organization's policy limits from the server
Otherwise it still depends on a setting that is off unless it is switched on remotely. The first time it is refused, Claude Code writes a note saying it is not served.
Why
The capability stays unavailable by default, and HIPAA organizations do not get it even when it is switched on.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear what the read_file as_written capability lets a connected client do.