{"version":"2.1.246","anchor":"publish-tool-calls-are-recorded-so-follow-up-turns-can-see-t","canonical_anchor":"publish-tool-calls-are-recorded-so-follow-up-turns-can-see-t","heading":"Publish tool calls are recorded so follow-up turns can see them","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/publish-tool-calls-are-recorded-so-follow-up-turns-can-see-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Publish tool calls are recorded so follow-up turns can see them\n\nPublishing through a tool now leaves a record in the conversation so later turns can see it.\n\n**What**\n\nWhen Claude publishes something through a tool call, the call and its result are now built into a record that is expanded into synthetic messages and appended to the conversation, unless they are already the last thing in the transcript.\n\n**Details**\n\n- Built only when the tool call has an identifier and the publish is not chained onto another publish.\n- The publish result is attached to the same record before it is returned.\n\n**Evidence**\n\n`publishTranscript`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}