MemSlides: A Hierarchical Memory Driven Agent Framework for Personalized Slide Generation with Multi-turn Local Revision
Abstract
MemSlides presents a hierarchical memory framework for personalized presentation agents that separates long-term user profiles, working memory for session constraints, and tool memory for reusable execution experiences to enable stable personalization and reliable local edits across multi-turn revisions.
Personalized presentation generation requires more than conditioning on a current prompt or template: agents must preserve stable user preferences across tasks, retain newly introduced preferences and constraints during multi-turn revision, and carry out local edits reliably. We propose MemSlides, a hierarchical memory framework for personalized presentation agents that separates long-term memory from working memory and further divides long-term memory into user profile memory and tool memory. User profile memory stores intent-conditioned profiles for round-0 personalization, working memory carries active preferences and session constraints across revision rounds, and tool memory stores reusable execution experience for reliable localized editing. MemSlides pairs this memory design with scoped slide-local revision, so targeted updates act on the smallest affected region instead of repeatedly regenerating the full deck. In controlled experiments, user profile memory improves persona-alignment judgments on a multi-persona, multi-intent profile bank, tool-memory injection improves closed-loop modify behavior in diagnostic matched-pair settings, and qualitative cases illustrate working memory's ability to carryover preferences. Taken together, these results suggest that effective personalization in presentation authoring depends on separating persistent user profiles, session-level working memory, and reusable execution experience across generation and localized revision.
Community
Thanks for checking out MemSlides!
MemSlides is a hierarchical memory-driven agent framework for personalized slide generation and multi-turn local revision.
Links:
- Project page: https://memslides.github.io/
- Code: https://github.com/huohua325/Memslides
- Demo Website: https://memslides.com/
- arXiv: https://arxiv.org/abs/2606.17162
The main idea is to separate persistent user profile memory, session-level working memory, and reusable tool memory, so the slide generation agent can personalize initial decks and perform reliable localized revisions across turns.
We introduce MemSlides, a memory-driven Slides Agent for personalized slide generation and multi-turn local revision.
The main question is: can a Slides Agent learn user preferences from multi-turn interactions, preserve session-level constraints, and revise only the intended parts of a deck?
MemSlides organizes memory from two perspectives:
- temporal scope: long-term memory vs. working memory
- functional role: preference memory vs. tool memory
This lets the agent separate persistent user preferences, current-session constraints, and reusable tool-execution experience, instead of simply appending all history into the prompt.
We also study localized revision, where a user request is mapped to the smallest effective slide region to reduce unintended drift in the rest of the deck.
Code, project page, and demo are linked below. Feedback is very welcome!
Neat approach to slide generation. Most presentation tools struggle with maintaining consistency over multiple edits, so separating the memory into user profiles, working memory, and tool execution sounds like a much more stable way to handle revisions than just regenerating everything from scratch.
I am curious, how does the system decide which parts of the deck are considered the smallest affected region during a local edit? Does it rely on the tool memory to map specific prompts to slide components?
I made a podcast on it with ResearchPod, it makes it easy to get the key concepts on the go:
https://researchpod.app/episode/afdb2aa6-91fc-4fbb-abf4-ce2fcf22d6ae
Thanks a lot for the thoughtful comment, and for making the ResearchPod episode!
In MemSlides, a revision is not handled as full-deck regeneration by default. We first infer whether the feedback points to a component, a slide, a small group of slides, or a deck-level change, then use the current deck state and memory to keep the edit as local as possible while preserving consistency.
Tool memory is one part of this process: it records useful context from tool use and helps connect revision intent with prior operations, assets, evidence, and constraints. But the boundary is not decided by tool memory alone; it also depends on the slide structure, working memory, and post-edit validation.
Thanks again for the podcast — really appreciate it!
Get this paper in your agent:
hf papers read 2606.17162 Don't have the latest CLI?
curl -LsSf https://hf.co/cli/install.sh | bash Models citing this paper 0
No model linking this paper
Datasets citing this paper 0
No dataset linking this paper
Spaces citing this paper 1
Collections including this paper 0
No Collection including this paper