yumauri/fbrcm

fbrcm is a terminal manager for Firebase Remote Config. Use its interactive
TUI to explore and edit projects, or use the CLI for scripts, repeatable
operations, and machine-readable output.
> [!TIP]
> Using fbrcm from an LLM agent, script, or CI runner? Start with the
> agent quickstart.
> Machine-readable command discovery is also available through
> fbrcm capabilities --json.
> [!CAUTION]
> This project is almost completely vibe-coded.
> [!TIP]
> Already using the official Firebase CLI? See
> fbrcm vs. Firebase CLI for feature parity,
> command equivalents, and the Remote Config workflows fbrcm adds.
fbrcm is most useful when work spans more than one Firebase project:
- inspect parameters, groups, conditions, and version history;
- compare and promote configuration between projects or template types;
- stage related changes as local drafts before publishing;
- import, export, validate, roll back, and restore Remote Config templates;
- manage client and server templates from the same workspace.
Installation
macOS and Linux
Install the latest release:
The installer places fbrcm in /usr/local/bin by default. To use another
directory:
With Homebrew:
Windows
Install the latest release from PowerShell:
The installer places fbrcm.exe in
%LOCALAPPDATA%\Programs\fbrcm\bin by default and adds that directory to your
user PATH. To use another directory:
With Scoop:
Other options
Download an archive from
GitHub Releases, or install from
source with Go 1.27.1 or newer:
Official release binaries include fbrcm's Google OAuth Desktop client. A plain
source build leaves it out. In that build, the google authentication method
reports that the built-in client is unavailable. The oauth,
service-account, and gcloud methods continue to work.
> **Unavailable — Google verification pending:** The built-in google method
> will remain unavailable until Google completes verification of fbrcm's OAuth
> application. Use oauth, service-account, or gcloud in the meantime.
For local development, build with a Desktop client from values in the current
shell. This does not add the client JSON to the repository or runtime
configuration:
Use a local development client unless you have access to the official release
credentials.
When both OAuth environment variables are unset, the generator and release
workflow produce an uncredentialed build in which Google sign-in is unavailable.
Setting only one variable is an error.
First run
Start the TUI:
For guided setup in the command-line interface instead, run:
On a new profile, fbrcm opens guided TUI setup. Both guided setup paths support:
- Google sign-in using fbrcm's built-in shared OAuth client (**unavailable —
Google verification pending**);
- an OAuth Desktop app client;
- a service-account JSON key;
- existing Google Cloud CLI Application Default
Credentials.
The identity needs access to the projects you want to manage. Project discovery
uses the Cloud Resource Manager API. Template reads, validation, publication,
defaults, and history use the Firebase Remote Config API. The apps commands
use the Firebase Management API to list registered apps, inspect them, and
download their SDK configuration.
fbrcm requests the broad cloud-platform OAuth scope because Google's
interactive consent flow rejects the narrower firebase.remoteconfig scope,
while the grantable firebase scope is insufficient for Remote Config. This
Firebase discussion
reports the same limitation. The Firebase Management API accepts
cloud-platform for the read-only apps commands, so those commands do not
need another scope. Its read-only scopes would not cover Remote Config writes.
fbrcm limits its Google API calls to Cloud Resource Manager, Firebase Remote
Config, and Firebase Management. See the privacy policy for the
data-access, local-storage, and deletion details.