slack-term 1.32.2 → 1.32.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -23,6 +23,29 @@ byte-for-byte by [`tests/parity.sh`](tests/parity.sh).
23
23
  - Slack `<!date^...>` markup is rendered as human-readable dates
24
24
  - Messages are grouped by day (Today / Yesterday / weekday)
25
25
 
26
+ ## Comparison with other Slack tools
27
+
28
+ `slack-term` focuses on everyday workspace interaction through shell commands:
29
+ read, search, reply, and coordinate work from a terminal or an agent script.
30
+ The alternatives below serve different workflows; links point to their upstream
31
+ documentation.
32
+
33
+ | Tool | Main workflow | How it compares with this project |
34
+ | --- | --- | --- |
35
+ | **`slack-term` (this project)** | Workspace messaging and automation | TypeScript and Rust implementations; explicit user-token setup; message previews and confirm codes for `send`, `edit`, and `delete`; `ask` waits for answers and `todo` tracks tasks through reactions. |
36
+ | [`slkcli`](https://github.com/therohitdas/slkcli) | Slack commands for macOS users and agents | Extracts credentials from the Slack desktop app for convenient onboarding. This project offers an explicit-token setup suitable for other platforms, at the cost of configuring an app and scopes. |
37
+ | [Official Slack CLI](https://docs.slack.dev/tools/slack-cli/) | Building, running, and deploying Slack apps | Choose it for Slack app development. This project's commands focus on interacting with messages in an existing workspace. |
38
+ | [Go `slack-term`](https://github.com/jpbruinsslot/slack-term) | Interactive terminal chat | Provides a full-screen terminal client. This project uses individual shell commands, which fit scripts and quick queries. The two projects are unrelated despite sharing a name. |
39
+ | [`wee-slack`](https://github.com/wee-slack/wee-slack) | Slack inside WeeChat | Offers ongoing chat with threads, reactions, and synchronized read markers. Choose it if you already use WeeChat; this project runs as a standalone CLI. |
40
+ | [`slackcat`](https://github.com/bcicen/slackcat) | Posting files and piped command output | Focuses on sending stdin, files, and streaming logs to Slack. This project also covers reading, searching, and following conversations. |
41
+ | [`slackdump`](https://github.com/rusq/slackdump) | Archiving and exporting Slack data | Offers dedicated archives, export formats, and a local viewer. This project's `dump` provides markdown history exports alongside everyday messaging commands. |
42
+
43
+ Choose this project when you want **scriptable conversations with a preview before
44
+ sending**. The confirmation step adds an extra invocation, and token setup requires
45
+ the appropriate Slack scopes. Reactions are immediate and do not use the confirm
46
+ gate. For a persistent chat UI or a dedicated archive, the specialized tools above
47
+ may be a better fit.
48
+
26
49
  ## Installation
27
50
 
28
51
  ### TypeScript (npm, recommended)
@@ -73,6 +96,11 @@ slack send "#general" "Hello team"
73
96
  # as the wrong account.
74
97
  slack send "#general" "Hello team" --code=<code>
75
98
 
99
+ # send/edit/ask refuse ambiguous bare URLs such as https://example.com/path/内容.
100
+ # Put the URL on its own line or use <https://example.com/path/> (or <url|label>).
101
+ # Intentional Unicode URLs should also be wrapped. --allow-url-adjacent warns only;
102
+ # the normal confirmation code is still required.
103
+
76
104
  # Reply in a thread — #chan:<thread_ts>, or just paste a message permalink
77
105
  slack send "#general:1700000000.000100" "Replying in thread"
78
106
  slack send "https://acme.slack.com/archives/C0123456789/p1700000000000100" "Replying in thread"