Repository navigation
feat: add hosted credential request handoff - #45
Merged
Merged
Conversation
This was referenced Nov 8, 2026
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
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.
Problem and behavior
Signed-in chat visitors need a safe way to respond when an agent requests credentials. With explicit CCP and identity opt-in, the widget now shows a typed request and opens the authenticated Dewee-hosted form. The visitor enters no credential value into the widget or chat. Status, cancellation, history restore and a value-free continuation stay bound to the verified user, agent and conversation by the Gateway.
The host pins the HTTPS form origin; only the fixed Dewee credential route and one-time token shape are accepted. Requests fail closed on an identity or conversation change, and the feature remains off by default. Direct Gateway transport does not support the hosted flow; its legacy stream and history now suppress credential-tool payloads and unmatched/malformed tool results to avoid exposing handoff data.
Part of #1. Gateway/CCP contract: nextlevelbuilder/dewee#2240, merged to
devatfd0cbd4. The issue remains open until an enabled Gateway/CCP deployment completes the real signed-in flow and recovery paths.Validation
PHP_BIN=C:/tools/php/php.exe pnpm test— 404 passed, 5 skipped;pnpm typecheck,pnpm build,pnpm test:bundlers,php -lpassed.Surface parity: Node/Workers, PHP, widget, HTTP contract and package docs updated. Gateway/CCP authorization and trace/activity evidence are supplied by #2240; trace parity RGD/CCP/API-CLI follows that change. CLI/MCP N/A for visitor transport routes; no privileged management operation is added here. Public docs follow-up: nextlevelbuilder/dewee-web-v2#133. Live deployment verification remains outstanding.