You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
File ReadingArea: what it touches
ImprovementsKind: in v2.1.310,
ImprovementsSection of the release
Unclear Which reads and uploads now behave differently for a user, and how, is not stated.
What
Claude Code can upload project files for a request run elsewhere. The code that decides which files go and how they are read changed:
uploadRulesForRequest now takes fewer arguments and returns the rules directly instead of an object with arguments and rules. It is used by the ReadProjectUploadText path, and putFiles is now given the rules as launchRules.
A file read call now passes followsLinks: true, so it follows symbolic links (shortcuts that point to another file).
An upload tool's settings gain namesResolvedPaths: true.
One tool gains a suggestedAllowRule check that matches when the tool's rule content equals a stored value. An allow rule is a saved permission that lets a tool run without asking.
Why
This may change how symlinked files are read and uploaded, and which allow rule is suggested in a permission prompt for file uploads.
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 doubtWhich reads and uploads now behave differently for a user, and how, is not stated.
