{"version":"2.1.318","anchor":"bash-tail-handling-bails-out-on-process-substitution","canonical_anchor":"bash-tail-handling-bails-out-on-process-substitution","heading":"Shell commands with process substitution skip special end-of-command handling","tier":"internal","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/bash-tail-handling-bails-out-on-process-substitution","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Shell commands with process substitution skip special end-of-command handling\n\nClaude Code no longer gives special end-of-command handling to shell commands that contain `(`\n\n**What**\n\nClaude Code checks the end of some shell commands for special handling. It now skips that handling when the command contains process substitution, the `<(...)` or `>(...)` form that feeds one command's output in as if it were a file. Before, it skipped only for commands using `tee`, `enable` or `coproc`.\n\n**Why**\n\nProcess substitution makes a command harder to read correctly, so Claude Code now leaves such commands out of the special handling rather than risk misreading them.\n\n- Area: Bash Tool\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}