sbx is per-user and only the host can execute the sbx
binary.
Prerequisites
- Windows 11 host (or macOS/Linux where
sbxruns). - Node 24.x exactly (pinned by
enginesand.nvmrc). - Docker Sandboxes
sbx>= 0.45 installed and logged in. - A Docker login and an initialized network policy.
- A Discord application with a bot token (setup verifies it, links you to the Message Content intent toggle, prints an invite URL, and can list your guilds).
- An OpenCode provider credential registered through
sbx secret.
Setup
1
Bootstrap the host (once)
Run these once, in order, as the user who will own the bot.
sbx injects provider credentials at the proxy. Pin and record the version
with sbx version. See Providers for built-in and
custom secret setup.2
Install and configure
~/.bot-celly/.env. PROJECTS_ROOT defaults to ~/Celly/projects
(created on boot). Setup also works offline: when Discord is unreachable it
falls back to entering the token and guild IDs by hand. Re-run the command to
start again; npx bot-celly doctor checks the host without starting.On boot the bot performs a preflight (sbx version, policy check,
single-instance lock) and fails fast with an actionable message. Logs are
written to ~/.bot-celly/data/bot.log.From source
From source
./data/bot.log.3
Add a project and send a message
In your Discord guild, create a project from a directory under
The bot runs the create saga (sandbox, bootstrap, serve child, health,
policy) and creates a
PROJECTS_ROOT:#my-app channel under the Forge category.Then post a plain message in that channel. Celly opens a thread, creates an
OpenCode session, and streams the reply. Reply in the thread to continue the
same session.Next steps
- Configuration — every environment variable and its default.
- Providers — credentials, custom hosts, and model selection.
- Terminal attach — drive the same sessions from a shell.
- Deployment — run Celly at logon with Task Scheduler.
- Operations — the admin page, logs, and backups.