8c83a3316a3af015e12c1c7fdf03f3cfcd2a7e3f
Check resolved symlinks in the file path but compared it to s.Home as given, so a home reached through a symlink rejected its own files. Seen when tools_test ran on NativeLink, whose work dir is under the /var/lib/nativelink -> private/nativelink symlink. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0119iKoN3fSvRGUAYHupPW4U
Slackerbot
A Slack bot that gives every DM and every channel its own AI coding agent, running in its own NixOS container.
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 into a Slack thread. Replying in that thread continues the same session.
- One container per DM or channel. DMs get a private container, and channels share one.
- 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. - One or more machines. 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 |
Quick start
git clone https://gitea.skyg.ca/ari/slacker-bot.git && cd slacker-bot
nix develop # or let direnv load it from .envrc
cd slackerbot && go test ./...
nix build .#slackerbot # the bot
nix build .#agent # the NixOS system each container boots
Languages
Go
95.3%
Starlark
3.2%
Nix
1.4%