slack-term 1.39.1 → 1.40.0

package/README.md

@@ -91,7 +91,7 @@ slack search "deploy" --count 50
 slack send "#general" "Hello team"
 # Prints who you're acting as (From: @handle (Uxxxx) — Workspace) + a destination
 # preview + confirm code; rerun with --code=<code> to actually send. Every gated write
-# (send/edit/delete/upload/schedule/channel create/lists/drafts) shows that From: line and
+# (send/edit/delete/upload/schedule/channel create/rename/lists/drafts) shows that From: line and
 # binds it into the code, so a profile switch mid-flow invalidates it instead of acting
 # as the wrong account.
 slack send "#general" "Hello team" --code=<code>

package/SKILL.md

@@ -120,7 +120,7 @@ plus `[as bot]` under `--as-bot`) and the resolved destination (`→ ... — THR
 `→ ... — NEW top-level message`); verify both before re-running with `--code`.
 
 **Every** gated write opens its preview with that same `From:` line — `send`, `edit`,
-`delete`, `upload`, `schedule send`, `schedule rm`, `channel create`, `lists create/add/set/share`, `drafts edit`,
+`delete`, `upload`, `schedule send`, `schedule rm`, `channel create`, `channel rename`, `lists create/add/set/share`, `drafts edit`,
 `drafts delete` — and the identity is part of the confirm hash: switching
 profile/token between preview and confirm invalidates the code instead of acting as
 someone else. It matters most on `schedule send`, where the message goes out later,
@@ -135,7 +135,8 @@ UTC, and the two are easy to mix up. Check the side you meant before confirming.
 member in plain text (honorifics like `山田さん` / `王老师`, or `Hi Dave`) without a
 matching `<@USERID>` tag, it prints `⚠ possible untagged mention: …` alongside the
 confirm code. It never blocks — third-party/external references are expected to trip it.
-To actually notify someone, write `@handle` (auto-converted to `<@USERID>`; see below).
+It stays quiet for people Slack notifies anyway: in a thread reply, anyone who started or
+replied in that thread; in a 1:1 DM, the other member. To actually notify someone, write `@handle` (auto-converted to `<@USERID>`; see below).
 
 When the target is a **thread**, the confirm preview shows the thread's recent messages
 (not the channel's last message) and prints `⚠ possible duplicate: …` if your text is
@@ -274,6 +275,22 @@ 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)
+
+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.
+
+```bash
+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
+```
+
+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.
+
 ## Output formatting
 
 - DM channels render as `@DisplayName`; public channels as `#channel-name`.
@@ -283,6 +300,11 @@ points into one message.
 - Attachments show a `📎 <name> (<size>) [<file-id>]` line under the message; `--json`
   adds a `files[]` array (`id`, `name`, `mimetype`, `size`, `url_private_download`,
   `permalink`) only on messages that have attachments. Fetch one with `slack download <file-id>`.
+- Forwarded / shared messages (Slack's "Forward", or a pasted message link) show under the
+  comment as `↪ shared message from @<author> in <#C…> · <ts>`, the original text quoted
+  with `│`, and its permalink. Legacy bot attachments show as `▸ <title>`; web-page link
+  previews are left out. `--json` adds `attachments[]` (`shared`, `unfurl`, `author_id`,
+  `author_name`, `channel_id`, `ts`, `title`, `text`, `permalink`) only when present.
 
 ## Getting a Slack token (first-time setup)