{"version":"2.1.248","anchor":"publishing-a-live-doc-binds-the-file-as-a-working-copy","canonical_anchor":"publishing-a-live-doc-binds-the-file-as-a-working-copy","heading":"Publishing a live doc binds the file as a working copy","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/publishing-a-live-doc-binds-the-file-as-a-working-copy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Publishing a live doc binds the file as a working copy\n\nPublishing a live doc keeps your local file bound to the published document.\n\n**What**\n\nAfter a live-doc publish, Claude Code now binds the published file as a working copy and returns that binding on the publish result, so the local file stays connected to the published document.\n\n**Details**\n\n- Runs only when the publish is recognised as a live doc and was not a typed or explicit file-path publish.\n- Gated by the existing live-files gate alongside the live-doc kind check; no separate named flag.\n- The result carries a new `liveDocWorkingCopy` field next to the existing `liveDocCollab`.\n\n**Evidence**\n\n`bindPublishedFileAsWorkingCopy`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}