A project’s settings live in brimble.toml in your repository. Brimble applies the file on every push. The brimble config commands help you write that file and act on what it changes. They don’t replace pushing it.
Generate the file
pull writes brimble.toml from the project’s current settings, the same as Generate brimble.toml in the dashboard. Environment variable values are left out. Without -f, it writes to the linked directory. It asks before overwriting a file. Pass -y to skip the question.
Commit the file unchanged and the next push changes nothing. Edit it and push to change the project.
Check the file
validate reports syntax errors, unknown fields, and out-of-range values with their line numbers, and exits non-zero when the file is invalid. Run it before you commit, or as a CI step.
Preview a change
plan compares the file with what’s running and shows what would change, grouped the same way as the dashboard’s review: Blocked, Needs approval, and Applies automatically, with each field’s old and new value. Resources that exist but aren’t in the file are listed and left as they are.
Nothing changes unless you approve. In a terminal, plan asks whether to apply the changes. Pass -y to apply without asking. If you apply from here, commit the same file, or your next push applies whatever is in the repository.
Approve changes a deploy is waiting on
When a push adds resources or makes a risky change, the deploy pauses at Needs approval. brimble deploy and brimble logs build notice the pause, show the plan, and ask what to do: approve and continue, reject and cancel the deploy, or decide later.
To act on it later or from a script:
approve and reject ask first. Pass -y to skip the question. Last modified on October 16, 2026
