{"version":"2.1.323","anchor":"at-mentioned-notebook-files-and-line-ranges","canonical_anchor":"at-mentioned-notebook-files-and-line-ranges","heading":"@-mentioned notebooks and large files are handled more completely","tier":"notice","area":"File Attachments","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/at-mentioned-notebook-files-and-line-ranges","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### @-mentioned notebooks and large files are handled more completely\n\n@-mentioned notebooks attach as parsed cells, and oversized files come with exact line ranges so Claude can read the whole file\n\n**What**\n\nTyping `@` followed by a file name attaches that file to your message.\n\n- Notebooks: Jupyter notebook files are now attached as a parsed `notebook` block of cells instead of raw text.\n\n- Large files: when a file is too big to attach whole and ranges are supplied, the mention can come back as `unread: \"in_ranges\"` with line ranges. Before, large files were cut short or marked `too_large`.\n\n- Read instructions: for an oversized file, Claude is told to make a set of parallel Read calls with exact `offset` and `limit` values that together return the whole file. Before, it only got general advice to read the file in portions.\n\n**Why**\n\nMentioning a big file or a notebook should give Claude its full contents in a usable shape, instead of a truncated file or a wall of notebook JSON.\n\n- Area: File Attachments\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}