slack-term 1.41.0 → 1.41.1
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/SKILL.md +1 -0
- package/dist/cli.js +160 -159
- package/package.json +1 -1
- package/ts/botIntent.ts +68 -0
- package/ts/cli.ts +34 -4
package/SKILL.md
CHANGED
|
@@ -415,6 +415,7 @@ slack news --limit 1
|
|
|
415
415
|
- **`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.
|
|
416
416
|
- **Send is rejected with "use #channel or @user"** — the CLI enforces human-readable targets. Use `#channel-name` or `@display-name`, not raw IDs.
|
|
417
417
|
- **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).
|
|
418
|
+
- **`refusing to act as YOU — SLACK_BOT_TOKEN is exported …`** — you set a bot token in the shell or a project `.env` (not the global `~/.config/slack-cli/.env`) but ran a write without `--as-bot`, which would post as the logged-in person. Add `--as-bot` to post as the app; to post as yourself, set `SLACK_TOKEN` or clear the bot token for that run (`SLACK_BOT_TOKEN= slack …`). Reads are never refused.
|
|
418
419
|
- **Enterprise Grid / admin-locked workspace** — custom app installation may need admin approval or be disabled outright.
|
|
419
420
|
|
|
420
421
|
## Safety
|