running and cancel all commands

This commit is contained in:
ari committed 2026-11-01 20:29:39 -05:00
1 parent 917a361370
commit af249326e8
7 files changed
+145 -6

No files matched your search

+5 -3
View File
@@ -19,14 +19,14 @@ In DMs the bot reads every message. You can also chat with it in Slack's assista
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. Your message gets 👀 while the agent works, then ✅ when it's done or ⚠️ if something went wrong.
5. While the agent works, its reply shows what it's doing (thinking, running a tool, writing the reply), when the agent last sent anything, and a **Cancel** button. They go away when the reply is done. To stop a reply part-way, press **Cancel**, or react to your message or the bot's reply with ❌ (`:x:`) or 🛑 (`:octagonal_sign:`). The reply ends with _(cancelled)_, and the session carries on with your next message.
5. While the agent works, its reply shows what it's doing (thinking, running a tool, writing the reply), when the agent last sent anything, and a **Cancel** button. They go away when the reply is done. To stop a reply part-way, press **Cancel**, or react to your message or the bot's reply with ❌ (`:x:`) or 🛑 (`:octagonal_sign:`). The reply ends with _(cancelled)_, and the session carries on with your next message. `running` lists every reply in progress in the channel, and `cancel all` cancels them all at once.
6. Messages in one thread run one at a time. If two people post at once, the second waits its turn.
7. 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.
8. **Container updates have their own thread.** Each time a container starts, the bot posts a top-level "Starting container" message in the channel (or your DM) and pins it. Every step goes in that message's thread as its own reply, saying what the bot is waiting for: placing it on a node, creating the home folder and launching it, and waiting for the agent. A last reply says the container is up. Your own thread only gets one message with a link to it. Stopping a container (`stop`, the **Stop** button or the idle limit) is reported in the same thread, ending with a reply that it's down. The pin is replaced the next time the container starts.
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.
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. When it runs `cancel all`, its own reply carries on.
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.
@@ -59,6 +59,8 @@ Send these as a **new message**, not in a thread. `move` and `listen` are the ex
| `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 |
| `running` | Replies the agent is working on in this channel right now, with links, who asked and how long ago they started |
| `cancel all` | Cancels every reply in progress in this channel, like pressing **Cancel** on each. Sessions are kept. Replies still starting the container are left |
| `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 |
@@ -88,7 +90,7 @@ If what follows `scale`, `keep`, `storage` or `move` doesn't look like a size, a
## 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`.
Anyone can talk to the agent and use `status`, `sessions`, `running`, `cancel all`, `nodes`, `permissions` and `stop`, and can view settings with a bare `keep` or `storage`.
**Changing** a container needs a permission: