Skip to content

✨ feat(memory): support to delete all memory entries#13161

Merged
nekomeowww merged 2 commits into
canaryfrom
neko/dev/memory-user-memory-delete-all
Mar 20, 2026
Merged

✨ feat(memory): support to delete all memory entries#13161
nekomeowww merged 2 commits into
canaryfrom
neko/dev/memory-user-memory-delete-all

Conversation

@nekomeowww

Copy link
Copy Markdown
Member

πŸ’» Change Type

  • ✨ feat
  • πŸ› fix
  • ♻️ refactor
  • πŸ’„ style
  • πŸ‘· build
  • ⚑️ perf
  • βœ… test
  • πŸ“ docs
  • πŸ”¨ chore

πŸ”— Related Issue

πŸ”€ Description of Change

πŸ§ͺ How to Test

  • Tested locally
  • Added/updated tests
  • No tests needed

πŸ“Έ Screenshots / Videos

Before After
... ...

πŸ“ Additional Information

@vercel

vercel Bot commented Mar 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
lobehub Ready Ready Preview, Comment Mar 20, 2026 3:11pm

Request Review

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We've reviewed this pull request using the Sourcery rules engine

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

πŸ’‘ Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5f6d0f5372

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with πŸ‘.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +61 to +65
Object.assign(draft, activityInitialState);
Object.assign(draft, contextInitialState);
Object.assign(draft, experienceInitialState);
Object.assign(draft, identityInitialState);
Object.assign(draft, preferenceInitialState);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Reset topic memory cache when purging all memories

This purge path resets the list/detail slices but does not clear topicMemoriesMap, which is still used by resolveTopicMemories in src/services/chat/mecha/memoryManager.ts to inject topic memories into chat context. As a result, topics that were opened before purge can continue using stale deleted memories until a full reload or explicit per-topic cache clear, so the β€œpurge all” action is not actually effective for active chat sessions.

Useful? React with πŸ‘Β / πŸ‘Ž.

