Skip to content

feat(nuxi): remember a few facts about people signed in on nuxt.com - #2685

Closed
HugoRCD wants to merge 1 commit into
feat/nuxi-slack-gate-memory-evalsfrom
feat/nuxi-web-memory
Closed

HugoRCD wants to merge 1 commit into
feat/nuxi-slack-gate-memory-evalsfrom
feat/nuxi-web-memory

Conversation

@HugoRCD

@HugoRCD HugoRCD commented Nov 20, 2026

Copy link
Copy Markdown
Member

Written by an AI agent on behalf of @HugoRCD. @HugoRCD has not reviewed it yet.

Stacked on #2684; merge that first, and this PR's diff shrinks to memory only.

Nuxi forgets everything between chats, so a signed-in nuxt.com user repeats their Nuxt version, hosting or main modules in every new conversation. This gives each person signed in on nuxt.com one small private note document (eve's fileMemory()), which Nuxi edits with personal__save_memory and personal__remove_memory and reads back at the start of each turn. Nobody else gets memory: anonymous visitors, Slack (DMs included), Discord and schedules are all off. That keeps notes about one person out of any conversation other people read, and stops anyone in a shared channel from planting a "convention" that shapes Nuxi's answers for everyone.

To try it locally, run pnpm dev:nuxi, sign in, tell Nuxi "I deploy on Cloudflare with Nuxt 4", then open a new chat and ask how to deploy. The preview link will follow once the migration has run on the preview database.

The notes are stored in a new agent_memory table in the nuxt.com database, through two internal routes, instead of a new Blob store. Each document carries the account id with ON DELETE CASCADE, so deleting the account deletes the notes, and data retention deletes documents untouched for 12 months, like chats. Writes are conditional on the version eve read, so two tool calls racing on one document can't overwrite each other. These are checked in data-retention.spec.ts: create-only doesn't overwrite, a stale version conflicts, account deletion cascades, and retention purges old documents. Who gets memory at all is checked in agent-memory-scope.spec.ts.

A recall failure is logged and skipped, so a database hiccup costs the turn its notes, not its answer. It does add one internal HTTP call before the model runs on every signed-in web turn.

Needs migration 0016_agent_memory. Nobody has tried memory against a real deployment or database yet: the tests use a local SQLite file, and the evals run with memory in the process. The existing 7 evals still pass, but none checks what Nuxi chooses to save.

ELI5

When you're logged in on nuxt.com, Nuxi can now jot down a few things about you, like which Nuxt version you use, so you don't have to repeat them next time. Only you see them, they're deleted with your account, and they disappear after a year without use.

One private eve file memory document per nuxt.com account, which Nuxi edits
with save and remove tools: their Nuxt version, hosting or main modules.
Anonymous visitors, Slack, Discord and schedules get none.

Documents live in a new agent_memory table through internal routes, with
optimistic versioning. Each carries its account id, so deleting the account
deletes it, and data retention deletes documents untouched for 12 months.

Amp-Thread-ID: https://ampcode.com/threads/T-01a1f850-034a-7018-8f21-8ff8e18f1355
@HugoRCD
HugoRCD requested a review from atinux as a code owner November 20, 2026 11:28
@vercel

vercel Bot commented Nov 20, 2026

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated
nuxt Building Building Preview Nov 20, 2026 11:28am UTC

Request Review

This branch was successfully deployed

1 active deployment
Preview — fe124eb0 Deployed Nov 20, 2026 by vercel[bot] via lighthouse #10365
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.

1 participant