Running Ops
Use the minimal Ops CLI for development only, and understand how web and desktop dev modes relate to the current workflow boundary.
The current Ops CLI is intentionally narrow. Its job is to start local development, not to own Supabase operations.
That keeps the command surface small and reduces confusion about where setup, migration, configuration, and installation workflows belong.
The command that still matters
pnpm ops devThis is the development entry point that remains inside Ops. Use it after the repository has already been prepared with Polter.
Web versus desktop development mode
- Web-only mode starts the Vite-based web experience for fast UI iteration.
- Desktop mode starts the Tauri shell plus the web app so you can verify native desktop behavior.
- Desktop mode requires the Rust toolchain and Tauri prerequisites.
What the minimal CLI does not do anymore
Responsibilities moved to Polter
Do not rely on Ops CLI commands for setup, database linking, migration management, runtime configuration, or packaged app installation. Those workflows are owned by Polter.
| Command | Description |
|---|---|
pnpm ops dev | Start local development. This is the supported Ops CLI workflow. |
npx polter app setup ops --path . | Prepare a source checkout before running the app locally. |
npx polter app configure ops --path . | Refresh development and runtime connection material when the backend changes. |