slack-term 1.35.0 → 1.37.0

package/README.md

@@ -126,7 +126,9 @@ slack react "<permalink>" eyes --remove   # take a reaction back
 slack ask "@bob" "本番に出してよい?" "出してよい" "待って"
 # --wait blocks until answered and prints ONLY the answer on stdout, so it composes:
 ANS=$(slack ask "@bob" "本番に出してよい?" "出してよい" "待って" --code=<code> --wait)
-# exit 0 = answered, 2 = timed out (--timeout, default 3600s), 3 = transport failure.
+# exit 0 = answered, 2 = timed out (--timeout, default 3600s), 3 = transport failure,
+# 4 = a reply matched several choices, 5 = a free-text reply that picked NO choice —
+# the reply text is on stdout, it is not a decision, and the question stays open.
 #
 # The question must say WHO may answer — only their reaction/reply is taken as the
 # answer, so a bystander can't decide it for them. `ask` refuses to post otherwise.
@@ -144,14 +146,26 @@ RESUME=$(slack ask "@bob" "本番に出してよい?" "出してよい" "待っ
 #   -> slack ask --waitFor='https://acme.slack.com/archives/C00000001/p1700000000000100'
 # Run it whenever you like: it re-reads the question from Slack, so nothing is
 # stored locally and any machine holding the link can collect. Same stdout/exit
-# contract as --wait, plus --timeout 0 = check once (exit 2 while still open, 4 if
-# somebody replied without choosing any of the offered options),
+# contract as --wait, plus --timeout 0 = check once (exit 2 while still open, 5 with
+# the reply on stdout if somebody wrote free text instead of choosing; re-wait past
+# it with --after=<reply ts>),
 # which is what a periodic monitor should use instead of parking on --wait.
 eval "$RESUME --timeout 0" && echo answered
 # A pressed pill is invisible to `slack tail` (it only sees `type: "message"`
 # events and drops `message_changed`), so this is the only way to hear about an
 # answer to a question you did not block on.
 
+# Who sent what: every send/ask/poll/edit is logged locally with its sender —
+# pid, cwd, git branch, agent CLI and session id — and the same attribution rides
+# along as invisible Slack message metadata (event_type `slack_term_sent`).
+slack sent                                     # newest first, sender on its own line
+slack sent "deploy" --since 2h --kind ask      # substring of the text
+slack sent --session 4f1c --cwd ~/ws/app --json
+# Log: ~/.config/slack-cli/sent.sqlite (SLACK_TERM_SENT_DB overrides).
+# Opt out of both with SLACK_TERM_ATTRIBUTION=off. Agent CLIs other than Claude
+# Code are found by process name; set SLACK_TERM_AGENT_SESSION / _CLI / _PID to
+# name the session explicitly.
+
 # Task tracking on top of reactions — :pushpin: marks a message as a task,
 # a second reaction carries its progress (see "todo" below)
 slack todo ls                                  # my open tasks
@@ -321,6 +335,24 @@ Or place it in `~/.config/slack-cli/.env` or a local `.env` file.
 
 See [`SKILL.md`](SKILL.md) for a full token-acquisition walkthrough.
 
+### Ubuntu desktop session
+
+Sign in to Slack in Chrome or Slack Desktop. `--from-chrome` reads a browser `xoxc-` token and cookie from the same Chrome profile; desktop import reads `xoxc-` tokens from native, Snap, or Flatpak data directories. Browser profiles contain sensitive cookies, so the CLI asks `Read local browser profiles and Slack session cookies? [y/N]` before scanning. Enter `y` to allow a scan; the default is no.
+
+```sh
+slack auth login --from-desktop                 # desktop token only
+slack auth login --from-chrome                  # Chrome token + Chrome cookie
+slack auth login --from-firefox                 # desktop token + Firefox cookie
+slack auth login --from-all                     # desktop and browser sources
+slack auth login --from-chrome --yes            # bypass the browser-read prompt
+slack auth tokens                              # print active credentials in .env format
+slack auth save --envfile=./.env.local          # export active token + cookie
+```
+
+`--from-all` attaches a cookie only when exactly one browser session is found. If several are found, the desktop token is saved without a cookie; use `slack auth chrome -w <name>` or `slack auth firefox -w <name>` to select the matching profile. These commands also ask before reading browser profiles, and accept `--yes` for scripts. Select the saved workspace with `slack auth use -g <name>`. `auth tokens` prints the active `SLACK_TOKEN`, optional `SLACK_COOKIE`, and optional `SLACK_BOT_TOKEN` to stdout; treat its output as secret. `auth save` requires a cookie, writes `SLACK_TOKEN` and `SLACK_COOKIE`, and makes the env file owner-readable only on Unix. `--workspace <name>` selects a specific profile.
+
+Chrome supports Linux `v10` cookies and `v11` cookies when `secret-tool` can read the unlocked GNOME keyring. Other Linux keyring backends are not yet supported. Firefox discovery covers native, Snap, and Flatpak profiles. If browser session access is unavailable, use `slack auth token` to add a user token from a Slack app. Treat desktop tokens and browser cookies as credentials; keep profile files and local env files private.
+
 ## Development
 
 ```sh

package/SKILL.md

@@ -162,15 +162,17 @@ without losing clicks. A reaction is durable state anyone can read back later.
 - **Two pills pressed = no answer.** Changing your mind leaves both reactions in place, so
   `ask` says so in the thread once and keeps waiting rather than guessing.
 - **Exit codes** are the contract: `0` answered (the answer alone on stdout), `2` nobody
-  replied, `3` transport/config failure, `4` somebody replied but picked none of the
-  offered choices. Everything human-facing goes to stderr, so
+  replied, `3` transport/config failure, `4` a reply matched several choices (stdout
+  empty), `5` a **free-text reply** that picked none of the offered choices — the reply
+  text is on stdout. Everything human-facing goes to stderr, so
   `ANS=$(slack ask … --wait)` is safe.
-- **A reply that chooses nothing is not an answer.** When choices were offered, only a
-  reaction, the choice text, or its number counts. A reply like 「意味が分かりません」 or a
-  question back exits `4` with **stdout empty** — measured 2026-09-04, a clarifying
-  question was returned as `rc=0` and stored as the decision, which is what an automated
-  caller acts on. `2` and `4` need different reactions: one waits, the other answers a
-  person who is standing there.
+- **A reply that chooses nothing is delivered, but is not a decision.** When choices were
+  offered, only a reaction, the choice text, or its number is a decision (`0`). A reply
+  like 「背景を教えて」 or 「3 でなく X にして」 exits `5` at once with the text on stdout
+  — read it and act on it; do not treat it as a chosen option (measured 2026-09-04, a
+  question back returned as `rc=0` was stored as the decision). The question stays open,
+  so a pill pressed later still decides it: re-wait past the delivered reply with
+  `slack ask --waitFor='<permalink>' --after=<reply ts>` (stderr prints this line).
 
 **Collecting an answer you did not block on.** Without `--wait`, stdout is a runnable
 `slack ask --waitFor='<permalink>'`. Run it any time — it re-reads the question from Slack
@@ -184,6 +186,22 @@ This path is not optional convenience — **a pressed pill is invisible to `slac
 which only sees `type: "message"` events and drops `message_changed`. Without `--waitFor`
 an answer can be pressed and nobody ever hears about it.
 
+### sent — what did I post, and which session posted it
+
+Every `send`/`ask`/`poll`/`edit` is logged locally (`~/.config/slack-cli/sent.sqlite`)
+with its sender: agent pid, cwd, git branch, agent CLI and session id. The same
+attribution is attached as Slack message `metadata` (event_type `slack_term_sent`) —
+invisible in the client, readable through the API from any machine.
+
+```bash
+slack sent "deploy" --since 2h               # text substring, newest first
+slack sent --kind ask --session <id-prefix>  # this session's questions
+slack sent --cwd . --json                    # everything posted from this repo, every field
+```
+
+Read-only and token-free. `SLACK_TERM_ATTRIBUTION=off` disables both the log and the
+metadata; `SLACK_TERM_AGENT_SESSION` / `_CLI` / `_PID` override what is detected.
+
 ### todo — tasks as reactions
 
 A task is any message carrying the marker reaction 📌 `:pushpin:`. Progress lives in a
@@ -304,7 +322,7 @@ slack news --limit 1
 - **`missing_scope`** — add the scope from the error, then click **Reinstall to Workspace** (scope changes require reinstall).
 - **`token_revoked`** — app uninstalled; reinstall from the app page.
 - **Token starts with `xoxb-`** — that's a Bot Token. Add scopes under **User Token Scopes** instead, reinstall, and copy the **User OAuth Token**.
-- **`xoxc-` desktop session token** — accepted by the public Slack API (send/edit/delete/react/upload/channel create+invite included) as long as its `xoxd` session cookie is attached (`slack auth chrome`/`slack auth firefox`, or `SLACK_COOKIE=...`). Without the cookie it still fails with a clear "needs its session cookie" error.
+- **`xoxc-` desktop session token** — accepted by the public Slack API (send/edit/delete/react/upload/channel create+invite included) as long as its `xoxd` session cookie is attached (`slack auth firefox` on Ubuntu, `slack auth chrome` on macOS/Linux, or `SLACK_COOKIE=...`). Without the cookie it still fails with a clear "needs its session cookie" error.
 - **`conversations.invite` reports success but the member never shows up** — the invited user is likely a single-channel guest (`is_ultra_restricted`); Slack silently no-ops the invite since that account type can only ever belong to the one channel it was created in. `channel create --invite` now warns about this up front.
 - **Send is rejected with "use #channel or @user"** — the CLI enforces human-readable targets. Use `#channel-name` or `@display-name`, not raw IDs.
 - **Confirm code mismatch on any gated write** — the content, target or acting identity changed between preview and confirm (a different profile/`SLACK_TOKEN`, or `--as-bot` added or dropped). Re-run without `--code` for a fresh preview, and re-check the `From:` line and the `→` destination line (THREAD REPLY vs NEW top-level message).