{"version":"2.1.242","anchor":"tool-host-output-gets-its-own-attachment-types","canonical_anchor":"tool-host-output-gets-its-own-attachment-types","heading":"Tool-host output gets its own attachment types","tier":"internal","area":"Remote Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/tool-host-output-gets-its-own-attachment-types","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Tool-host output gets its own attachment types\n\nTwo attachment types for tool-host output and notices were added to the accepted set.\n\n**What**\n\nTwo attachment types for output from a tool host, one for its result lines and one for a notice about it, were added to the accepted set, along with a matching message subtype check.\n\n**Details**\n\n- The notice is pushed during an attachment scan only when its producer hook is present, so whether it appears in practice depends on that producer being wired up.\n\n**Evidence**\n\n`tool_host_result_lines`\n\n- Area: Remote Tools\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}