slack-term 1.45.0 → 1.47.0

package/README.md

@@ -444,6 +444,9 @@ slack stream --grep '<@U00000001>' --replies-to self --json   # + every reply in
   when the relay is down it goes back to `--interval`. Both paths share one record of
   what was printed, so a message is never printed twice. The relay is used only when
   streaming as the bot (it rings for the bot's channels) and never with `--once`.
+  The connection is a WebSocket (the relay hibernates between bells, so an idle
+  connection costs next to nothing); against a relay deployed before that, it falls
+  back to Server-Sent Events. `SLACK_RELAY_TRANSPORT=websocket|sse` pins one.
 - **Polling fallback** (no relay configured, `--as-user`, or `--no-relay`). The stream
   prints a `WARNING: polling mode` line on stderr, pointing to the relay setup. It
   polls every `--interval` (default `45s`), paced to stay inside Slack's rate limits:

package/SKILL.md

@@ -362,7 +362,7 @@ Reason flags stack independently of progress and of each other: ❗ `exclamation
 `slack thread`/`slack read` before replying to avoid duplicates; consolidate multiple
 points into one message.
 
-### todos — Slack's To-dos tab (read-only)
+### todos — Slack's To-dos tab
 
 Not `slack todo`: that tracks tasks as reactions. `slack todos` reads Slack's own
 **personal** To-dos tab (the successor of "Later"), the list in the sidebar.
@@ -371,12 +371,23 @@ Not `slack todo`: that tracks tasks as reactions. `slack todos` reads Slack's ow
 slack todos                       # open to-dos, soonest due first (OVERDUE marked)
 slack todos --filter completed    # also: saved (everything saved), archived
 slack todos --json -n 20          # one object per item: due, done, permalink, text
+
+# Writes — gated like send: the first run previews and prints a code, rerun with --code=<code>
+slack todos add  "<permalink>" --due 2026-11-01T18:00   # --saved: no checkbox
+slack todos done "<permalink>"                          # --undo reopens it
+slack todos edit "<permalink>" --due none               # or --due <time>, --todo / --saved
+slack todos rm   "<permalink>"                          # removes the to-do; the message stays
 ```
 
+A To-do always points at a message, so the target is a message permalink or
+`#chan:<ts>`. `add` refuses a message that is already saved; `done`/`edit`/`rm`
+refuse one that isn't (Slack's delete answers ok even when there is nothing to
+delete, so the CLI checks first).
+
 There is no public API: it uses the desktop client's internal `saved.list`, so
 it needs the **xoxc session** (`slack auth login`) and shows only your own
-to-dos. Bots can't see them. Slack can change this endpoint without notice.
-Adding and completing to-dos is not supported yet.
+to-dos. Bots can't see them. Writes use the internal `saved.add` /
+`saved.update` / `saved.delete`. Slack can change these endpoints without notice.
 
 ## Output formatting