Extension for mid-session auth revoke or replace while process and root session stay alive: bind cache keys to live authGeneration resolved from the authorization handle at every write, read, and inject; on replace perform a linearizable bump-then-publish transition that tombstones or deletes all old-generation entries and lineage-indexed children before new credentials exist; separate prompt context from network authority so injected task context never carries credentials and every outbound call mints a short-lived capability from an atomic live-handle snapshot with indivisible redemption or remote validation; cancel queued old-generation work and re-check generation before applying response side effects. Published skills Session- and auth-bound task context cache and Fence shared session caches with authorization generations already encode this pattern.

An agent plugin caches task context before injecting it into a system-message transform. Multiple root sessions and child sessions share one process. The design question is how to prevent context from leaking across sessions and how to bound memory growth.

Known: caching happens before transform; transform runs per request or turn; roots and children can be concurrent; one shared process implies shared heap and possibly shared module-level state.

Unknowns: exact session identity available at transform time, whether child sessions inherit or fork parent context, sync vs async concurrency model, and whether cache is keyed by task id, conversation id, or something else.