prompt.context
A Claude Code settings key, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.
A new prompt.context hook event lets plugins add named context blocks to a prompt, capped at 32 blocks and 32000 characters.
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.259.
In the changelogs
6Releases whose published page names prompt.context.
-
v2.1.286
Plugin hooks gain a prompt.compose method and an asUser option on submit
Plugin hooks can now call a new prompt.compose method, and prompt.submit now accepts an asUser option that must be true or false
found in this entry's text
-
v2.1.265
ui.invalidate now supports invalidating command.describe
The ui.invalidate plugin operation can now also invalidate command.describe
found in this entry's text
-
v2.1.259
New functionHooks event: prompt.context
A new prompt.context hook event lets plugins add named context blocks to a prompt, capped at 32 blocks and 32000 characters.
found in this entry's text, named in this entry
-
v2.1.259
New plugin/hook events 'prompt.context' and 'session.start'
Two hook events arrive: session.start fires on terminal session start, and prompt.context is registered but has no emitter here.
found in this entry's text, named in this entry
-
v2.1.259
Plugin UI hooks can now invalidate on prompt.context, not just prompt.section
Plugins can now invalidate prompt.context specifically through ui.invalidate, alongside ui.render and prompt.section.
found in this entry's text, named in this entry
-
v2.1.259
prompt.context dispatch hook point
Computed prompt context blocks are forwarded through a registered prompt.context handler when one exists, alongside a session-bound extension point.
found in this entry's text, named in this entry
First cited
5The earliest release whose published evidence quoted prompt.context was v2.1.259, 2 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
0The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.