1.6 KiB
1.6 KiB
Slackerbot
Talk to the bot in Slack, and your message goes to a goose agent inside a systemd-nspawn container. The agent's reply streams back over ACP into a Slack thread. Replying in that thread continues the same session. One container serves all different sessions for a channel.
- One container per DM or channel. DMs get a private container, and channels share one.
- Access Controls different users may given privillege access in certain channels, access is delegated by "manager users" via configuration or with the bot.
- Persistent home folder.
/rootlives on a btrfs subvolume with a guaranteed size and a cap. Everything else is rebuilt on each start. - Managed from Slack. Users can
scale,stop, set idle timeouts withkeep, resizestorage, andmovecontainers between nodes. Changes are limited by per-channel permissions. - Scalable A master runs the Slack bot, and slaves add capacity. New containers go wherever CPU, RAM and storage stay most even, and live migration moves a running container with only a short pause.
Docs
| File | For |
|---|---|
| INSTALLATION.md | Setting up the Slack app, the host and extra nodes |
| USERGUIDE.md | Slack commands and how permissions work |
| ARCHITECTURE.md | How the system and the code are put together |
| AGENTS.md | Rules for changing the code: tests, layout, style |