Skip to content

Latest commit

 

History

History
61 lines (40 loc) · 1.98 KB

File metadata and controls

61 lines (40 loc) · 1.98 KB

Comparison

@yudin-s/react-chrome-ai is a React hook layer for Chrome Built-in AI. It is intentionally focused on browser-native APIs and UI state.

Direct LanguageModel Calls

Direct calls are fine for tiny demos:

const session = await LanguageModel.create();
const text = await session.prompt("Hello");

Use this package when the app needs production UI states:

  • support detection;
  • availability checks with the same options used for creation;
  • user activation hints;
  • first-run download progress;
  • session cleanup;
  • streaming chunks in React state;
  • context-window usage;
  • structured output helpers;
  • task API wrappers.

@browser-ai/core

@browser-ai/core is a good fit when your app is standardized around the Vercel AI SDK provider model.

Choose this package instead when you want:

  • React hooks directly;
  • no AI SDK dependency;
  • explicit Chrome session lifecycle control;
  • UI-first download and readiness state;
  • task API hooks beyond the general Prompt API.

The two approaches can coexist. Use @browser-ai/core for AI SDK transports and this package for Chrome-specific React UX.

simple-chromium-ai

simple-chromium-ai is a compact TypeScript wrapper for experimenting with Chromium AI APIs.

Choose this package when:

  • the application is React;
  • UI needs to show readiness, progress, and errors;
  • you want hooks rather than a generic wrapper;
  • examples and agent-friendly docs matter.

@types/dom-chromium-ai

@types/dom-chromium-ai provides community TypeScript declarations for Chromium AI APIs.

This package ships conservative local types so users can install one package and start building. You can still use @types/dom-chromium-ai in applications that want declarations closer to the latest upstream spec.

Cloud Gemini SDKs

Cloud Gemini SDKs call Google-hosted models and require cloud credentials, quota, and network access.

This package wraps Chrome's browser-owned APIs. It does not call Google cloud APIs and does not manage API keys.