{"version":"2.1.247","anchor":"forked-contexts-reuse-the-system-prompt-instead-of-re-render","canonical_anchor":"forked-contexts-reuse-the-system-prompt-instead-of-re-render","heading":"Forked contexts reuse the system prompt instead of re-rendering it","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/forked-contexts-reuse-the-system-prompt-instead-of-re-render","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Forked contexts reuse the system prompt instead of re-rendering it\n\nForked contexts reuse the already-rendered system prompt instead of rebuilding it each time.\n\n**What**\n\nStarting a forked context used to rebuild the system prompt from scratch every time. It now takes a cached bundle when one exists, or the prompt already rendered for the current turn, and only builds a new one as a last resort.\n\n**Details**\n\n- When it does build one, it now passes the current permission mode as well as the main loop's model, so the forked prompt matches the mode you are actually in.\n- The cache-breaking phrase is read from the call's own options rather than global app state.\n\n**Evidence**\n\n`renderedSystemPrompt`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}