Two months before it changed its name to "Meta," Facebook CEO Mark Zuckerberg personally introduced us to his metaverse for work: Horizon Workrooms, envisioned as a virtual space for workers to collaborate. Today, the company announced it's shutting that space down: "Meta has made the decision to discontinue Workrooms as a standalone app, effective February 16, 2026," reads the note tucked away on a help page.
Meta will also no longer sell its headsets and software as a service for businesses, another help page reads: "We are stopping sales of Meta Horizon managed services and commercial SKUs of Meta Quest, effective February 20, 2026."
There's a new name in charge of stewarding Star Wars at Lucasfilm. The studio just announced that Dave Filoni - best-known for his work on The Mandalorian and The Clone Wars - will be taking over as president. Former president Kathleen Kennedy, whose departure had been rumored for some time, will be stepping down and returning to producing films full-time.
Under the new structure, Filoni will continue to serve as chief creative officer at Lucasfilm, alongside becoming the studio's president. Lynwen Brennan, who has been at the studio since 1999 and most recently served as president and GM of Lucasfilm business, will be co-president.
From the floor at AWS re:Invent, Ryan is joined by AWS Senior Principal Engineer David Yanacek to chat about all things AWS, from the truth behind AWS’s Black Friday origin mythos to the development of essential cloud tools like SQS and DynamoDB. Plus, how David envisions autonomous agents will ease developers' operational burdens.
Our vision is to evolve GitHub Copilot into an ecosystem of agents that collaborate across the entire development lifecycle from coding and code review to security, debugging, deployment, and maintenance. To unlock the full potential of multi-agent workflows, we need to move beyond isolated interactions—that start from scratch each session—and toward a cumulative knowledge base that grows with every use.
Cross-agent memory allows agents to remember and learn from experiences across your development workflow, without relying on explicit user instructions.
Each interaction teaches Copilot more about your codebase and conventions, making it increasingly effective over time. For example, if Copilot coding agent learns how your repository handles database connections as it’s fixing a security vulnerability, Copilot code review can then use that knowledge to spot inconsistent patterns in future pull requests. Or if Copilot code review notices that certain files must stay synchronized, in the future Copilot coding agent will automatically update them together when generating new code.
The challenge: What to remember and when to forget
Our agents continuously improve at extracting the context needed for specific tasks. The core challenge for memory systems isn’t about information retrieval, but ensuring that any stored knowledge remains valid as code evolves across branches and time.
In practice, this means a memory system must handle changes to code, abandoned branches, and conflicting observations—all while ensuring that agents only act on information that’s relevant to the current task and code state. For example, a logging convention observed in one branch may later be modified, superseded, or never merged at all.
One option would be to implement an offline curation service to deduplicate, resolve conflicts, track branch status, and expire stale information. At GitHub’s scale, however, such an approach would introduce significant engineering complexity and LLM costs, while still requiring mechanisms to reconcile changes at read time. We started by exploring a simpler, more efficient approach.
Our solution: just-in-time verification
Information retrieval is an asymmetrical problem: It’s hard to solve, but easy to verify. By using real-time verification, we gain the power of pre-stored memories while avoiding the risk of outdated or misleading information.
Instead of offline memory curation, we store memories with citations: references to specific code locations that support each fact. When an agent encounters a stored memory, it verifies the citations in real-time, validating that the information is accurate and relevant to the current branch before using it. This verification boils down to a small number of simple read operations, adding no significant latency to agent sessions in our testing.
Memory creation as a tool call
We implemented memory creation as a tool that agents can invoke when they discover something that’s likely to have actionable implications for future tasks.
How Copilot agents store learnings worth remembering as they carry out their tasks.
Consider this example: While reviewing a pull request from an experienced developer, Copilot code review discovers that API version tracking must stay synchronized across different parts of a codebase. It might encounter these three updates in the same pull request:
In src/client/sdk/constants.ts:
export const API_VERSION = "v2.1.4";
In server/routes/api.go:
const APIVersion = "v2.1.4"
In docs/api-reference.md:
Version: v2.1.4
In response, Copilot code review can invoke the memory storage tool to create a memory like this:
{
subject: "API version synchronization",
fact: "API version must match between client SDK, server routes, and documentation.",
citations: ["src/client/sdk/constants.ts:12", "server/routes/api.go:8", "docs/api-reference.md:37"],
reason: "If the API version is not kept properly synchronized, the integration can fail or exhibit subtle bugs. Remembering these locations will help ensure they are kept syncronized in future updates."
}
The result: The next time an agent updates the API version in any of these locations, it will see this memory and realize that it must update the other locations too, preventing a versioning mismatch that could break integrations. Similarly, if an inexperienced developer opens a pull request that updates only one of these locations, Copilot code review will flag the omission and suggest the missing updates, automatically transferring knowledge from a more experienced team member to a newer one. 💥
Memory usage
Retrieval
When an agent starts a new session, we retrieve the most recent memories for the target repository and include them in the prompt. Future implementations will enable additional retrieval techniques, such as a search tool and weighted prioritization.
How Copilot enriches agent prompts with memories from previous tasks.
Verification
Before applying any memory, the agent is prompted to verify its accuracy and relevance by checking the cited code locations. If the code contradicts the memory, or if the citations are invalid (e.g. point to nonexistent locations), the agent is encouraged to store a corrected version of the memory reflecting the new evidence. If the citations check out and the memory is deemed useful, the agent is encouraged to store it again in order to refresh its timestamp.
Privacy and security
It’s important to note that memories are tightly scoped. Memories for a given repository can only be created in response to actions taken within that repository by contributors with write permissions, and can only be used in tasks on that same repository initiated by users with read permissions. Much like the source code itself, memories about a repository stay within that repository, ensuring privacy and security.
Cross-agent memory sharing
The full power of our memory system emerges as different Copilot agents learn from one another.
Copilot code review discovers a logging convention while reviewing a pull request: “Log file names should follow pattern ‘app-YYYYMMDD.log’. Use Winston for logging with format: timestamp, error code, user ID.”
Copilot coding agent is later assigned a task to implement a new microservice. It sees and verifies the memory and automatically applies the same logging format.
Copilot CLI helps a developer debug an issue, efficiently retrieving the correct log file and finding the relevant timestamps based on the logging format learned by the code review agent.
Each agent contributes to and benefits from the shared knowledge base, allowing agents to reuse validated repository knowledge across tasks. As additional agents adopt memory—whether for development workflows, debugging, or security analysis—they’ll contribute to and benefit from the same evolving understanding of your codebase.
Evaluation
Stress-testing agent resilience
Our biggest concern was the impact of outdated, incorrect, or even maliciously injected memories. To test the system’s resilience, we deliberately seeded repositories with adversarial memories–facts that contradicted the codebase–with citations pointing to irrelevant or nonexistent code locations.
Across all test cases, agents consistently verified citations, discovered contradictions, and updated incorrect memories. The memory pool self-healed as agents stored corrected versions based on their observations. The citation verification mechanism robustly prevented the risk of misleading memories.
Simulating a realistic memory pool
For each repository in our evaluation set, we ran agents on diverse historical tasks (predating our target evaluation tasks) and let them populate the memory database organically, using the “store_memory” tool we provided. To simulate worst-case conditions, we overrepresented memories from branches that were abandoned or closed without merging, ensuring realistically noisy memories.
When we ran Copilot code review on the pull requests in our evaluation set, memory usage led to 3% increase in precision and 4% increase in recall.
Measuring impact on developers
The ultimate test of our memory system was its impact on real developers in their everyday workflows. We ran A/B tests on the first two Copilot agents to deploy memory, Copilot code review and Copilot coding agent, measuring the impact on key user metrics.
Copilot coding agent: 7% increase in pull request merge rates (90% with memories vs. 83% without). This means developers are saving more time and getting the desired results more often when they assign tasks to Copilot.
Copilot code review: 2% increase in positive feedback on comments (77% with memories vs 75% without). This means automated code review is yielding improved quality assurance.
Both increases are highly statistically significant, with p-value <0.00001
These results demonstrate that cross-agent memory delivers measurable value to developers in their daily workflows.
What’s next
We’ve deployed repository-scoped memory storage and usage in Copilot CLI, Copilot coding agent, and Copilot code review on an opt-in basis. We’re listening to user feedback and tracking performance metrics closely as we iterate and prepare for a wider rollout across more Copilot workflows. We’re also exploring a range of approaches to tuning memory generation, curation, prioritization, and usage.
Cross-agent memory reduces the need to re-establish context at the start of each task by allowing validated information to persist across agentic workflows. We’re excited about the possibilities memory will unlock, and we’re just getting started. We look forward to your feedback so we can ensure GitHub Copilot continues to evolve in ways that best support your needs. Happy coding!
Read our Docs to learn how to enable memory in Copilot >
The 1st cumulative update release for SQL Server 2025 RTM is now available for download at the Microsoft Downloads site. Please note that registration is no longer required to download Cumulative updates. To learn more about the release or servicing model, please visit:
Starting with SQL Server 2017, we adopted a new modern servicing model. Please refer to our blog for more details on Modern Servicing Model for SQL Server
Crispin Thompson is the Founder and Principal Consultant at The Leadership Studio, offering nearly 30 years of experience in leadership roles throughout the technology industry. With a proven track record in driving transformational change, he specializes in digital transformation, pricing strategy, and operations management. Known for his hands-on, people-first approach, Crispin empowers teams to thrive and achieve exceptional results through effective coaching services.
Before founding The Leadership Studio, Crispin served as an Executive at a Fortune 100 tech company, where he led cross-functional teams to achieve groundbreaking successes in partner and finance transformations. His leadership development initiatives consistently bridged the gap between high-level strategy and operational execution, earning recognition for innovative solutions and strategic insight.
At The Leadership Studio, Crispin leverages his expertise to help individuals and organizations navigate complex challenges and build sustainable paths to success. He is passionate about fostering growth, driving impactful change, and cultivating a culture of excellence, all while enhancing team expertise.
Outside of work, Crispin enjoys traveling, playing some very mediocre golf, and spending time with his young daughter, reflecting his belief in a balanced and well-rounded approach to leadership.
I hope you enjoyed this show, please head over to Apple Podcasts and subscribe and leave me a rating and review, even one sentence will help spread the word. Thanks again!
Log in
