With the desktop app
If you already use the app, it checks your deployed version on launch and offers the upgrade automatically. Accept the prompt, sign in to Cloudflare when asked, done.
The app can upgrade any Second Brain on a .workers.dev address, however it was set up. If you do not have the app yet:
Download it and open it.
Choose Already have a Second Brain? and enter your brain's address and password. This only connects the app, not your Cloudflare account.
The app notices the Worker is behind the version it ships with and offers to update it. Accept, sign in to Cloudflare once, and the app redeploys the Worker in place.
If your brain is behind a custom domain rather than .workers.dev, the app cannot auto-locate the account; use the git methods instead.
With git
One-click deployers: the button created a standalone copy of the repository in your GitHub account. Add the Second Brain repository as an upstream remote, merge, and push; the push triggers Cloudflare's connected build, which redeploys the Worker.
If you deploy from your own machine, it is shorter:
git pull upstream main
npm install
npm run deployIf you used the desktop app to update since, the app updated the Worker directly, so this repository copy stays old. Harmless on its own, but pushing from it later makes Cloudflare rebuild from the old copy and roll the Worker back. Keep this repository synced too if you use it.
What changes, and what your data does
The new Worker replaces the old one; that is the whole change. Your memories, password and connected tools are preserved, and the schema catches up on the first request after the deploy: new columns are added, anything already present is skipped. There is no maintenance window, no command to run, and no new variables unless a release note says otherwise.
Going from v2 to v3 adds one step: open the dashboard once as the owner after upgrading, so the migration files your existing memories into your personal layer.
What you will see: Workers and Pages, your Worker, Deployments shows a recent timestamp. If something looks off, give it one request first, because that is when the migration runs, then check the release notes.
Then send a test recall for something you saved before the update:
RecalledA memory saved before the update, back in a fresh answer.