{"version":"2.1.251","anchor":"follow-ups-delivered-straight-to-a-running-artifact-editor","canonical_anchor":"follow-ups-delivered-straight-to-a-running-artifact-editor","heading":"Follow-ups delivered straight to a running artifact editor","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/follow-ups-delivered-straight-to-a-running-artifact-editor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Follow-ups delivered straight to a running artifact editor\n\nFollow-ups can go straight to a working artifact editor if you set an environment variable.\n\n**What**\n\nA follow-up message on a thread can be handed directly to an artifact editor sub-agent that is still working, instead of going back through the coordinator first. It requires the environment variable `CLAUDE_CODE_EDITOR_CODELIVERY` to be set to a truthy value and the session to be a relayed human conversation; otherwise the path is skipped entirely.\n\n**Details**\n\n- Matching relies on the editor's acknowledgement carrying a follow-up URL, checked against the coordinator's record of which editors are live.\n- Carries messages for the races this opens up: the worker dying mid-flight, the page being deleted, the page being republished by someone else, and the follow-up being withdrawn or cancelled.\n\n**Usage**\n\n`CLAUDE_CODE_EDITOR_CODELIVERY=1 claude` **Evidence** `artifact_editor_codelivery`\n\n- Area: Artifacts\n- Names: `CLAUDE_CODE_EDITOR_CODELIVERY`\n- Tier: Nothing to try yet\n- Useful: 3\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}