Browser extension (Chrome, Edge, Brave)

The Gravitree browser extension is a front door onto the same catalog, approvals, and Outcomes as the web app. It reads page context from supported sites and runs governed catalog actions — never DOM automation as a substitute for a CRM write.

Activation milestone (aha in minutes): install → connect org → one real enrich → one approved write → see it in Outcomes.

What the extension supports

Writes always use the server confirmation token gate — the extension cannot skip approval with a client-side flag.

Install

Option A — Chrome Web Store

When a public or unlisted listing is available, open the store link from Browser extension and click Add to Chrome. Edge/Brave users can often install from the same Chromium store listing when published.

Option B — Load unpacked (developer / private beta)

1. Get the apps/extension pack from your Gravitree deployment or engineering contact.
2. Chrome / Edge / Brave → Extensions → enable Developer mode.
3. Load unpacked → select the extension folder.
4. Pin the Gravitree icon.

Connect your org

1. Open the extension popup → Connect Gravitree.
2. Sign in at gravitre.app if needed and select the org.
3. On /extension/connect, authorize — the page sends your session to the extension (same JWT + org as the web app).

Extension popup

A connected popup shows the org id you authorized and your role, plus the connectors currently active for it. Check the org id here before enriching — it is the org every read and write will be attributed to.

If connect fails: confirm you opened Connect from the extension (so ext_id is present), you are signed in, and an org is selected.

First value — enrich and approve a write

1. Connect Apollo and/or HubSpot under BUILD → Connectors (/connectors) in the active Environment.
2. Open a LinkedIn profile (or Gmail / Outlook / a company page).
3. Use the overlay (or popup → Enrich) — Gravitree runs catalog reads from page context.
4. Choose a suggested write (e.g. create contact / create list) → Approve.
5. Open Outcomes / Runs — the run should show source=browser_extension and a completed notification fanout.

The overlay separates what it read from the page from what each connector returned, so a missing result is legible rather than mysterious — below, Apollo matched but HubSpot came back unavailable with the reason.

linkedin.com/in/… — Gravitre overlay

Choosing a suggested write does not write anything yet. The overlay first shows the exact field-by-field payload and the catalog action it will call, and the footer stays pinned to Writes need approval:

linkedin.com/in/… — confirm write

That sequence is the product “aha”: the write is the same governed path as chat, not a parallel automation stack.

Optional — the side panel

If you would rather keep Gravitre docked than open the overlay on top of the page, use Open side panel in the popup. It targets the current tab only and runs the same governed catalog path — it is a different placement, not a different engine.

Extension side panel

Permissions (why we ask)

We do not request debugger, <all_urls>, or background crawling.

You can audit this yourself at any time — the popup's What Gravitre can see panel lists the exact hosts and restates the read and write limits:

Extension popup — permission scope

Trigger a workflow from the overlay (v3)

The overlay can list active typed-contract workflows and run them through the same execute path as chat (plan steps → approve → Outcomes). It does not invent new workflow logic in the extension.

1. Open the overlay on a supported page.
2. Under Workflows, pick an active multi-step workflow.
3. Review the plan steps (same shape as chat’s plan bar).
4. Approve & run — confirm uses the server token; execution is the shared engine path.
5. Open Outcomes for the run — full step chain, source=browser_extension.

Expanding a workflow shows every step and the catalog action behind it before you approve, so “3 steps” is auditable rather than opaque:

linkedin.com/in/… — workflow plan

Live example (production tip verify): workflow MSP NVD CVE Lookup completed with steps nvd.cve.get + cisa_kev.feed.get — run 139fd6cc-7d53-4dfd-ac1b-c59e902109ea.

Ask about this page (v4 overlay chat)

The overlay includes a short Ask about this page box. It calls the same unified-turn / execute_task_streaming path as main Gravitree chat, with page context passed in as data.

Inline (quick): fact questions grounded in the page (name, title, company).
Handoff: write intents, long threads, or multi-step plans (≥3 steps — same threshold as the main-chat progress panel) open full Gravitree chat at /ai?c={conversationId} (same conversation). The overlay does not duplicate that progress panel.

It is not a second reasoning stack and not a place to approve complex connector plans — use Continue in Gravitree when the overlay says the request needs the full app.

Live transcript proof: conversation cc618049-… — overlay page-context answer + write handoff stub, both persisted before opening the full app.

Troubleshooting

Platform names (IA)

If older docs mentioned Command Center, Agent Swarm, or Apps, use current names: Gravitre AI, Multi-Agent Run, Connectors. See FAQ — renamed surfaces.

Related

• Approvals
• Monitor Runs
• Connect integrations
• Product page: Browser extension