{"version":"2.1.317","anchor":"new-sdk-tool-result-metadata-field-built-in-tool","canonical_anchor":"new-sdk-tool-result-metadata-field-built-in-tool","heading":"SDK tool results can say which built-in tool produced them","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/new-sdk-tool-result-metadata-field-built-in-tool","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### SDK tool results can say which built-in tool produced them\n\nTool results sent to SDK programs can now carry an optional field naming the built-in Claude Code tool that produced them\n\n**Unclear.** Which built-in tools fill in this value is not stated, so an SDK program cannot yet rely on finding it for any given tool.\n\n**What**\n\nThe SDK lets other programs run Claude Code and read what it does. Each tool result it sends them carries some display information. That information can now include an optional `built_in_tool` value. This value names the built-in Claude Code tool whose own completed run produced the result.\n\n**Why**\n\nA program built on the SDK can use this to react to the results of specific built-in tools.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}