feat(slack): post slash-command replies in-channel#32
Merged
Conversation
Slack slash-command replies defaulted to response_type: ephemeral, which showed "Only visible to you". Route all /parallax replies and plan-approval error follow-ups through response_type: in_channel so they are visible to the whole channel. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Slack slash-command replies defaulted to
response_type: ephemeral, which is what produced the "Only visible to you" label on/parallax status(and every other subcommand). This routes all replies throughresponse_type: in_channelso they are visible to everyone in the channel.Changes
packages/slack/src/handlers/commands.ts— added areply()helper wrapping everyrespond()with{ response_type: 'in_channel', text }, and routed all/parallaxsubcommand responses (retry,cancel,status,pr-review, plus usage/unknown/error messages) through it.packages/slack/src/handlers/plan-approval.ts— addedresponse_type: 'in_channel'to the error/failure follow-ups (replace_original: false). Success paths already update the original in-channel message viareplace_original: trueand were left unchanged.packages/slack/src/test/commands.test.ts— new handler tests assertingin_channelon the usage message, a successfulstatus, and an unreachable-orchestratorstatus.docs/slack-bot.md— documented that all slash-command replies are posted in-channel.Testing
pnpm --filter @parallax/slack build✅pnpm --filter @parallax/slack lint✅pnpm --filter @parallax/slack test✅ (17 tests)Note
All slash-command output is now public, including error/usage messages (e.g. a mistyped command). If preferred, those noisy cases could stay ephemeral while keeping confirmations public — happy to adjust in a follow-up.
🤖 Generated with Claude Code