Comment on lines +101 to +103
deleteAll: userMemoryProcedure.mutation(async ({ ctx }) => {
await ctx.userMemoryModel.deleteAll();

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Purge persona documents in deleteAll mutation

The new deleteAll endpoint only calls ctx.userMemoryModel.deleteAll(), but persona data is served separately via UserPersonaModel.getLatestPersonaDocument() and is not removed here. In practice, useFetchPersona (initialized globally) can repopulate an old persona after purge (for example on reload/focus), so users can still see memory-derived profile text after β€œPurge All,” which violates the destructive action’s expected behavior.

Useful? React with πŸ‘Β / πŸ‘Ž.

@lobehubbot

Copy link
Copy Markdown
Member

@ONLY-yours - This PR adds support to delete all memory entries, touching memory routes, backend routers, store actions, and services. Please take a look.

@codecov

codecov Bot commented Mar 20, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 17.80822% with 60 lines in your changes missing coverage. Please review.
βœ… Project coverage is 74.56%. Comparing base (04f963d) to head (2864509).
⚠️ Report is 24 commits behind head on canary.

Additional details and impacted files
@@            Coverage Diff             @@
##           canary   #13161      +/-   ##
==========================================
- Coverage   74.60%   74.56%   -0.04%     
==========================================
  Files        1514     1514              
  Lines      124476   124548      +72     
  Branches    13790    13791       +1     
==========================================
+ Hits        92862    92874      +12     
- Misses      31503    31563      +60     
  Partials      111      111              
Flag Coverage Ξ”
app 67.64% <17.80%> (-0.05%) ⬇️
database 97.89% <ΓΈ> (ΓΈ)
packages/agent-runtime 89.60% <ΓΈ> (ΓΈ)
packages/context-engine 83.53% <ΓΈ> (ΓΈ)
packages/conversation-flow 92.37% <ΓΈ> (ΓΈ)
packages/file-loaders 87.02% <ΓΈ> (ΓΈ)
packages/memory-user-memory 66.68% <ΓΈ> (ΓΈ)
packages/model-bank 99.84% <ΓΈ> (ΓΈ)
packages/model-runtime 84.72% <ΓΈ> (ΓΈ)
packages/prompts 74.60% <ΓΈ> (ΓΈ)
packages/python-interpreter 92.90% <ΓΈ> (ΓΈ)
packages/ssrf-safe-fetch 0.00% <ΓΈ> (ΓΈ)
packages/utils 90.09% <ΓΈ> (ΓΈ)
packages/web-crawler 88.81% <ΓΈ> (ΓΈ)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Ξ”
Store 66.11% <10.76%> (-0.15%) ⬇️
Services 49.89% <33.33%> (-0.02%) ⬇️
Server 69.89% <100.00%> (+<0.01%) ⬆️
Libs 42.20% <ΓΈ> (ΓΈ)
Utils 91.09% <ΓΈ> (ΓΈ)
πŸš€ New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • πŸ“¦ JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@nekomeowww nekomeowww merged commit 48c3f0c into canary Mar 20, 2026
32 of 34 checks passed
@nekomeowww nekomeowww deleted the neko/dev/memory-user-memory-delete-all branch March 20, 2026 15:32
@lobehubbot

Copy link
Copy Markdown
Member

❀️ Great PR @nekomeowww ❀️

The growth of project is inseparable from user feedback and contribution, thanks for your contribution! If you are interesting with the lobehub developer community, please join our discord and then dm @arvinxx or @canisminor1990. They will invite you to our private developer channel. We are talking about the lobe-chat development or sharing ai newsletter around the world.

ONLY-yours added a commit that referenced this pull request Mar 27, 2026
# πŸš€ release: 20260326

This release includes **91 commits**. Key updates are below.


- **Agent can now execute background tasks** β€” Agents can perform
long-running operations without blocking your conversation.
[#13289](#13289)
- **Better error messages** β€” Redesigned error UI across chat and image
generation with clearer explanations and recovery options.
[#13302](#13302)
- **Smoother topic switching** β€” No more full page reloads when
switching topics while an agent is responding.
[#13309](#13309)
- **Faster image uploads** β€” Large images are now automatically
compressed to 1920px before upload, reducing wait times.
[#13224](#13224)
- **Improved knowledge base** β€” Documents are now properly parsed before
chunking, improving retrieval accuracy.
[#13221](#13221)

### Bot Platform

- **WeChat Bot support** β€” You can now connect LobeChat to WeChat, in
addition to Discord.
[#13191](#13191)
- **Richer bot responses** β€” Bots now support custom markdown rendering
and context injection.
[#13294](#13294)
- **New bot commands** β€” Added `/new` to start fresh conversations and
`/stop` to halt generation.
[#13194](#13194)
- **Discord stability fixes** β€” Fixed thread creation issues and Redis
connection drops.
[#13228](#13228)
[#13205](#13205)

### Models & Providers

- **GLM-5** is now available in the LobeHub model list.
[#13189](#13189)
- **Coding Plan providers** β€” Added support for code planning assistant
providers. [#13203](#13203)
- **Tencent Hunyuan 3.0 ImageGen** β€” New image generation model from
Tencent. [#13166](#13166)
- **Gemini content handling** β€” Better handling when Gemini blocks
content due to safety filters.
[#13270](#13270)
- **Claude token limits fixed** β€” Corrected max window tokens for
Anthropic Claude models.
[#13206](#13206)

### Skills & Tools

- **Auto credential injection** β€” Skills can now automatically request
and use required credentials.
[#13124](#13124)
- **Smarter tool permissions** β€” Built-in tools skip confirmation for
safe paths like `/tmp`.
[#13232](#13232)
- **Model switcher improvements** β€” Quick access to provider settings
and visual highlight for default model.
[#13220](#13220)

### Memory

- **Bulk delete memories** β€” You can now delete all memory entries at
once. [#13161](#13161)
- **Per-agent memory control** β€” Memory injection now respects
individual agent settings.
[#13265](#13265)

### Desktop App

- **Gateway connection** β€” Desktop app can now connect to LobeHub
Gateway for enhanced features.
[#13234](#13234)
- **Connection status indicator** β€” See gateway connection status in the
titlebar. [#13260](#13260)
- **Settings persistence** β€” Gateway toggle state now persists across
app restarts. [#13300](#13300)

### CLI

- **API key authentication** β€” CLI now supports API key auth for
programmatic access.
[#13190](#13190)
- **Shell completion** β€” Tab completion for bash/zsh/fish shells.
[#13164](#13164)
- **Man pages** β€” Built-in manual pages for CLI commands.
[#13200](#13200)

### Security

- **XSS protection** β€” Sanitized search result image titles to prevent
script injection.
[#13303](#13303)
- **Workflow hardening** β€” Fixed potential shell injection in release
automation. [#13319](#13319)
- **Dependency update** β€” Updated nodemailer to address security
advisory. [#13326](#13326)

### Bug Fixes

- Fixed skill page not redirecting correctly after import.
[#13255](#13255)
[#13261](#13261)
- Fixed token counting in group chats.
[#13247](#13247)
- Fixed editor not resetting when switching to empty pages.
[#13229](#13229)
- Fixed manual tool toggle not working.
[#13218](#13218)
- Fixed Search1API response parsing.
[#13207](#13207)
[#13208](#13208)
- Fixed mobile topic menus rendering issues.
[#12477](#12477)
- Fixed history count calculation for accurate context.
[#13051](#13051)
- Added missing Turkish translations.
[#13196](#13196)

### Credits

Huge thanks to these contributors:

@bakiburakogun @hardy-one @Zhouguanyang @sxjeru @hezhijie0327 @arvinxx
@cy948 @CanisMinor @Innei @lijian @lobehubbot @neko @rdmclin2
@rivertwilight @tjx666
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants