In separate terminals:

bin/bot    # the gateway connection
bin/jobs   # background jobs (reminder delivery)

Guild commands register per-server automatically — no env var needed. If you work on Scam Image Detection, you'll also need the OCR sidecar: docker compose --profile ocr up -d ocr.

AI-assisted development

If you want to use coding agents but keep them isolated from the rest of your machine, the compose file includes a sandbox: the dev container (built from Dockerfile.dev) ships Ruby, the GitHub CLI, Claude Code, and Copilot CLI as an unprivileged user, with the repo mounted at /app. Secrets (.env, .env.deploy) are masked inside the container, and the compose file and Dockerfiles are mounted read-only, so the agent can't read your credentials or loosen its own sandbox.

Agent state lives on the host under ~/.ai-sandbox so it survives container rebuilds. One-time setup:

mkdir -p ~/.ai-sandbox/shrkbot/{claude,local-state,local-share}
touch ~/.ai-sandbox/shrkbot/claude.json

Then:

• put the git identity the agent should commit with into ~/.ai-sandbox/gitconfig-shrkbot,
• optionally put a GitHub PAT into ~/.ai-sandbox/github-pat-private (used for pushes; scope it to this repo),
• make sure gh auth login has been run on the host — ~/.config/gh is mounted in.

Start it with:

docker compose run --rm dev bash

and run your agent from there. It talks to the same compose Postgres as the other services.

Contributing

Found a bug, or missing a feature? Open an issue, or send an email to [email protected] — both are read. If you'd like to add something yourself, fork the project and open a PR; the how-tos in docs/ will get you started. For bigger changes it's worth opening an issue first so we can talk it through before you put the work in.

Deployment

Deploys to a single box via Kamal 2 — see docs/running/deployment.md.

License

MIT