{"version":"2.1.319","anchor":"bash-tail-pipe-capture-hardened-marks-file-stricter-parsin","canonical_anchor":"bash-tail-pipe-capture-hardened-marks-file-stricter-parsin","heading":"Saving output piped into tail is stricter and safer","tier":"notice","area":"Bash","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/bash-tail-pipe-capture-hardened-marks-file-stricter-parsin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Saving output piped into tail is stricter and safer\n\nClaude Code's saving of output piped into `tail` now checks commands more carefully, skips risky shell forms and checks free disk entries\n\n**What**\n\nWhen a shell command pipes its output into `tail`, Claude Code can save that output to a file. `tail` shows only the last lines. This feature now also writes a marks file and shares its files with the shell more directly. It is applied in fewer cases:\n\n- The command is fully parsed and the `tail` line count must match.\n\n- It is skipped for `eval` of quoted strings.\n\n- It is skipped when built-in shell commands are overridden.\n\n- It is skipped when `||` comes before `tail`.\n\n- It can refuse when the disk has few free file entries at the start.\n\nClaude Code also checks that the marks are valid. Before, the decision used a simple text match, with no disk check and no marks file.\n\n**Why**\n\nUnusual shell commands are less likely to be changed or broken by this feature.\n\n- Area: Bash\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}