status button

This commit is contained in:
ari committed 2026-11-01 15:29:38 -05:00
1 parent c7547a9125
commit 9e94c05fb6
5 files changed
+109 -23

No files matched your search

+1 -1
View File
@@ -19,7 +19,7 @@ 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. 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.
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.
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.