# User guide How to use slackerbot from Slack. ## Your container | Where you talk to the bot | Container | Who can use it | |---|---|---| | DM with the bot | `u-` | Only you | | Channel, private channel or group DM (@mention the bot) | `c-` | Anyone in that channel | In channels, @mention the bot every time, including in threads. The bot doesn't see plain replies. Each message reaches the agent with the sender's name in front (e.g. `Alice: try the other branch`), so the agent knows who's asking. ## Talking to the agent 1. Send a message. If the container is stopped, the bot starts it, and if it doesn't exist yet, the bot creates it. Your home folder (`/root`) is kept between starts. 2. A new top-level message starts a **new session**, and the reply goes in a thread. 3. **Reply in that thread to continue the same session**, even days later. `sessions` lists past ones. 4. The answer streams in as the agent works. Tool calls show up as 🔧 lines. 5. Messages in one thread run one at a time. If two people post at once, the second waits its turn. 6. Containers unused for longer than their idle limit are stopped (default 6 hours, see `keep`). Files are kept, and the bot posts to say it stopped the container. Other replies you may get: - **"maxed out":** no node has room right now. Try again later. - **"being moved, try again in a moment":** a move is in progress. - **"dead slave":** the node your container lives on is offline. Pick **Create new container** to get a fresh one on a healthy node (old sessions won't carry over), or **Wait** to get a message when the node is back. ## Commands Send these as a **new message**, not in a thread. `move` is the one exception, and also works in a thread. | Command | What it does | |---|---| | `help` | Shows the command list | | `status` | State, size, time unused and idle limit, with **Stop** and **Scale up** buttons | | `sessions` | Past sessions with links. Open one and reply in its thread to continue | | `stop` | Shuts the container down. Files are kept | | `scale up` / `scale down` | Doubles or halves RAM and CPU | | `scale 8G 4cpu` | Sets an exact size | | `scale +2G` / `scale -1cpu` / `scale 512M +0.5cpu` | `+` or `-` changes by that much. Memory and CPU can be mixed or left out | | `keep 24h` (or `3d`, `1d12h`, `2w`, `5 hours`) | Stops the container after that long unused | | `keep indefinite` (or `forever`) | Never stops it for being unused. Use `stop` when done | | `keep default` | Back to the server's default | | `keep` | Shows the current idle limit | | `storage` | Shows home folder usage, guaranteed space and max | | `storage 20G` / `storage +5G` / `storage -2G` | Sets or changes the max (the cap) | | `storage min 8G` / `storage min 8G max 20G` | Sets the guaranteed space, or both | | `nodes` | Every node with what's free on it, and where this container runs | | `move ` / `move to ` / `migrate ` | Moves this container to that node | | `move` / `move auto` | Moves it to whichever other node keeps resources most even | | `permissions` | Who may change what here | If what follows `scale`, `keep`, `storage` or `move` doesn't look like a size, a time or a node (e.g. "keep the tests passing"), the message goes to the agent instead. **Scale:** memory takes `G`/`GB` or `M`/`MB`, and CPU takes `cpu`/`cores` (fractions are fine). The minimum is 256 MB and 0.25 CPU, and the server sets a maximum. A running container changes size right away, and a stopped one gets the new size when it next starts. Shrinking memory below what's in use may stop programs inside. **Keep:** the minimum is 10 minutes. The server can cap the maximum or turn off `keep indefinite`. Setting `keep` restarts the countdown. **Storage:** sizes take `M`, `G` or `T`. Both numbers are at least 512 MB, the guarantee can't be more than the max, and the max can't go below what's already used. If the drive can't promise a bigger guarantee, the bot refuses it. You can raise the max even when the caps on that drive already add up to more than it holds. The bot flags the drive as **overbooked** but still makes the change. **Moves:** each move gets its own top-level message saying who started it, with progress in its thread and ✅ or ❌ when done. A running container keeps running during the bulk copy, and is only stopped briefly for a final sync. Sessions come along. When a container's node is too full to restart it, the bot moves it automatically. ## Permissions Anyone can talk to the agent and use `status`, `sessions`, `nodes`, `permissions` and `stop`, and can view settings with a bare `keep` or `storage`. **Changing** a container needs a permission: | Permission | Covers | |---|---| | `scale` | `scale …` and the **Scale up** button | | `storage` | `storage `, `storage min …` | | `move` | `move …` and **Create new container** | | `keep` | `keep