Chrome extension - v0.2.35

Route AI requests from trusted browser apps without exposing provider code.

AI Runtime is a Chrome MV3 extension that gives approved websites and Chrome extensions one controlled runtime for Ollama, LM Studio, WebLLM, OpenRouter, and Anthropic.

Download extension Configuration steps

Purpose

A shared AI gateway for pages you explicitly trust.

Instead of embedding API keys and provider-specific code in every web app, the extension keeps provider configuration in Chrome and exposes a runtime only to origins or extension IDs that you authorize.

Local-first routing

Prefer Ollama, LM Studio, or WebLLM when available. Ollama requests use the extension-backed CORS proxy so localhost ports such as 11434 work from MV3 extension pages.

Trusted caller list

Grant access by hostname or Chrome extension ID. Unauthorized pages can detect that setup is needed, but they cannot use the runtime.

Attachments

Send prompts with optional text, JSON, CSV, PDF, and image attachments through the same runtime request flow.

Install

Load the unpacked extension package in Chrome.

The download contains a ready-to-load extension folder. Chrome will assign an extension ID after installation; client apps need that ID unless they use the page detection helper.

  1. Download and unzip the extension package.
  2. Open chrome://extensions.
  3. Enable Developer mode.
  4. Choose Load unpacked.
  5. Select the extracted extension folder.

Configuration

Set providers first, then authorize callers.

01

Open extension options

Use Chrome's extension details page or the small page launcher on an authorized site. The options page contains AI providers, authorized callers, a test console, and the local audit view.

02

Configure providers

Set local base URLs for Ollama or LM Studio, enable WebLLM if the browser profile supports WebGPU, and add OpenRouter or Anthropic API keys only if cloud AI is required. The packaged extension allows non-standard localhost ports in its MV3 content security policy.

03

Authorize callers

Add each trusted hostname or Chrome extension ID. Hostname authorization ignores protocol and port, so localhost covers common local development ports.

04

Test and monitor

Run a prompt from the options page, verify provider availability, inspect the latest local audit entries, and clear the audit log when stored prompt or response text is no longer needed.

Security and privacy

Data stays local unless a selected provider or bridge target needs it.

API keys and settings are stored in Chrome local extension storage. Prompts, attachments, and responses can be sent to cloud AI APIs only when a trusted caller uses an allowed cloud provider that is configured. Per-app provider/model defaults are also kept in the extension's local storage. See the full privacy policy before publishing or sharing the extension.

Read the technical guide Read the privacy policy