{"version":"2.1.269","anchor":"tool-use-display-messages-gain-richer-categorization-displa","canonical_anchor":"tool-use-display-messages-gain-richer-categorization-displa","heading":"Tool-use display messages gain richer categorization: displayHint, team-memory-write flag, and search target classification","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/tool-use-display-messages-gain-richer-categorization-displa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Tool-use display messages gain richer categorization: displayHint, team-memory-write flag, and search target classification\n\nTool-use summaries now include a display hint, a team-memory-write flag, and a search target classification\n\n**What**\n\nWhen Claude Code builds an internal summary of a tool call for display, it now works out more detail automatically:\n\n- `displayHint`: a short snippet of the command or query for bash, list, MCP (external tool integration), and non-team search tools\n\n- `isTeamMemoryWrite`: whether the call wrote to shared team memory\n\n- `searchTarget`: whether a search-type tool call targeted `team_memory`, plain `memory`, or something else\n\nThese join the existing `readPaths`, `editLines`, and `memoryWriteOps` fields already tracked for tool-use records.\n\n**Why**\n\nThis gives the parts of Claude Code that render tool-call activity (and anything consuming these records) finer-grained information about what a tool call actually did, particularly around memory and search operations, without changing what the tools themselves do.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}