sbx (Docker Sandboxes) microVM on your host, and you drive it from a
Discord channel and thread: start a session from your phone, watch it work, and
pick it back up later.
The model is small enough to hold in your head:
- Channel = project. One
sbxsandbox and one host directory. - Thread = session. One OpenCode conversation.
- The bot runs on the
sbxhost, because only the host can invoke thesbxCLI. It supervises one long-livedsbx exec ... opencode servechild per project and talks to it over the sandbox’s published loopback port using the@opencode-ai/sdk.
celly-<slug> and the default
Discord category is Forge.
Topology
Provider credentials are injected bysbx secret at the host proxy. They are
never stored in the bot or the repository.
Start here
Quickstart
Bootstrap the host, install Celly, and run your first prompt in a few
minutes.
Commands
The full command surface, access rules, and what is deferred.
What you get
- Per-project sandbox isolation. Every project owns a microVM; the host filesystem outside the mounted project directory is unreachable. See Security.
- Streaming replies throttled into a single live message, with fence-aware chunking.
- Approvals.
auto,buttons, orplanper channel, with Discord permission buttons and interactive agent questions. See Approvals. - Sessions everywhere.
/resume,/fork,/undo//redo,/compact,/diff, and terminal attach all share one OpenCode session. - Per-session git worktrees under
<project>/.celly/worktrees, opt-in per project or by default withWORKTREE_DEFAULT. - Cost tracking and budgets with
/costand/budget. - Multi-guild deployment and a loopback admin page.