Open
Conversation
Owner
|
Hi @Photon1c - thanks for the submission. I reviewed this and it still needs a bit of work to integrate fully with the system and QR code pairing. I'm opening another PR that extends this into a complete solution, and will credit you for it! |
Author
|
Hi @chrysb, Thanks for taking a look and extending it! Glad the initial patch helped identify the integration points. |
keaganstokoe
added a commit
to keaganstokoe/alphaclaw
that referenced
this pull request
Mar 12, 2026
Adds full Slack channel support across AlphaClaw — onboarding wizard, channel dashboard, pairings, gateway sync, watchdog notifications, and the channel creation modal. Slack uses Socket Mode which requires two tokens (Bot Token + App Token) rather than one. This is handled via a new `extraEnvKeys` property on channel definitions and dual-token logic in the gateway sync and onboarding flows. Changes: - Add Slack to channel definitions, env keys, and known vars - Add Slack Bot Token and App Token fields to onboarding wizard - Wire Slack into openclaw.json generation (fresh + import flows) - Handle dual-token channel sync in gateway (--bot-token / --app-token) - Use Object.keys(kChannelDefs) instead of hardcoded channel arrays - Add Slack to channel dashboard, pairings UI, and pairing routes - Add App Token field to create-channel modal (Slack is single-account) - Add watchdog crash notifications via Slack DM - Add slack-api.js (minimal Web API wrapper matching existing patterns) - Add Slack SVG icon - Update agents-service test for Slack channel account Ref: chrysb#8 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
6 tasks
chrysb
added a commit
that referenced
this pull request
Mar 13, 2026
Restore the WhatsApp provisioning and login behavior on top of current main, including plugin setup, route response parity, onboarding/watchdog wiring, and a resizable QR output UI. References #8.
4 tasks
chrysb
added a commit
that referenced
this pull request
Mar 22, 2026
Restore the WhatsApp provisioning and login behavior on top of current main, including plugin setup, route response parity, onboarding/watchdog wiring, and a resizable QR output UI. References #8.
chrysb
added a commit
that referenced
this pull request
Mar 22, 2026
Restore the WhatsApp provisioning and login behavior on top of current main, including plugin setup, route response parity, onboarding/watchdog wiring, and a resizable QR output UI. References #8.
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
2 participants
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.
This PR adds WhatsApp as an onboarding channel option alongside the existing channel flow.
Changes include:
Test status:
All tests pass locally.
Passing test suites:
Total:
5 test files
63 tests passed
Notes:
The setup flow now displays WhatsApp correctly during onboarding. I encountered a separate workspace initialization issue during setup which appears unrelated to this patch and may be part of the repository initialization workflow.
Happy to adjust implementation details if maintainers prefer a different integration approach.