## Table of Contents * [Project Updates](https://gitlab.com/groups/gitlab-org/-/work_items/20966#project-updates) * [Problem to Solve](https://gitlab.com/groups/gitlab-org/-/work_items/20966#problem-to-solve) * [Customer Problems (ordered by priority)](https://gitlab.com/groups/gitlab-org/-/work_items/20966#customer-problems-priority-order) * [Development Timeline](https://gitlab.com/groups/gitlab-org/-/work_items/20966#development-timeline) * [Project Stakeholders](https://gitlab.com/groups/gitlab-org/-/work_items/20966#project-stakeholders) * [Project Resources](https://gitlab.com/groups/gitlab-org/-/work_items/20966#project-resources) --- ## Project Updates Curious where this project stands? Find recent updates below: * [2026-06-24](https://gitlab.com/groups/gitlab-org/-/work_items/20966#note_3490847735) * [2026-06-17](https://gitlab.com/groups/gitlab-org/-/work_items/20966#note_3466854493) * [2026-06-11](https://gitlab.com/groups/gitlab-org/-/work_items/20966#note_3450589328) * [2026-06-10](https://gitlab.com/groups/gitlab-org/-/work_items/20966#note_3442790731) * [2026-06-04](https://gitlab.com/groups/gitlab-org/-/work_items/20966#note_3424312285) * [2026-05-27](https://gitlab.com/groups/gitlab-org/-/work_items/20966#note_3392090364) * [2026-05-19](https://gitlab.com/groups/gitlab-org/-/work_items/20966#note_3365333652) * [2026-05-06](https://gitlab.com/groups/gitlab-org/-/work_items/20966#note_3322301097) ## **Problem to Solve** GitLab is missing a key component to compete in the fast-changing AI landscape: memory. Major AI platforms are converging on this idea ([LangChain](https://docs.langchain.com/oss/python/concepts/memory), [Anthropic](https://platform.claude.com/docs/en/agents-and-tools/tool-use/memory-tool), [GitHub](https://docs.github.com/en/copilot/concepts/agents/copilot-memory)). Without memory every session starts from scratch, agents have no knowledge of team standards, past decisions, prior mistakes, or unfinished work, users have to re-establish context every time, output stays generic because agents have no understanding of how a particular team operates, and nothing gets better with use. As workflows get more complex, the problem compounds. The following customers have validated the need for Memory: * https://gitlab.com/groups/gitlab-org/-/work_items/20966#note_3439032868 * https://gitlab.com/groups/gitlab-org/-/work_items/20966#note_3377074728 * https://gitlab.com/groups/gitlab-org/-/work_items/20966#note_3238215342 * https://gitlab.com/groups/gitlab-org/-/work_items/20966#note_3086776816 ## Customer Problems (ordered by priority) <table> <tr> <th> \# </th> <th>Problem</th> <th>Customer Validation</th> </tr> <tr> <td>1</td> <td> **Problem:** Agent starts from scratch every session - context is lost after every session. Agent doesn't know our team's standards and conventions. **Structured as a Job to be Done:** When I start a new session, I want the agent to already know my team's standards and past decisions, so that I don't have to re-establish context every time. </td> <td>Archer: sessions lock out with no recovery; group-level custom instructions needed across all Duo features</td> </tr> <tr> <td>2</td> <td> **Problem:** Agent repeats the same mistakes - no feedback loop despite direct user feedback in app or chat. **Structured as a Job to be Done:** When I give the agent feedback, I want that feedback to stick, so that the agent stops repeating the same mistakes and improves over time. </td> <td>Code Review quality issue: feedback signals not closing the loop vs. Cursor BugBot</td> </tr> <tr> <td>3</td> <td> **Problem:** Complex workflows re-derived from scratch every invocation. **Structured as a Job to be Done:** When I run a complex workflow, I want the agent to remember how we've approached similar work before, so that we're not starting from zero every time. </td> <td>DAP memory issue: agent should not repeat everything, should develop skills</td> </tr> <tr> <td>4</td> <td> **Problem:** Sub-agents and external agents are context-blind to each other. **Structured as a Job to be Done:** When multiple agents are working together, I want them to share context with each other, so that nothing falls through the cracks and work doesn't have to be repeated. </td> <td>DevRel field issue: shared memory for external + DAP agents is an open gap</td> </tr> </table> ## Development Timeline | Delivery Item | Delivery Item Description | Due Date | |---------------|---------------------------|----------| | [Engineering and Design Spike](https://gitlab.com/gitlab-org/gitlab/-/work_items/598733) | The objective of the Spike is to align on a PoC, get stakeholder sign-off on the requirements and customer problems laid out for Beta, GA, and Post-GA, design the architecture required to achieve the outcomes required in the Beta, GA, and Post-GA, and ensure alignment with Duo Workflow Service and Spec Driven Development DRIs. | 2026-07-10 (end of %&quot;19.2&quot; ) | | [Beta Release](https://gitlab.com/groups/gitlab-org/-/work_items/21883) | We'll release a Beta version that provides us a feedback mechanism to improve the functionality before we hit GA. | 2026-09-11 (%19.4 release) | | [General Availability](https://gitlab.com/groups/gitlab-org/-/work_items/21884) | We'll refine the functionality based on real user experience and deliver a fully functionality and mature offering for users. | 2026-11-13 (%&quot;19.6&quot; release) | | [Post General Availability Work](https://gitlab.com/groups/gitlab-org/-/work_items/21885) | After the functionality goes GA we'll continue to collect feedback, listen to users, and improve the offering. | N/A | ## Project Stakeholders Primary: * Engineering Manager: @armin.pasalic * Engineering Manager: @aying-gl * Senior Machine Learning Engineer: @junminghuang * Backend Engineer: @tmrrss * Backend Engineer: @rchanyj * Staff Backend Engineer: @ghavenga * Senior Product Manager: @mmacfarlane * Senior Product Manager: @frwang1 Contributors: * Principal Developer Advocate: @dnsmichi * Senior Engineering Manager: @bastirehm * Knowledge Graph Lead: @michaelangeloio * Product Manager: @mcorren * Staff Product Designer: @nickleonard * Principal Engineer: @engwan ## Project Resources * Memory Slack Channel: [#f_memory](https://gitlab.enterprise.slack.com/archives/C0B8CTJVBN2) * Memory Wiki: [Spec Driven Development Memory System Planning](https://gitlab.com/groups/gitlab-org/-/wikis/Spec-Driven-Development-Memory-System---Planning) * Memory Meeting Notes: [Notes for Sync Meetings Related to Project](https://docs.google.com/document/d/1vIWcMKwjox1nlbY5rnzH7qrOz8mmmPAWgRt3BW-l2VE/edit?tab=t.0)