{"version":"2.1.323","anchor":"new-tool-results-cut-attachment-and-cut-request-id","canonical_anchor":"new-tool-results-cut-attachment-and-cut-request-id","heading":"New handling for requests whose old tool results were cut","tier":"internal","area":"Tool Results","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/new-tool-results-cut-attachment-and-cut-request-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### New handling for requests whose old tool results were cut\n\nClaude Code recognises `tool_results_cut`, where old tool results are replaced with placeholders, and the teleport relay steps aside for such requests\n\n**Unclear.** It is not clear what makes tool results get cut or when this happens.\n\n**What**\n\nA tool call is a single action Claude takes, such as reading a file, and its output is the tool result. Claude Code now recognises requests where old tool results have been replaced with placeholders.\n\n- Attachment: a `tool_results_cut` attachment type is handled, and `cut_request_id` is accepted as a request id next to `suppressed_request_id`.\n\n- Teleport relay: when a request replaces old tool results with placeholders, the relay falls back to the standard path, logs the reason `tool_results_cut`, and reports whether placeholders are being sent. The relay's tools-used header handling also changed, so its MCP flag no longer depends on a second check.\n\n- Reason labels: `tool_results_cut` was added to a list of reasons, and a new `vm_unavailable` case sits next to `cloud_unavailable` and `network_off`.\n\n**Why**\n\nThese changes point to a way of trimming old tool output from a conversation. Where history has been rewritten like this, the relay uses the normal path instead of passing it on.\n\n- Area: Tool Results\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}