Repository navigation
docs(auth): 完善 chrome-use 动态码登录与迁移说明 - #29
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
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.
Document the browser authenticator flow supported by chrome-use builds that list
--totpin auth help: fetch TOTP after observing the challenge, or complete an existing challenge without replaying credentials or_autotype. Each vault phase retains its own authorization and audit.Explain setup-key migration through the vault UI, keep keys out of chat/arguments, distinguish authenticator codes from SMS/email/push, and stop treating pending verification as a completed login. Manual multi-account selection now requires an identified account instead of silently choosing the first result.
Documentation only. Checked the commands against the companion chrome-use implementation and reviewed the diff; no vault was read or modified. Requires that companion chrome-use feature before its new flag is used.
Companion implementation and acceptance evidence: leeguooooo/chrome-use#806.