Document browser-based device authorization for CLI login - #3130
Open
atharvadeosthale wants to merge 1 commit into
Open
Document browser-based device authorization for CLI login#3130atharvadeosthale wants to merge 1 commit into
atharvadeosthale wants to merge 1 commit into
Conversation
- Update CLI installation docs with the new appwrite login flow and screenshots - Add announcement blog post (authored by Chirag, dated 2026-07-29) - Add changelog entry for 2026-07-29
Appwrite WebsiteProject ID: Website (appwrite/website)Project ID: Tip Schedule functions to run as often as every minute with cron expressions |
| title: "Announcing Device Authorization for the Appwrite CLI: Log in from your browser" | ||
| description: The Appwrite CLI now signs you in through your browser. Confirm a device code, review permissions, and authorize, without typing credentials into your terminal. | ||
| date: 2026-07-29 | ||
| cover: /images/blog/announcing-cli-device-authorization/cover.avif |
Contributor
There was a problem hiding this comment.
We need a cover sorted out
adityaoberai
requested changes
Jul 28, 2026
| featured: false | ||
| callToAction: true | ||
| faqs: | ||
| - question: "What is Device Authorization in the Appwrite CLI?" |
Contributor
There was a problem hiding this comment.
This should include OAuth
|
|
||
| Today, we are announcing **Device Authorization** for the Appwrite CLI. Running `appwrite login` now hands the sign-in process to your browser, so you can authenticate the CLI with the account session you already trust. | ||
|
|
||
| # How it works |
Contributor
There was a problem hiding this comment.
We should probably add an info note at the end or a subsection that clarifies that existing API key based auth and flows won't break and that they are still recommended for CI workflows, etc.
Contributor
There was a problem hiding this comment.
This should also be more explicitly covered in the docs
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
The
appwrite logincommand now uses browser-based device authorization. This PR updates the website for the new flow:/docs/tooling/command-line/installation#login): rewrote the Login section to walk through the device authorization flow (terminal code + URL → confirm code → authorize → device connected), with light and dark screenshots of each step plus a terminal screenshotannouncing-cli-device-authorization(authored by Chirag, dated 2026-07-29). Cover points to/images/blog/announcing-cli-device-authorization/cover.avif, which does not exist yet and needs designNotes
bun run optimize;bun run formatpasses