CLI reference
The client is the same bunker binary as the server. Install it with the installer (without sudo it only installs the binary into ~/.local/bin). bunker help <command> shows the details of any command.
Get started
Section titled “Get started”bunker login https://bunker.example.com # approve this computer in the browserbunker deploy # publish this folder; creates the app the first timebunker share ada@example.com "London Office" --role editorbunker openCommands
Section titled “Commands”| Command | |
|---|---|
bunker login [url] |
Sign in. Opens the browser to approve this computer (a one-time code is shown in the terminal too) and saves a personal token in ~/.config/bunker/config.json. --token bk_... (or --token - for stdin) uses an existing token; --no-browser; --scopes read,write,admin |
bunker deploy [dir|file|-] |
Publish a folder, a single file or stdin as a new version. Aliases publish, up |
bunker open [site] |
Open an app (or the dashboard) in the browser. --draft opens the draft preview |
deploy details:
- The first deploy of a folder creates the app and writes
bunker.json{server, site}. Later deploys update that app and upload only files that changed (content hashes). A single file or stdin doesn’t writebunker.json: pass--siteto update the same app again (otherwise each deploy creates a new one). - If
package.jsonhas abuildscript, Bunker builds first (npm, pnpm, yarn or bun) and uploadsdist/,build/orout/.--build/--no-buildforce it either way;--dir distpicks a folder. - Files matched by
.gitignoreor.bunkerignoreare skipped. - Flags:
--site/-s slug,--message/-m text,--title/-t name(new app),--draft,--open/-o,--filename(for stdin, defaultindex.html).
bunker deploy ./site -m "New menu"bunker deploy report.html --opencat page.html | bunker deploy -bunker deploy --draft| Command | |
|---|---|
bunker sites [ls|create|rm|rename|info] |
List, create, rename and remove apps. ls --filter all|mine|shared|org|starred|recent|templates|trash, --query text; create/rename --slug address; create --description text. Aliases site, ls |
bunker share [site] <email|group>... |
Share with people (anything with an @) or groups (a name or ID). --role viewer (default) or editor |
bunker unshare [site] <email|group>... |
Stop sharing |
bunker versions [site] |
List versions. Alias history |
bunker rollback [site] [version] |
Make an earlier version live again (default: the previous one). bunker restore [site] [version] does the same |
bunker pull <site> [dir] |
Download an app’s working files into a folder. --version n, --force |
[site] can be left out inside a folder that has a bunker.json.
Server functions
Section titled “Server functions”See Server functions. The app’s address comes first (bunker fn ls team-lunch); inside a folder with bunker.json you can leave it out.
| Command | |
|---|---|
bunker fn [ls] [site] |
List the app’s functions with their triggers, elevated flag and any bundling error |
bunker fn call [site] <name> [json|@file|-] |
Call a function and print what it returns. --draft runs the draft code |
bunker fn runs [site] |
Recent runs with status, time, trigger, user and error. --name/-n fn for one function; --limit n (default 20) |
bunker fn logs [site] |
Recent runs with their logs, oldest first. --follow/-f streams live logs; --name/-n fn; --limit n |
bunker secrets [ls] [site] |
List the app’s secret names (values can’t be read back) |
bunker secrets set [site] <NAME> |
Store or replace a secret. The value is never an argument: it’s read from a hidden prompt, from stdin, or with --from-file path, so it stays out of your shell history |
bunker secrets rm [site] <NAME> |
Delete a secret |
Agents and automation
Section titled “Agents and automation”| Command | |
|---|---|
bunker ai [site] "<prompt>" |
Build a new app by describing it, or change one (--site). Changes land in the draft. --open |
bunker api <op.name> [path params] [--param value ...] [--data json] |
Call any API operation |
bunker ops [filter] |
List every operation the server offers. --names, --full |
bunker mcp |
Run a local MCP server over stdio (MCP) |
bunker init [dir] |
Set up a folder for Bunker and write AGENTS.md so coding agents follow the sandbox rules. --site links an existing app |
Account and tools
Section titled “Account and tools”| Command | |
|---|---|
bunker whoami |
Who you’re signed in as |
bunker logout |
Sign out and revoke this computer’s token (--keep-token only forgets it) |
bunker tokens [ls|create|rm] |
Manage personal access tokens: bunker tokens create ci-deploy --scopes read,write --days 30 |
bunker doctor |
Check config, connection, sign-in, versions and clock |
bunker update |
Update this program to the latest release, checksum verified. --check, --force, --version v0.3.0. Alias upgrade |
bunker update --remote |
Update the server you’re signed in to (admins; same as Admin → Updates) and wait until it’s back. --check, --version v0.3.0 |
bunker completion bash|zsh|fish |
Print a shell completion script |
bunker backup [file] |
Download a full backup (database, files, secret.key) from the server you’re signed in to (admins). --no-key leaves the key out. See Backups |
bunker restore <backup.tar.gz> |
Unpack a backup into BUNKER_DATA_DIR (stop the server first; the old database is kept as bunker.db.pre-restore-<time>) |
Server
Section titled “Server”| Command | |
|---|---|
bunker serve (or no command) |
Run the server, configured with environment variables |
bunker dev |
A local single-user server on 127.0.0.1:8080 with no sign-in (you are a local admin) |
bunker demo |
Like dev, pre-filled with example apps, people and data |
bunker healthcheck |
Exit 0 when the local server answers /healthz (for Docker HEALTHCHECK) |
bunker version |
Print the version |
Global flags
Section titled “Global flags”--json (machine-readable output), --yes/-y (skip confirmations), --server url (or BUNKER_SERVER), --profile name (or BUNKER_PROFILE, for several logins), --no-color (or NO_COLOR=1), --debug (print HTTP requests), --help/-h.
Every operation is a command
Section titled “Every operation is a command”Every server feature is an operation, so new features work in the CLI immediately:
bunker api sites.list --filter minebunker api sites.get team-lunch # positional = path paramsbunker api sharing.add --site team-lunch --type user --id ada@example.com --role viewerbunker api files.write --site team-lunch --path about.html --content @about.htmlbunker api sites.update team-lunch --data '{"settings":{"spa":true}}'bunker api db.rule --site team-lunch --coll orders --rule privatebunker api drafts.publish --site team-lunchbunker api fn.call --site team-lunch --name hello --data '{"input":{"color":"green"}}'Numbers and booleans are converted using the parameter’s type. @file reads a file, @- reads stdin, and for upload parameters @folder sends a whole folder.
Skip login and set BUNKER_SERVER and BUNKER_TOKEN:
- run: bunker deploy ./dist --site team-handbook -m "$GITHUB_SHA" env: BUNKER_SERVER: https://bunker.example.com BUNKER_TOKEN: ${{ secrets.BUNKER_TOKEN }}Tokens start with bk_, have scopes read, write and optionally admin, expire after at most 90 days (BUNKER_TOKEN_MAX_DAYS), and appear in the audit log as via: token.