Get started
From store to first turn.
Install the signed extension, pair one revocable device credential, and choose when Chelai may work with a site.
1. Install Chelai
Open the download center in desktop Chrome or Firefox and continue to the signed browser-store listing. Browser-managed installation provides signing and updates.
2. Connect your account
Open the extension and choose Continue to Chelai. Sign in through your deployment’s identity provider, click Create connection code, and paste that code into the extension. The extension connects immediately; there is no approval return trip and no access token to manage.
3. Choose site access
Use Allow site access from the popup or side panel. Chelai resolves the active tab when you click and asks the browser for that origin. Click again to remove the grant.
4. Open the workspace
The side panel is the full conversation surface. The floating overlay uses the same composer for quick work beside a page. Connect browser tools only when an agent needs the browser command bridge.
Common states
The extension says “Not connected”
Chat may still be available. “Connected” refers to the browser-tool command bridge, not whether the Chelai identity is valid.
The extension cannot read this page
Browser-internal pages, extension pages, and other restricted schemes do not accept normal site permissions. On an HTTP(S) page, grant that origin explicitly.
The connection code expired
Create a new code. Codes are single-use and expire after ten minutes; an expired or consumed code cannot be revived.
I paired the wrong device
Open Paired devices and revoke the labeled token. Connecting another browser does not require revoking existing devices.
Administrator deployment
The extension’s production Chelai origin belongs in the generated manifest’s host permissions. Chrome consumer installs use the Web Store; managed environments may distribute through enterprise policy. Firefox packages require Mozilla signing whether listed or self-distributed.
Serve this site and Chelai’s /api and /auth paths on the same HTTPS origin so secure OIDC session cookies can power pairing and live trial pages.