Share one crew across the install, keep user memory per user

Bots, workspaces and computers now belong to the install. Users reach
workers only through bot_users (assigned by a super admin or admin) and
workspace_users; the coordinator and main computer are one per install,
and only the super admin sees the coordinator. Conversations are per
user (bot_sessions.user_id), jobs run for the session's user, and live
updates go only to who should see them.

A bot's core memory is now general knowledge shared by every user it
works for; what it learns about a user lives in bot_user_memories.

One-off scripts move existing installs over: move-bot-memory-to-owners
(run first), then share-crew.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
2026-10-19 11:37:14 +01:00
co-authored by Claude Opus 5.5
parent 4dd34ed251
commit e45d54d30b
133 changed files with 1854 additions and 436 deletions
+6
View File
@@ -26,6 +26,12 @@ export const SaveUserRequestSchema = z
* A new profile photo as a base64 data URL; left out keeps theirs.
*/
image: z.string().startsWith("data:image/", "Pick an image").nullish(),
/**
* Every worker assigned to them and every workspace they're in,
* replacing the old lists. Left out: unchanged.
*/
bot_ids: z.array(z.coerce.number().int().positive()).optional(),
workspace_ids: z.array(z.coerce.number().int().positive()).optional(),
})
.refine((data) => data.password == data.confirm_password, {
message: "The passwords don't match",