docs: add Cursor Cloud pscale build/install notes to AGENTS.md#1291
Closed
heyglassy wants to merge 2 commits into
Closed
docs: add Cursor Cloud pscale build/install notes to AGENTS.md#1291heyglassy wants to merge 2 commits into
heyglassy wants to merge 2 commits into
Conversation
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.
What
Adds a
## Cursor Cloud specific instructionssection toAGENTS.mdcovering two things discovered while setting up a Cursor Cloud dev environment:pscalefrom this repo (entry point./cmd/pscale, install to/usr/local/bin/pscale), and that installing the binary does not authenticate it.pscale auth loginhangs on the desktop keyring prompt. In the Cursor Cloud VM the gnome-keyring SecretService backend is present but locked, so after approving the device flow the CLI blocks on a "Choose password for new keyring" dialog and never writes the token (auth checkkeeps reportingNO_AUTH). Documented the workaround: run withDBUS_SESSION_BUS_ADDRESS=unix:path=/dev/nullsopscalefalls back to its plaintext file store at~/.config/planetscale/access-token(must be applied to reads too, since those also open the keyring).Why
Both are non-obvious and cost real time to rediscover. The keyring hang in particular looks like a failed login when it's actually a blocked credential write.
Notes
pscale version 0.299.0builds and runs from this repo with Go 1.26.