Enquire docs
    Enquire docs
    Getting startedUser guide
    ArchitectureBrowser toolsProcedures
    Claude Code integrationExtension guide
    DeploymentRoadmapBenchmarks
    Integrations

    Extension guide

    Install, configure, and use the Enquire Chrome extension.

    The Enquire extension is the browser-side runtime. It owns the visible Chrome tab, stores local settings and procedures, runs the side-panel agent, and keeps the cloud tunnel open when Cloud mode is enabled.

    Install

    Enquire is currently distributed as a signed beta build. Email support@enqr.dev for access.

    For local development, build from the sibling enquire repo:

    npm install
npm run build:store

    Then load the extension in Chrome:

    1. Open chrome://extensions
    2. Enable Developer mode
    3. Click Load unpacked
    4. Select dist/chrome-mv3-store/ from the enquire repo

    Modes

    ModeWhat it does
    LocalRuns the side-panel agent in your browser. External MCP clients cannot reach this browser.
    Edit on GitHub

    Claude Code integration

    Wire Enquire into Claude Code: HTTP MCP setup, multi-tunnel routing, common patterns.

    Deployment

    Self-host bridge, API, and Postgres on Railway; web on Vercel.

    On this page

    InstallModesLLM ProvidersSide PanelProceduresPrivacy Boundary
    CloudSigns in through app.enqr.dev, opens a WebSocket tunnel to bridge.enqr.dev, and lets MCP clients call your browser through https://bridge.enqr.dev/mcp.

    Cloud mode requires the same account you use on app.enqr.dev. Your MCP client uses a bearer token from /app/setup; the extension uses that session to keep its tunnel registered.

    LLM Providers

    The side-panel chat can use cloud or local models depending on your settings:

    ProviderNotes
    AnthropicUses your stored API key in BYO mode, or the managed bridge when your account is in managed mode.
    OpenAI, Google AI, Bedrock, AzureStored locally in extension settings for BYO use.
    Ollama, WebLLM, transformers.jsLocal or in-browser models for cheaper mechanical browsing steps.

    If you only use Enquire through Claude Code, Cursor, or another MCP client, the client’s model can drive the MCP tools directly. You only need an extension-side model for the side-panel chat.

    Side Panel

    Open the side panel from the Enquire toolbar icon. It gives you:

    SurfacePurpose
    Chat timelineUser messages, assistant responses, and timestamped tool calls.
    Active tab barShows the Chrome tab the agent will drive; detach without closing the tab.
    Agent state barCurrent mode, plan progress, and last action.
    Model pickerPer-chat override for the configured model.
    Tool badgeShows the visible tool surface for the active tier and mode.

    The same agent loop powers enquire__chat from external MCP clients, so a run started in Claude Code can still appear as a live conversation in the side panel.

    Procedures

    Procedures are local-first browsing recipes stored in chrome.storage.local. You can create, edit, replay, and delete them from the extension UI or through MCP procedure tools.

    Some procedures include a captured tool-call trace. Those can replay deterministically step-by-step before falling back to the LLM recipe path. Hand-authored YAML procedures remain useful for flows that need judgement or site-specific notes.

    Privacy Boundary

    In BYO mode, API keys and raw page content stay on your machine unless you explicitly ask a model provider to process page content. The cloud bridge relays MCP requests to your extension; it is not a hosted browser.

    Cloud services store account metadata, usage/cost logs, and dashboard-visible procedures that you sync or save through the API. Local memory and local procedure state stay in the extension unless a sync path explicitly sends them.

    See also: Getting started | Architecture | Browser tools