{"version":"2.1.284","anchor":"remote-bash-output-can-be-truncated-to-a-caller-supplied-cha","canonical_anchor":"remote-bash-output-can-be-truncated-to-a-caller-supplied-cha","heading":"Shell command output in remote sessions can be capped at a set length","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/remote-bash-output-can-be-truncated-to-a-caller-supplied-cha","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Shell command output in remote sessions can be capped at a set length\n\nShell command output in a remote session can now be cut to a given number of characters, and otherwise is shortened as before\n\n**Unclear.** Nothing in this build appears to supply the limit yet, so the cap may have no effect for now.\n\n**What**\n\nWhen Claude Code runs a shell command in a remote session (one running on another machine rather than your own), it can now cut the command's normal output and its error output to a given number of characters, if a limit is supplied. When no limit is supplied, the output is shortened the same way it was before.\n\nThe remote command runner also no longer returns an identifier for each piece of output.\n\n**Why**\n\nA cap like this limits how much command output a remote session sends back, which matters for commands that print a lot.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}