{"version":"2.1.280","anchor":"clearer-message-for-unreadable-large-saved-output-files-on-a","canonical_anchor":"clearer-message-for-unreadable-large-saved-output-files-on-a","heading":"Clearer message for unreadable large saved-output files on a remote host","tier":"notice","area":"Remote Tools","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/clearer-message-for-unreadable-large-saved-output-files-on-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Clearer message for unreadable large saved-output files on a remote host\n\nClearer explanation given to Claude when a large tool output is saved to a file it can't read on a remote host\n\n**What**\n\nWhen a tool's output is too large and gets saved to a file on a remote host instead of being sent back directly, the message shown to Claude has been reworded. It used to say to 'read it there'; it now explicitly says the file cannot be read from here, and suggests re-running the command remotely with `head`, `tail`, or `grep` if that's safe.\n\n**Why**\n\nThe old wording could be read as implying Claude could still read the file somehow. The new wording is more explicit about the limitation and gives concrete commands to work around it.\n\n- Area: Remote Tools\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}