You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
ArtifactsArea: what it touches
ImprovementsKind: in v2.1.310,
ImprovementsSection of the release
What
read_file now refuses a path that passes through a symlink (a shortcut file that points to another location) when the symlink's target uses ".." (go up one folder) anywhere after its leading "../" parts. A target that only climbs at the start is still accepted; one that climbs again further along is rejected.
Separately, a new kind of attachment, project_doc_reads, now sits in the same group as inlined_image_paths, mcp_resource and structured_output. An attachment is an extra piece of context Claude Code adds to the conversation.
Why
The refusal closes off a way for a file path to reach outside where it is meant to through a crafted symlink. The new attachment type points toward reads of project documents being handled as their own kind of context.
