Server configuration
All environment variables are optional for local development. The defaults provide a working setup out of the box.Single-user vs multi-user mode
By default, Buckle runs in single-user mode with no login screen. This is ideal for local development and personal use. To enable multi-user mode with Google OAuth, set the three auth variables:Bring your own database
By default, the Docker Compose setup bundles a PostgreSQL instance. To use an external PostgreSQL instance instead:Telemetry
Self-hosted Buckle sends no telemetry by default. The gateway’s analytics sink stays off unless both of these are set:
See Telemetry for details on what is collected and where.
CLI configuration variables
These variables configure thebuckle CLI tool. Each one overrides the matching stored value, so they suit CI jobs and scripts where writing config files is awkward.
Development vs production
SettingBUCKLE_ENV=dev switches the CLI to development mode, which uses separate files and keychain entries so it never interferes with your production setup:
Variables set by buckle run
buckle run injects these into the wrapped agent process. They are not user-configurable:
See the Coding Agents guide for what
buckle run does end to end.