resume active sessions
This commit is contained in:
1 parent
9e94c05fb6
commit
917a361370
19 files changed
+871
-42
No files matched your search
+24
-21
@@ -27,7 +27,8 @@ In DMs the bot reads every message. You can also chat with it in Slack's assista
|
||||
9. **Attach files** to your message (images, logs, zips) and they're copied into the container at `/root/slack-uploads/<message time>/<name>`, and the agent is told where. A message with files always goes to the agent, never to a command. Files over the server's size limit (default 100 MB) are left out, and the home folder's max size still applies.
|
||||
10. **The agent can send you files.** It has a `send_file` tool, and the files land in the thread when its reply ends, where Slack previews images, video and PDFs. At most 5 files per reply, each under the server's size limit.
|
||||
11. **The agent can run the commands below for you**, so you can ask it things like "give yourself 8G" or "keep running over the weekend". It runs them as you, the sender of the message it's answering, with your permissions. Anything that changes the container is posted in the thread as ":robot_face: The agent ran `scale 8G` for Alice", with the bot's answer. If the agent stops the container, it waits until the reply ends. Its moves get their own thread like any other move. It can do everything a command can except `help`, and it can't press buttons.
|
||||
12. **System updates ask first.** When the server gets a new container system (new tools, for example) while yours is running, the bot asks once, under the agent's next reply, whether to restart onto it. **Restart now** restarts the container right away (it waits if the agent is still replying), and **Later** leaves it alone. Either way, `/root` and your sessions are kept, and the update also applies the next time the container starts for any reason.
|
||||
12. **Restarts don't lose your reply.** If slackerbot restarts while the agent is working on your message, the reply ends with a note that it's restarting. When it's back, it posts ":arrows_counterclockwise: slackerbot restarted part-way through this reply, so I'm picking it back up" in the thread, and the agent carries on where it stopped (or starts, if it hadn't got your message yet). After an hour, or after 3 restarts in a row, it asks you to send the message again instead. Messages sent while slackerbot is down aren't seen, so send those again.
|
||||
13. **System updates ask first.** When the server gets a new container system (new tools, for example) while yours is running, the bot asks once, under the agent's next reply, whether to restart onto it. **Restart now** restarts the container right away (it waits if the agent is still replying), and **Later** leaves it alone. Either way, `/root` and your sessions are kept, and the update also applies the next time the container starts for any reason.
|
||||
|
||||
Other replies you may get:
|
||||
|
||||
@@ -53,26 +54,27 @@ Anyone in the channel can change these. In an `all-messages` thread, `move` stil
|
||||
|
||||
Send these as a **new message**, not in a thread. `move` and `listen` are the exceptions, and also work in a thread. In the assistant pane, the first message of a chat counts as new.
|
||||
|
||||
| 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. Flags nodes running a different version than the master |
|
||||
| `move <node>` / `move to <node>` / `migrate <node>` | 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 |
|
||||
| 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. Flags nodes running a different version than the master |
|
||||
| `move <node>` / `move to <node>` / `migrate <node>` | 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 |
|
||||
| `in-flight` / `in-flight all` | Super users only. For debugging: shows the replies slackerbot would pick back up after a restart, here or in every channel. Only you see the answer |
|
||||
|
||||
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.
|
||||
|
||||
@@ -106,6 +108,7 @@ Roughly how it fits together:
|
||||
- **User managers** can change everything: any channel's list, the default list, DM switches and the manager list. **Channel managers** (`manage`) can only edit their own channel's list. There's always at least one user manager.
|
||||
- If you lack a permission, the bot answers with :lock: and names who has it, without tagging them.
|
||||
- Automatic moves don't need a permission.
|
||||
- `in-flight` shows other people's messages, so it needs you to be a **super user** (anyone on the list that applies here, with any permission) or a user manager. `in-flight all` needs you on the default list, or a user manager. DMs count the default list.
|
||||
|
||||
| Command | Who | What it does |
|
||||
| ------------------------------------------------------------- | ---------------------- | ---------------------------------------------------- |
|
||||
|
||||
Reference in new issue
Block a user