Monorepo for the PowerSync CLI and related tooling. Built with pnpm workspaces and OCLIF.

• Architecture, scripts, and troubleshooting tips live in packages/editor/README.md.

• Node: LTS v24+ (see .nvmrc; use nvm use to switch)
• Package manager: pnpm

The workspace is split into the main CLI, shared packages, and optional plugins:

├── cli/                    # @powersync/cli — main CLI (commands, cloud/self-hosted, templates)
├── packages/
│   ├── cli-core/           # @powersync/cli-core — base commands & YAML utils (used by CLI + plugins)
│   ├── editor/             # CLI Config Studio — Monaco web app that edits service.yaml/sync-config.yaml
│   └── schemas/            # @powersync/cli-schemas — config validation (LinkConfig, CLIConfig)
├── plugins/
│   ├── config-edit/        # @powersync/cli-plugin-config-edit — serves the Config Studio preview
│   └── docker/             # @powersync/cli-plugin-docker — docker configure, reset, start, stop
├── examples/               # Sample projects initialized with the CLI (see examples/README.md)
│   ├── cloud/
│   └── self-hosted/
└── docs/
    ├── usage.md            # General CLI usage (Cloud, self-hosted, linking, auth)
    └── usage-docker.md     # Docker plugin (configure, reset, start, stop, templates)

• cli depends on cli-core, cli-schemas, @powersync/cli-plugin-config-edit, and @powersync/cli-plugin-docker. It loads the bundled plugins and re-exports base command types from cli-core.
• cli-core depends on schemas. It provides SelfHostedInstanceCommand, YAML helpers (!env), and shared types for plugins.
• packages/editor builds the Config Studio assets consumed by the config-edit plugin and embeds schemas from @powersync/cli-schemas.
• @powersync/cli-plugin-config-edit depends on cli-core and serves the built editor from plugins/config-edit/editor-dist using the Nitro server.
• @powersync/cli-plugin-docker depends on cli-core and cli-schemas. No dependency on the CLI package.

Workspace roots are listed in pnpm-workspace.yaml: cli, packages/*, plugins/*.

We rely on standard OCLIF plugin loading so plugins can register new commands or hook into command execution. The main CLI ships with Docker and Config Studio plugins under plugins/docker and plugins/config-edit, and any other OCLIF-compatible plugin can be installed the same way.

For PowerSync-specific plugins, the optional @powersync/cli-core package exposes base command helpers and shared types. The bundled plugins consume these helpers and serve as reference implementations.

Users can manage their own installed plugins dynamically at runtime. Run powersync plugins --help for install, uninstall, and inspection options.

nvm use          # use Node from .nvmrc (optional)
pnpm install
pnpm build

Run the CLI from the repo root:

powersync --help

From the repo root, create the Docker layout and run the stack:

powersync docker configure
powersync docker start

See plugins/docker and docs/usage-docker.md for details.

Open the Monaco-based Config Studio that edits service.yaml/sync-config.yaml directly inside your project:

pnpm build                                  # ensures packages/editor copies its dist to plugins/config-edit/editor-dist
powersync edit config --directory ./powersync --port 3000

• The command above is provided by @powersync/cli-plugin-config-edit and automatically sets POWERSYNC_PROJECT_CONTEXT (based on the linked project) before serving the built editor through the Nitro server.
• Features include YAML schema validation, Monaco-powered completions, unsaved-change tracking, reset/save controls, and an error panel for schema violations.
• For local UI work (without running the CLI command) export POWERSYNC_PROJECT_CONTEXT JSON that points at your project (the CLI sets this for you) and start the dev server: POWERSYNC_PROJECT_CONTEXT='{"linkedProject":{"projectDirectory":"/path/to/project","linked":{"type":"self-hosted"}}}' pnpm --filter editor dev.
• Prefer the default host (127.0.0.1); only pass --host 0.0.0.0 when you explicitly intend to expose the editor on your network.
• Architecture, scripts, and troubleshooting tips live in packages/editor/README.md.

The examples/ folder contains basic projects initialized with the CLI. See examples/README.md for the full list and links to each example's README.

• Usage — How the CLI works: Cloud and self-hosted, linking, auth, supplying instance info
• Usage (Docker) — Docker plugin: configure, reset, start, stop, templates, flags
• CLI documentation conventions — How we document commands (description, summary, examples, flags, topics)
• CLI package README — Install, usage, and command reference