Skip to main content
This guide covers running Celly as a long-lived service on a Linux host with systemd --user. As on Windows, the bot must run as the user who owns the sbx daemon and its credentials.

1. Host bootstrap

  1. Install sbx (Docker Sandboxes), then log in and initialize the network policy:
    Celly targets sbx >= 0.45.0.
  2. Install Node 24 with fnm (or nvm):
  3. Register provider credentials used by the sandboxed agent (see Providers):

2. Install and configure

The wizard writes ~/.bot-celly/.env. The required values are documented in Configuration.

3. systemd user service

Install globally first with npm install -g bot-celly. Create ~/.config/systemd/user/celly.service:
bash -lc loads your shell profile so fnm/nvm and sbx are on PATH; exec keeps the CLI as the main process so SIGTERM reaches Celly’s shutdown handler. Enable it and keep it running after logout:

4. Verifying a deployment

  • sbx diagnose reports a healthy daemon and authentication.
  • systemctl --user status celly is active (running).
  • curl -s http://127.0.0.1:4560/api/health returns {"ok":true,...}.
  • ~/.bot-celly/data/bot.log shows the preflight passing and the Discord client logging in.

5. Troubleshooting

6. Admin, backups, and paths

  • The loopback admin page, log rotation, SQLite backups, and restore are covered in Operations.
  • The sensitive-path denylist and PROJECTS_ROOT containment are covered in Configuration.
  • Known limitations are listed in Limitations.