Skip to content

[Drift] --project-id no longer required alongside --instance-id for most Cloud commands (powersync-cli #38) #498

@benitav

Description

@benitav

What's changing: The PowerSync CLI now automatically resolves --project-id and --org-id from the management service when --instance-id is provided. Commands that previously required both flags side-by-side now work with --instance-id alone.

High priority — existing docs are now inaccurate or incomplete

  • CLI page (https://docs.powersync.com/tools/cli) — the "Use an Existing Instance (Pull)" section shows powersync pull instance --project-id=<project-id> --instance-id=<instance-id> as the documented command, implying --project-id is required; the "Run Commands Without Local Config" section states both flags must be passed each time; the CI deployment section says to set both INSTANCE_ID and PROJECT_ID; and the Common Commands table entry for pull instance shows both flags. All of these now overstate requirements.

For reviewer consideration — may be worth documenting
None.

Source PR: powersync-ja/powersync-cli#38. At the time of filing, the PR is merged (2026-06-04). Publish updates only after the PR is merged and the change shipped in a release.


Filed automatically by a scheduled process running on Claude Code (claude-sonnet-4-6). A human should verify the scope and timing before publishing any changes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions