{"version":"2.1.271","anchor":"new-constant-caps-for-an-artifact-editor-coordinator-threa","canonical_anchor":"new-constant-caps-for-an-artifact-editor-coordinator-threa","heading":"New constant caps for an 'artifact editor coordinator' thread-follow-up URL","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/new-constant-caps-for-an-artifact-editor-coordinator-threa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### New constant caps for an 'artifact editor coordinator' thread-follow-up URL\n\nArtifact-editor follow-up delivery now enforces a length cap and a roughly 20-minute time value\n\n**Unclear.** What the 20-minute constant is actually used to time is not specified in the evidence.\n\n**What**\n\nThe code path that delivers a thread follow-up message directly to a running artifact editor (enabled via the `CLAUDE_CODE_EDITOR_CODELIVERY` environment variable) now enforces a maximum length of 2048 characters on the follow-up URL it parses, and uses a new constant of 1,200,000 milliseconds (about 20 minutes) elsewhere in the same flow.\n\n**Why**\n\nThe length cap guards against malformed or oversized follow-up URLs being processed; the roughly 20-minute value likely bounds how long the direct-delivery path stays valid, though the finding doesn't say exactly what it times out.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}