Run with Browser AI · Chapter 01
Run Chapter 01 with Browser AI
Inspect whether the current browser is merely an AI client or can act as an AI runtime.
← Read The Browser Stops Being Just a Client
Execution
Not inspected
Observed state machine
What “built-in” means in this browser
No capability call has been made in this page yet.
- 01Not inspected
- 02Unsupported
- 03Unavailable
- 04Downloadable
- 05Downloading
- 06Available
- 07Session ready
- 08Running
- 09Completed
- 10Failed
Derived from events
Observatory measurements
Missing evidence stays missing. The dashboard never estimates an absent measurement.
Application instrumentation
Cross the boundary without erasing it
The page can validate what it sends. Extension receipt is confirmed only in the attached DevTools panel.
- 01Application SDKBuild a sanitized envelope
- 02Same-origin bridgeValidate schema and size
- 03Extension transportRoute by inspected tab
- 04DevTools panelConfirm receipt and correlate
To test end to end, load the Observatory extension, attach DevTools to this tab and enable instrumentation for this origin.
Shared lifecycle · distinct contracts
Browser AI capability switchboard
No interface has been inspected. Each check will use that interface's declared creation options.
| Interface | Global | Exposed | Availability | Options |
|---|
Canonical fixture · live task API
Summarization contract
Exposed Not inspected
Availability —
Session None
Load the canonical fixture, then inspect the current browser.
Generated artifact
No summary yet.
Contract evaluation
- No evaluation yet.
Ranked evidence · explicit routing policy
Language routing laboratory
Choose a fixture, then inspect Language Detector.
Ranked detector evidence
| Rank | Language | Confidence | Use |
|---|---|---|---|
| No ranked candidates yet. | |||
Translated artifact
No translation yet.
Translation evaluation
- No translation evaluation yet.
Resource state · measured lineage
Session lineage laboratory
Prompt API Not inspected
Availability —
Inspect the current browser before creating a session.
Original session
Not created- ID
- —
- Parent
- None
- Usage
- —
- Quota
- —
- Remaining
- —
- Clone / destroy
- —
No output yet.
Cloned session
Not created- ID
- —
- Parent
- —
- Usage
- —
- Quota
- —
- Remaining
- —
- Clone / destroy
- —
No output yet.
Shared-history acknowledgement
No shared-history run yet.
Lifecycle invariants
- No invariants evaluated yet.
Chapter experiment
The Browser Stops Being Just a Client
Loading the chapter experiment…
No model output yet.
Inspect the context supplied by this chapter
What this experience knows
This experience is grounded in Chapter 01 rather than the entire website.
Central distinction
A browser acting as an AI client sends work to a model hosted elsewhere. A browser acting as an AI runtime owns or exposes the inference capability inside the browser execution environment.
Required concepts
- browser-managed versus application-managed inference;
- capability detection versus user-agent detection;
- availability versus session readiness;
- local execution versus complete data-flow privacy;
- interface compatibility versus behavioral compatibility.
Evidence boundary
The page can directly observe exposed JavaScript capabilities and the results of calls it makes. It cannot attest the exact underlying model unless the browser exposes that identity. A recorded trace describes another run and must never be presented as live evidence from the current browser.
This is the first chapter-specific Browser AI experience. It checks the capability boundary in the page’s real top-level context, prepares a local session only after an explicit click and records metrics-only evidence.
If the Prompt API is unavailable, replay the captured Chrome trace and continue through the same explanatory interface.