{"version":"2.1.287","anchor":"remote-shell-tool-output-previews-and-progress-forwarded-to","canonical_anchor":"remote-shell-tool-output-previews-and-progress-forwarded-to","heading":"Served shell calls now capture live output, unless PostToolUse or tool.call hooks are set","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/remote-shell-tool-output-previews-and-progress-forwarded-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Served shell calls now capture live output, unless PostToolUse or tool.call hooks are set\n\nShell commands in remote-served sessions now keep a live tail of their output, skipped when PostToolUse hooks or tool.call handlers exist\n\n**Unclear.** When this behaviour is switched on is not known.\n\n**What**\n\nIn a remote-served session, where Claude Code runs commands on behalf of another host, progress from shell commands (bash and PowerShell) is now forwarded instead of skipped. A new handler, `onShellProgress`, keeps the last part of the output and records it with `calls.noteOutput`. It also notes whether the beginning was cut off (`truncated_head`) and the total size (`total_bytes`).\n\nThis capture is skipped when any of these is present:\n\n- a command-type `PostToolUse` hook, a hook that runs after a tool call succeeds\n\n- a `tool.call` handler from a plugin\n\n- another matching hook\n\n**Why**\n\nRemote tool calls can show a live preview of a running command's output. If you have your own `PostToolUse` hooks or `tool.call` handlers set up, this capture does not happen, so the preview will not appear.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}