Installing an extension

This page walks you through the install flow end-to-end. The same flow applies to free, subscription, per-seat, and metered extensions.

Before you start

You'll need:

A bRRAIn account.
An organization where you have Architect or Sovereign role.
A working brain pod for that organization (Healthy on the Console dashboard).
For paid extensions, a payment method on file for the organization.

If any are missing the install dialog will prompt you to fix that step before continuing.

Step 1 — Pick the extension

From the Marketplace catalog or directly from a search result, click the extension you want. Read the listing — particularly the Scopes required and Pricing detail sections. See Browsing extensions for what each section means.

Step 2 — Click Install

The button is always Install for free extensions and Subscribe & install for paid. If you're not signed in you'll be prompted; if you don't have an organization yet you'll be invited to create one.

Step 3 — Pick the destination organization

If you belong to more than one organization, you're shown a picker. Pick the one to install into. The picker shows each organization's plan tier and current install count so you can confirm at a glance.

If the extension requires a higher tier than your current plan, the picker tells you and offers an upgrade path.

Step 4 — Approve the scopes

We show you the full list of scopes the extension declares it needs. Each scope is explained in plain English:

The extension wants to read records from the engineering zone. The extension wants to write records to a new zone it will create called agent-orchestrator-runs. The extension wants to use the Slack integration to send messages. The extension wants to spawn a non-human actor named "agent-runner-bot" with role Operator.

You can:

Approve all — the simple path.
Customize — narrow some scopes (e.g., grant only one zone instead of two), or block some entirely. Extensions usually function with reduced scopes; some features may be disabled.
Deny — cancel the install.

Step 5 — Confirm billing (paid extensions only)

For paid extensions:

We show the price model.
We show your next invoice preview (proration if mid-cycle).
For per-seat models you confirm the active seat count.
For metered models you confirm the unit price and optional spend cap.

Your payment method on file is used.

Step 6 — Wait for the install

Once you confirm, three phases run in sequence:

Marketplace records the install (instant) — the extension appears as Pending in your Console.
Console wires the extension into your nav (instant) — a new entry appears under Installed extensions.
Your pod fetches and starts the extension (typically 10–60 seconds) — the status pip turns from amber to green when the extension is reachable.

The Marketplace page redirects you to your Console while phase 3 completes. Watch the status pip; when it's green, you're done.

Step 7 — Configure (optional)

Most extensions show a brief setup wizard the first time you open them. Common setup steps:

Choose default settings (template language, time zone, default integrations).
Connect to vendor accounts via OAuth (if the extension uses integrations you haven't already configured).
Invite specific members to the extension's iframe (if the extension wants its own access list narrower than your organization's role hierarchy).

You can revisit setup at any time via the extension's settings page.

Re-installing

Re-clicking Install on an extension you already have is a no-op for free extensions and a pricing-confirmation re-prompt for paid ones. We never charge you twice for the same install.

Installing on multiple organizations

Each organization is a separate install. If you're an Architect across three organizations and want the same extension on all three, you install it three times — once per organization.

Troubleshooting

Status stays amber — your pod is still wiring up. Wait 60 seconds, then refresh. If it stays amber beyond 5 minutes, click for the diagnostic pane.

Status turns red — install failed. Common reasons:

The extension's binary failed signature verification (rare; contact support).
Your pod ran out of disk space (resize from Console → Storage).
A scope you denied was actually mandatory (re-install with full scope approval).
The extension's manifest is incompatible with your pod version (upgrade your pod).

The diagnostic pane shows the specific reason and the next step.

Extension iframe shows an error — the extension's child process is up but its UI is failing to load. Check the extension's Observability pane for crash detail. Most extensions auto-restart and recover within a minute.

Where to next

Console: Marketplace install — operator-side detail on how installs are managed.
Billing & licensing — what happens to billing when you install, update, or uninstall.
Pick the extension you want to install from the Marketplace extensions list.