{"version":"2.1.229","anchor":"sibling-workflow-agents-stagger-their-first-request-to-warm-","canonical_anchor":"sibling-workflow-agents-stagger-their-first-request-to-warm-","heading":"Sibling workflow agents stagger their first request to warm the cache","tier":"use","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/sibling-workflow-agents-stagger-their-first-request-to-warm-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Sibling workflow agents stagger their first request to warm the cache\n\nParallel workflow agents stagger their first call to share cache; tune with an env var.\n\n**What**\n\nWhen several workflow agents start with an identical prompt prefix, the followers now wait briefly for the leader's first response so their request hits the prompt cache instead of paying full price for the same prefix. The wait is capped by `CLAUDE_CODE_WORKFLOW_PREFIX_STAGGER_MS`, which has a built-in default when unset and is forced to 0 when `DISABLE_PROMPT_CACHING` is set.\n\n**Details**\n\n- Agents sharing a prefix register in a warm-up map; the first one through is the leader\n- Followers wait up to the cap, then proceed regardless\n- With prompt caching disabled there is no wait at all\n\n**Evidence**\n\n`CLAUDE_CODE_WORKFLOW_PREFIX_STAGGER_MS`\n\n- Area: Workflows\n- Names: `CLAUDE_CODE_WORKFLOW_PREFIX_STAGGER_MS`, `DISABLE_PROMPT_CACHING`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}