{"version":"2.1.286","anchor":"promptcompose-plugin-hook-point","canonical_anchor":"promptcompose-plugin-hook-point","heading":"Plugins can now take over how the system prompt is put together","tier":"use","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/promptcompose-plugin-hook-point","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Plugins can now take over how the system prompt is put together\n\nA new `prompt.compose` hook point lets a plugin module build the system prompt from its sections, and Claude Code falls back to its own if that fails\n\n**What**\n\nThe system prompt is the set of standing instructions Claude Code gives the model at the start of each conversation, built from several sections. Plugins can now hook into how those sections are put together through a new hook point, `prompt.compose`.\n\n- When a plugin module implements `prompt.compose`, Claude Code builds the system prompt through it.\n\n- If that call fails, Claude Code builds the prompt itself as before.\n\n- The existing `prompt.section` hook point now also passes along where each section came from.\n\n- Plugins also get a new compose function that builds a system prompt from supplied facts, and it raises an error when the running process builds no system prompt.\n\n**Why**\n\nPlugin authors can now reorder or replace sections of the system prompt. Nothing changes unless a plugin module actually implements the hook.\n\n- Area: Plugins\n- Names: `prompt.compose`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 4\/5"}