Every browser state has a product state.
Feature detection, downloads, progress, cancellation, quotas, context overflow, failure, and cleanup are reactive and typed.
Private AI. Native to Chrome. Ready for your framework.
Ship on-device AI
without the browser plumbing.
Production-ready components and composables for Chrome's Prompt API, writing tools, translation, Proofreader, and WebMCP. No inference server. No API key. No deep-reactivity slowdown.
- ✓ MIT licensed
- ✓ TypeScript-first
- ✓ SSR-safe
- ✓ Zero telemetry
Local AI session Ready
Ask the local model…
Running on-device with Gemini Nano 0 network requests
Prompt API Structured output Long-input handlingWebMCPVue + Nuxt
A production layer, not another model SDK
The native API is powerful.
The lifecycle is the hard part.
Chrome provides the model. Browser AI Kit handles the states and limits that turn a browser experiment into a feature people can depend on.
Responsive while the model works.
Native sessions stay outside deep reactivity. Stream rendering is frame-coalesced so typing remains crisp during local inference.
Long input is a supported path.
Measure real browser quotas, split at safe boundaries, and merge with API-specific strategies instead of arbitrary character caps.
Choose the interface level that fits.
Start with accessible components, move to composables for a fully custom UI, and keep direct access to familiar native operations.
From install to local response in minutes
Small API. Serious defaults.
Drop in a complete chat interface or keep the UI entirely yours. Browser AI Kit stays close to Chrome's vocabulary, so the native documentation and your application code still line up.
npm install @desource/browser-ai-vue
<script setup lang="ts">
import { PromptApi } from "@desource/browser-ai-vue";
import "@desource/browser-ai-vue/assets/lib.css";
</script>
<template>
<PromptApi context-strategy="summarize" />
</template>Production concernNativeKit
Download and readiness UXBuild itIncluded
Measured long inputBuild itIncluded
Prompt context recoveryBuild itIncluded
Nuxt SSR safetyManualIncluded
Accessible starter UINoneIncluded
Calling the native API directly is a good fit for one-off tasks. The kit earns its place when lifecycle, persistence, SSR, or long content matters.
Live in your browser
Eight surfaces.
One consistent experience.
Availability below is detected from this Chrome profile. Open an example to test the real local API—there is no mocked response or hosted fallback behind these demos.
Checking
Prompt API
Stream private chats, return schema-constrained JSON, and keep long sessions useful.
Checking
Summarizer
Turn long content into summaries, key points, headlines, or teasers on-device.
Checking
Writer
Draft text in the tone, format, and length your interface needs.
Checking
Rewriter
Make existing text clearer, shorter, longer, or more formal without a server.
Checking
Translator
Translate supported language pairs with Chrome-managed local packs.
Checking
Language Detector
Rank likely languages with confidence scores and long-text merging.
Checking
Proofreader
Correct grammar, spelling, and punctuation with inspectable edit ranges.
Checking
WebMCP
Publish lifecycle-safe app tools for compatible browser agents to discover and call.
Built for more than one ecosystem
Native to your framework.
Consistent underneath.
Vue, Nuxt, React, Angular, Svelte, and a framework-neutral TypeScript core ship from one repository and share one tested browser-behavior contract.
Vavailable
Vue
Components, composables, and complete TypeScript coverage.
Package guide →Navailable
Nuxt
Auto-imports, client components, and SSR-safe defaults.
Package guide →Ravailable
React
Hooks, external-store state, and accessible components.
Package guide →Aavailable
Angular
Signals, injectable services, and standalone components.
Package guide →Savailable
Svelte
Readable stores, controllers, and Svelte components.
Package guide →TSavailable
TypeScript core
Tree-shakeable lifecycle, text, attachment, and WebMCP controllers.
Package guide →A privacy boundary users can understand
No inference endpoint hiding in the fine print.
The library does not send prompts, outputs, or telemetry to DeSource Labs. Chrome owns model execution and storage. If your app adds a hosted fallback, that becomes a separate product and consent decision.
Read the privacy and fallback guide →Open source and ready to build on
Make the browser the AI runtime.
Start with a package guide, run every API against your local Chrome profile, or inspect the shared contracts that keep every framework adapter aligned.