Environment variables

Variable	Effect
PEKO_ROOT_PATH	where the toolchain is installed. Default ~/.Peko.
PEKO_PLATFORM_URL	the platform base URL. Default https://app.pekoui.com.
PEKO_REGISTRY_URL	the package index and blob base.
PEKO_OFFLINE	skip the keychain read and all network access, for hermetic builds.
PEKO_SKIP_ROOT_CHECKUP	bypass the installation health gate. Setup sets this on the commands it spawns.
PEKO_RUNNER_KEY	the age recipient to seal signing material to.
PEKO_ASSUME_NON_APPLE_HOST	treat the host as non-Apple, forcing the remote Apple build path.

Studio and the dev loop set a few more for the app they launch: PEKO_DEV_SERVER points the window at the framework dev server, PEKO_INITIAL_ROUTE restores the route across a relaunch, and PEKO_DEMO activates the demo surface.

Global flags

Every command accepts these, parsed before the subcommand:

Flag	Effect
--json	emit machine-readable events instead of prose
--verbose	extra output
--quiet	suppress informational output
--no-color	no ANSI colour

--json is what Peko Studio consumes.

Flag syntax

A flag value can be written --flag=value or --flag value. The space form works for flags that are declared to take a value; for anything else the second token is treated as a positional argument. A declared value-flag with no value is an error rather than a silent empty string.

Where the built-in help may lag

peko help <command> is generated from files that ship with the CLI, and a few have drifted from the code. Where this book and peko help disagree, this book describes what the code does. The notable cases are peko run (the dev loop replaced an older hot-reload design), peko format (it reprints from the syntax tree rather than only re-indenting), and several flags that work but were not listed, including --global on add and remove, --web-dist on build, and the remote-build targets on deploy.