Add WhatsApp channel support and QR login flow parity#18
Draft
Add WhatsApp channel support and QR login flow parity#18
Conversation
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.
Remove WhatsApp from onboarding channel inputs and pairing-step plumbing while keeping the post-setup channel flow intact, and fix completion copy spacing for dynamic channel names.
|
Thanks for carrying this through and for referencing #8. Glad the initial patch helped surface the integration points. I’m happy to test the WhatsApp flow from the user side if that’s useful. |
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.
Summary
main, including channel creation, onboarding/import validation, pairings support, and watchdog notifications.channels login) with API response behavior that surfaces stdout/stderr without treating incomplete login as a hard API failure.Test plan
npm test -- tests/server/agents-service.test.js tests/server/routes-agents.test.jsWHATSAPP_OWNER_NUMBERas valid channel credential.References #8