Sync from docs: CLI no longer requires --project-id/--org-id for most commands (powersync-docs #475)#48
Merged
michaelbarnes merged 1 commit intoJun 25, 2026
Conversation
…#475) The CLI now auto-resolves project and org IDs from the instance ID. Only `powersync link cloud --create` still requires --project-id. CI deployments only need INSTANCE_ID (drop PROJECT_ID / ORG_ID).
Contributor
|
note that the docs PR may have been merged a little prematurely. The CLI version with this change isn't fully out yet. |
Collaborator
Author
|
Good catch — converting to draft. These changes should not be merged until the CLI version that auto-resolves project/org IDs from instance ID is fully released. Once that version is out, mark ready for review to proceed. Generated by Claude Code |
Contributor
|
Now released |
michaelbarnes
approved these changes
Jun 25, 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
3 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.
Source docs PR: powersync-ja/powersync-docs#475
What changed in docs
The PowerSync CLI now automatically resolves project and org IDs from the instance ID, making
--project-idand--org-idoptional for most commands. The only exception ispowersync link cloud --create, which still requires--project-idbecause no instance ID exists yet.Skill updates in this PR
skills/powersync/references/powersync-cli.md— Updated instance resolution note; removed--project-idfrompull instance,link cloud(non---create), and flag/env examples; droppedPROJECT_ID/ORG_IDfrom the CI env-vars table and example; updated Common Commands table and migration table accordingly.skills/powersync/AGENTS.md— Updated "Required Inputs Before Coding" to remove "Project ID" as a required input when using the CLI with an existing instance.Notes for reviewer
powersync link cloud --create --project-id=<id>is intentionally unchanged — the docs explicitly carve out--createas still requiring--project-id.cli.yamlmulti-env Option B example still includesproject_id/org_idfields; these remain valid as an optional performance cache (the CLI uses them to skip a lookup when present). No change was made there since the fields are still supported and the example is illustrative, not prescriptive.--org-idnote onpowersync login/--createwas also left intact — the docs confirm those still apply for multi-org tokens.Generated by Claude Code