making use of the extended perms and added future work

This commit is contained in:
ari committed 2026-11-01 13:55:25 -05:00
1 parent 296e465f48
commit 22fd8fbce8
19 files changed
+617 -40

No files matched your search

+22 -5
View File
@@ -9,25 +9,42 @@ How to use slackerbot from Slack.
| DM with the bot | `u-<user id>` | Only you |
| Channel, private channel or group DM (@mention the bot) | `c-<channel id>` | 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.
In channels, @mention the bot to start a session. In a session's thread, the bot by default only reads replies that @mention it, but a thread can be switched to read every reply (see **Listening in threads** below). 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, and the first message of a session tells the agent which channel it's in.
In DMs the bot reads every message. You can also chat with it in Slack's assistant pane (the bot's icon in the top bar). Each chat there is its own session, its first message can be a command (the suggested **Container status**, **Past sessions** and **What can you do?** buttons send `status`, `sessions` and `help`), and the agent is told which channel you have open next to it.
## 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.
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. To stop a reply part-way, 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.
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.
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.
## Listening in threads
Channel threads start out in `only-mentions`: the bot only reads replies that @mention it. Switch with `@slacker /listen …` (the mention matters, because Slack treats a message starting with `/` as a slash command). `listen` without the slash works too.
| Command | Where | What it does |
|---|---|---|
| `@slacker /listen all-messages` | in a session's thread | The bot reads every reply in this thread |
| `@slacker /listen only-mentions` | in a session's thread | Back to replies that @mention the bot |
| `@slacker /listen` | in a thread | Shows what this thread does |
| `@slacker /listen channel all-messages` (or a top-level `@slacker /listen all-messages`) | anywhere in the channel | Sets the channel's default for threads that haven't set their own |
| `@slacker /listen channel` | anywhere in the channel | Shows the channel's default |
Anyone in the channel can change these. In an `all-messages` thread, `move` still needs an @mention, so a chatty "move on" doesn't move the container. DMs always read every message.
## Commands
Send these as a **new message**, not in a thread. `move` is the one exception, and also works in a thread.
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 |
|---|---|