Forum

This seems like a SillyTavern usage issue instead of a Zeabur deployment issue. I have asked AI and I am passing the instruction down for you:

The core problem is that SillyTavern's multi-user mode gives each user their own isolated data directory. When you install a third-party extension, it gets registered in your user's settings.json under the extensions list — other users don't inherit that.

What Should Work

Content Scaffolding is exactly designed for this. You need to:

1. Install the extensions on one account first (the admin/template account)
2. Find the relevant files in that user's data directory — specifically the extension settings in settings.json and any extension-specific data files
3. Set up /default/scaffold/index.json to copy those files to every new user on creation

The scaffold index.json format looks something like:

[
 {
 "filename": "settings.json",
 "type": "settings"
 }
]

But there's a catch — third-party extensions are cloned via git into the server's extension directory, not into user data. The code lives server-side (shared), while the activation/settings are per-user.

So the Real Fix Is Two Parts

1. Extension code on the server — use a custom Docker image or startup script to ensure the extension repos are cloned into the server's third-party extensions folder (this is the ephemeral filesystem issue you hit)

2. Extension activation per user — use scaffolding to provide a settings.json that has those extensions already enabled, so new users don't have to manually activate them

This post has been inactive for a while. We will be closing it in 2 days if there is no new activity.