|
Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
|
The GitHub Copilot SDK just shipped a new feature: optional memory configuration on session create and resume. Here is what it does, and how it is different from persisted sessions.
When I heared "session memory" my first thought was "persisted sessions" — the ResumeSessionAsync flow that lets you reload an existing session by ID and continue where you left off. That is not what this is. Persisted sessions are about durability of the conversation itself: close the app, reopen it, pick up the thread. Memory configuration is something different.
Memory is a feature of the Copilot runtime that lets the agent read and write facts across turns — a kind of long-running knowledge store that the agent can consult and update during a session. Think of it as the agent's notepad, not the conversation log.
The new MemoryConfiguration type exposes a single Enabled flag today. You opt in per session, on both create and resume:
Log in
var session = await client.CreateSessionAsync(new SessionConfig
{
Model = "gpt-4o",
Memory = new MemoryConfiguration { Enabled = true }
});That's it. The SDK serialises it as { "memory": { "enabled": true } } on the wire. When you leave Memory unset, the field is omitted entirely and the runtime applies its own default.
Now we can ask our agent to remember stuff:
There is a subtle default you need to understand. The SDK has two client modes:
CopilotClientMode.CopilotCli (the default): Memory is left unset. The runtime decides. CopilotClientMode.Empty: Memory defaults to disabled unless you explicitly set it. A caller-supplied value always wins in either mode. If you are building an app on Empty mode and you want memory, you must opt in explicitly. The runtime will not silently enable it for you.
| Persisted sessions | Memory configuration | |
| What it stores | The full conversation thread | Facts/notes the agent writes |
| Lifetime | Until you delete the session | Managed by the runtime |
| API surface | ResumeSessionAsync(sessionId) |
SessionConfig.Memory |
| Scope | Cross-process, cross-restart | Within the session, agent-controlled |
A persisted session lets you reload the conversation. Memory lets the agent remember things across turns within — and potentially across — sessions, depending on how the runtime implements it.
You can use both at the same time: resume a persisted session with memory enabled, and the agent brings its notepad along.
ResumeSessionAsync also accepts the memory configuration:
var session = await client.ResumeSessionAsync(sessionId, new ResumeSessionConfig
{
Memory = new MemoryConfiguration { Enabled = true }
});This means you can control memory independently of whether the session is new or resumed. Useful if you want to enable memory for an existing session that was originally created without it.
PR #1617 — SDK: add optional memory configuration to session create and resume
The Verifiable Credentials Working Group has published a First Public Working Draft today for the Verifiable Credential Forgery Defense v1.0 specification. This publication is complementary to the publication of quantum-resistant cryptosuites and is motivated by the same threat. While cryptosuites let issuers secure new proofs with post-quantum signatures, this specification lets an issuer establish post-quantum-backed authenticity for credentials that may have been signed with conventional quantum-vulnerable algorithms and cannot, or is not feasible, to re-issue them. This is achieved by publishing a witness list that is itself the subject of a separate Verifiable Credential that can be signed with a quantum-resistant scheme.
The Working Group welcomes comments via the GitHub repository issues.
The Pointer Events Working Group is pleased to publish Pointer Events Level 3 as a W3C Recommendation. The features in this specification extend or modify those found in Pointer Events, a W3C Recommendation that describes events and related interfaces for handling hardware-agnostic pointer input from devices including a mouse, pen, or touchscreen. For compatibility with existing mouse-based content, this specification also describes a mapping to fire Mouse Events for other pointer device types.
This revision includes new features: altitudeAngle, azimuthAngle, pointerrawupdate event, associated coalesced events, and built-in predicted events.
Following the newer Recommendation, Pointer Events Level 2 has been marked as a W3C Superseded Recommendation:
1198. This week, we look at how to answer the question every author dreads: "So, what's your book about?" with workplace communications coach Joel Schwartzberg. We look at the difference between describing a book and selling it, how nonfiction authors can craft point-driven responses, and how fiction writers can distill their stories into a compelling pitch.
Joel Schwartzberg is a workplace communications coach, speaker, and speechwriter. He's the author of "Get to the Point: Simplify, Sharpen, and Sell Your Message," and you can find him at joelschwartzberg.net
🔗 Join the Grammar Girl Patreon.
🔗 Share your familect recording in Speakpipe or by leaving a voicemail at 833-214-GIRL (833-214-4475)
🔗 Watch my LinkedIn Learning writing courses.
🔗 Subscribe to the newsletter.
🔗 Find an edited transcript.
🔗 Get Grammar Girl books.
| HOST: Mignon Fogarty
| Grammar Girl is part of the Quick and Dirty Tips podcast network.
| Theme music by Catherine Rannus.
| Grammar Girl Social Media: YouTube. TikTok. Facebook. Threads. Instagram. LinkedIn. Mastodon. Bluesky.
Hosted on Acast. See acast.com/privacy for more information.
