The GitHub Copilot SDK has added optional memory configuration to session create and resume flows. Memory configuration is distinct from persisted sessions: persisted sessions store the full conversation thread for cross-process durability, while memory lets the agent read and write facts across turns within a session — like a notepad. The new MemoryConfiguration type exposes an Enabled flag, which must be explicitly set when using CopilotClientMode.Empty. Both features can be used simultaneously, and memory can be toggled independently on new or resumed sessions.
Table of contents
The wrong mental model firstWhat memory configuration actually doesThe mode-based default mattersPersisted sessions vs. memory: the actual differenceResuming with memoryMore information680 Impressions