- The message queue is not persisted across restarts. Queued-but-unsent prompts are dropped; active runs re-attach from session history.
- Role names are not accepted for role configuration; use role IDs.
- The finalization footer shows cost and in/out tokens. Cache reads and
writes are tracked in
/costbut are not rendered in the footer. - Access control is global across guilds.
ACCESS_ROLE_ID,BLOCK_ROLE_ID, andOWNER_ROLE_IDapply to every configured guild; per-guild roles are not supported. A configured guild the bot cannot see is skipped at startup with a warning. - Provider secrets are host-only. Managing
sbx secretfrom Discord is deferred; register credentials on the host. - GitHub access is one shared host token. The optional
GITHUB_TOKEN(GH_TOKENfallback) applies to every project and sandbox; per-user or per-project GitHub identities are not supported, and connecting GitHub from Discord is deferred. - Not yet implemented: per-user command rate limiting, sandbox disk-usage
warnings, and
DATA_DIRcloud-sync detection. KeepDATA_DIRout of synced folders yourself. - Some checks are host-only. The
sbxspike,sbx policy lssemantics, Windows path mapping, and live Discord behavior are exercised on the host, not in the Linux test suite. - The one-line install uses npm and still needs the host.
npx bot-cellyrequires Node 24 and a host withsbxinstalled, logged in, and policy-initialized; it never installs host software. - The bash deny list is defense-in-depth, not the sandbox boundary. Celly statically analyzes shell commands and fails closed on what it cannot prove, but arbitrary wrapper binaries, encoded payloads, and unmodelled shell features can still reach the sandbox. The sandbox is the boundary.
- Discord only renders code fences made of exactly three backticks. Celly normalizes agent output so long replies never emit a longer fence, but it cannot represent a nested fence — a code block whose body itself contains a fence — the way a plain Markdown file can.
- Thread-name edits are rate-limited. Discord allows roughly two thread-name edits per ten minutes per channel, so status updates are coalesced and may lag.
- Sandboxes created before smart thread names do not receive the naming instruction until recreated. Those threads keep their seeded prompt-derived title while still receiving live status prefixes.
- The agent may never name a thread. When no name marker is emitted, the seeded prompt-derived title stands.
Related
- Known issues — confirmed bugs and workarounds.
- Commands — the current surface and what is deferred.
- Configuration — the variables behind these limits.