When you should update

Update now if:

you are far behind and missing features you actually need
your current build has a bug already fixed upstream
you are setting up a fresh install and want the current stable baseline

Wait if:

your current setup is stable and you do not need anything new
you rely on extensions that may lag behind
you do not have time to troubleshoot after updating

Common update mistakes

Confusing branch updates with tagged releases. “Latest commit” and “latest stable version” are not the same thing.
Ignoring Node.js requirements. The official docs still point users toward modern Node.js versions, with Node 18+ as the baseline in setup guidance.
Updating before backing up important data. Characters, presets, and custom files matter more than the app shell.
Blaming the version for backend issues. Sometimes the front end is fine and the real issue is API config.

Should NSFW or ERP users stay on release?

Question

When you should update

Update now if:

you are far behind and missing features you actually need
  your current build has a bug already fixed upstream
  you are setting up a fresh install and want the current stable baseline

Wait if:

your current setup is stable and you do not need anything new
  you rely on extensions that may lag behind
  you do not have time to troubleshoot after updating

Common update mistakes

Confusing branch updates with tagged releases. “Latest commit” and “latest stable version” are not the same thing.
  Ignoring Node.js requirements. The official docs still point users toward modern Node.js versions, with Node 18+ as the baseline in setup guidance.
  Updating before backing up important data. Characters, presets, and custom files matter more than the app shell.
  Blaming the version for backend issues. Sometimes the front end is fine and the real issue is API config.

Should NSFW or ERP users stay on release?

Accepted Answer

Usually yes. ERP users care about consistency. If you have a tuned stack with characters, lorebooks, author’s notes, and a backend that behaves the way you want, surprise churn is not helpful. That is why the official recommendation toward the release branch is still the sensible default for most NSFW users in 2026.