{"version":"2.1.310","anchor":"read-follows-symlinks-and-upload-rules-reworked","canonical_anchor":"read-follows-symlinks-and-upload-rules-reworked","heading":"File upload rules reworked, with symlinks followed and resolved paths named","tier":"notice","area":"File Reading","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/read-follows-symlinks-and-upload-rules-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### File upload rules reworked, with symlinks followed and resolved paths named\n\nThe rules for uploading project files were reworked: reads follow symlinks, uploads name resolved paths, and one tool can suggest an allow rule\n\n**Unclear.** Which reads and uploads now behave differently for a user, and how, is not stated.\n\n**What**\n\nClaude Code can upload project files for a request run elsewhere. The code that decides which files go and how they are read changed:\n\n- `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`.\n\n- A file read call now passes `followsLinks: true`, so it follows symbolic links (shortcuts that point to another file).\n\n- An upload tool's settings gain `namesResolvedPaths: true`.\n\n- 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.\n\n**Why**\n\nThis may change how symlinked files are read and uploaded, and which allow rule is suggested in a permission prompt for file uploads.\n\n- Area: File Reading\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}