Starting applications with the ap CLI

On this page

Whether backend, app, or homepage – you start every application of a platform project with the same command inside the repository folder:

ap run-local

The CLI loads the right environment files, starts required Docker services (e.g. the backend’s database), and then launches the development server. Fixed ports per repository allow several applications to run in parallel.

This works the same locally on your machine and in a remote workspace. In VS Code, Cursor, and Antigravity, the start button of the platform extension runs the same command.

Choosing target and device

For apps you can specify target and device, e.g. for Flutter:

ap run-local chrome            # web build in the browser
ap run-local ios-simulator     # iOS simulator (macOS)
ap devices list                # show available devices

More useful commands

Command	Purpose
`ap doctor`	Checks whether all required tools are available
`ap bootstrap`	Installs the `.tool-versions` runtimes without starting the app
`ap ports`	Shows the repositories’ local ports
`ap workspace info`	Shows the project/repository overview
`ap git auto-commit`	Stages, commits, and pushes in one step
`ap secrets edit <file>`	Edit encrypted GitOps configuration
`ap cli-update check`	Checks for CLI updates

Note

The ap CLI is installed and kept up to date automatically by the setup app. In workspaces it is preinstalled.

If something doesn’t start

ap doctor shows whether a tool is missing.
If the start aborts because a port is taken, stop the old process or the old Docker containers.
Your own variables for local runs belong in env/local.custom.env – see Working with environment variables.