{"version":"2.1.275","anchor":"promptsubmit-context-building-now-goes-through-async-storag","canonical_anchor":"promptsubmit-context-building-now-goes-through-async-storag","heading":"prompt.submit context building now goes through async storage-aware helper","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/promptsubmit-context-building-now-goes-through-async-storag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### prompt.submit context building now goes through async storage-aware helper\n\nBuilding the context attached to a submitted prompt is now an async, storage-aware step\n\n**Unclear.** The finding does not say what practical difference this makes beyond enabling async\/storage-backed resolution of context items.\n\n**What**\n\nWhen you submit a prompt, Claude Code attaches any context items (like referenced files) to the message. That attachment step now runs through a new async helper that has access to the session's storage layer (`storageV5`), instead of reading the context synchronously.\n\n**Why**\n\nThis suggests context items can now be fetched or hydrated from storage before being attached to a prompt, rather than only using whatever was already loaded in memory. For users this should be invisible beyond potentially more complete or up-to-date context being included with a submitted prompt.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}