{"version":"2.1.318","anchor":"remote-control-tool-results-and-inputs-are-size-capped","canonical_anchor":"remote-control-tool-results-and-inputs-are-size-capped","heading":"Remote Control apps get shortened tool inputs and capped tool results","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/remote-control-tool-results-and-inputs-are-size-capped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Remote Control apps get shortened tool inputs and capped tool results\n\nTool results sent to Remote Control apps are rebuilt as text, oversized ones are replaced with a message, and long tool inputs are shortened\n\n**Unclear.** It is not clear whether this applies to all tool calls or only to tools called from scripts.\n\n**What**\n\nA tool call is one action Claude takes, such as running a command, and its result is what comes back. When Claude Code sends these to a Remote Control app:\n\n- Tool results are rebuilt as plain text.\n\n- Results that are too large are replaced by a message saying the output is too large to show.\n\n- Long tool inputs are shortened.\n\n- Progress from tools called inside a script is held back until the result is sent.\n\n**Why**\n\nRemote apps receive messages of a limited size, so a very large tool result no longer has to travel to them in full.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}