Quick setup

What it does

briglia quicksetup is the desktop version of the Ubuntu Touch app's quick setup. The briglia process itself serves a small page on 127.0.0.1 and opens it in your browser. Keys go from that page to the process on your machine, which sends each one to its provider for a live check, then stores them in ~/.config/briglia/secrets.json. Nothing is sent to briglia.dev.

Before you start

• Mac: Homebrew must be installed (Briglia never installs it), plus python3 with a working pip (the Xcode Command Line Tools or brew install python).
• Linux: apt, dnf or pacman, sudo, python3 with pip, and a systemd user session (any normal desktop or server install has one). Quick setup installs Briglia as an always-on service there; on a Mac you keep running it from the terminal.
• Disk: the tools take about 1.5 GB (LibreOffice is most of it) and can need up to 40 minutes on a slow connection. Quick setup checks free space before it starts.
• Keys, in the order the page asks for them — the same as the QR generator: OpenCode Go, OpenAI, Serper, Jina, Telegram bot token, Telegram chat ID. Optional: an AgentMail key (gives Briglia its own email address), an OpenRouter key or a custom OpenAI-compatible endpoint as alternative providers.

1. Install Briglia

   curl -fsSL https://github.com/permaevidence/briglia-cli/releases/latest/download/install.sh | bash

   Copy

   Details on the install page. Quick setup is for a fresh install; an already configured Briglia is changed with briglia setup.

2. Run quick setup

   briglia quicksetup

   Copy

   The terminal prints a link and opens it in your browser. The link works once and for five minutes; press Enter in the terminal at any time for a new one. Keep the terminal open next to the browser: on Linux, sudo asks for your password there.

3. Type your keys

   Fill in your name and the six required keys (plus the optional ones). There is no verify button: each key is checked with its provider on its own as soon as you pause typing or move to the next field, and the result appears right under it — Checking…, a green ✓, or a red ✗ with the reason. Correct a failed key in place and it is checked again automatically (Check again re-tries an unchanged one); changing a key that was already verified sends it back to be checked. The Telegram line also resolves your bot and your chat — a brand-new bot may need you to open it in Telegram and send /start first, then press Check again.

4. Save, then let it set up the computer

   Save and continue becomes available once everything required is filled in and verified; it stores it all together. The page then works through the system steps one by one, each with evidence, not assumptions:

   • Mac: Full Disk Access for your terminal app (the page opens the right System Settings pane; macOS asks to quit and reopen the terminal — do it, then run briglia quicksetup again and it continues from where it was), keep-awake (Briglia prevents idle system sleep while it runs; a closed lid or a manual sleep still stops it), and the toolchain.
   • Linux: keep-awake (a headless box passes on evidence; a desktop that could suspend gets the fix or the exact command), the toolchain (one package-manager install with sudo in the terminal), then the always-on service, verified live before setup is marked complete.

   Since 0.2.20 a failed toolchain or system step shows the command's own last output lines under the red reason (up to 8, secrets redacted) — a brew install --cask libreoffice failure shows its Error: line right on the page instead of only "exited with status 1", so you rarely need the terminal to see what to fix. The output belongs to that step alone and clears when you retry.

5. Done

   Mac: the terminal asks whether to start Briglia now. Linux: Briglia is already running as a service and answers on Telegram; briglia in the terminal opens a local chat.

Changing settings later

Since 0.2.11, briglia quicksetup on an install that is already set up opens a settings page instead of refusing. From it you can change or add API keys, add a provider (OpenCode Go, OpenRouter, OpenAI API, ChatGPT subscription, a custom endpoint or a local server), sign in to ChatGPT, and choose the model, the reasoning effort and which provider is active. Each section is verified and saved on its own; leaving a key blank keeps the stored one, and the browser never receives stored secrets.

If Briglia is running, that process serves the page, and a save waits for an idle moment (it will not interrupt a turn, a subagent or a maintenance task). If Briglia is stopped, the settings command holds the instance lease while the page is open, so a second agent cannot start underneath it. Closing the page keeps whatever was saved. briglia setup in the terminal remains the step-by-step alternative.

What the page can and cannot protect

The page is served only on 127.0.0.1, by the briglia process, for one session. Requests need the single-use link, an exact origin and a header no cross-site form can send; the page has no inline scripts and no storage. A process running as you can already read your secrets file, so the page grants it nothing new; root can read everything anyway. Another account on the same machine could, in the few milliseconds the link sits on the browser opener's command line, grab it and get a session until you press Enter — the terminal tells you when a link was used by something else. Full text in Security.