{"version":"2.1.309","anchor":"stdio-handling-for-subprocess-no-longer-assumes-proc","canonical_anchor":"stdio-handling-for-subprocess-no-longer-assumes-proc","heading":"Redirected input and output for subprocesses is detected without \/proc paths","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/stdio-handling-for-subprocess-no-longer-assumes-proc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Redirected input and output for subprocesses is detected without \/proc paths\n\nClaude Code no longer relies on \/proc paths to tell whether a subprocess's input or output is redirected\n\n**What**\n\nWhen Claude Code starts another program, it checks whether that program's input or output is redirected somewhere else. It used to decide this by checking whether the path began with `\/proc\/` followed by its own process number. `\/proc` is a special folder on Linux that describes running programs. It now compares the path with the one belonging to that input or output channel directly.\n\n**Why**\n\nThis could fix passing input and output through to programs in environments where the old `\/proc` check gave the wrong answer.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}