{"version":"2.1.292","anchor":"procselffd-path-resolution-refuses-reads-when-the-real-pa","canonical_anchor":"procselffd-path-resolution-refuses-reads-when-the-real-pa","heading":"Linux file reads are refused when the real path of an open file cannot be found","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/procselffd-path-resolution-refuses-reads-when-the-real-pa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Linux file reads are refused when the real path of an open file cannot be found\n\nOn Linux, Claude Code now refuses a file read if the system cannot say where the opened file really is\n\n**What**\n\nOn Linux, Claude Code now asks the system for the real location of a file after opening it, using the `\/proc\/self\/fd` area that Linux provides. If the system cannot answer, Claude Code refuses the read with a message like: Refusing to read : the system would not say where it was opened.\n\nOne mode, called by-spelling, skips this check and returns nothing instead of refusing.\n\n**Why**\n\nThis makes the permission checks on file reads harder to get around. On systems where `\/proc` is not available, reads outside the by-spelling mode can now fail instead of going ahead.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}