Skip to the collection

agent-native · Browser & Web Execution · Verified 2026-10-11

Jet Browser

Listed on The Agent-Native Index

Jet Browser — the browser runtime agents can carry

What it does

Jet Browser packages WPE WebKit, a headless Wayland compositor, and a Rust WebDriver bridge as a standalone runtime for agent systems. One container owns one browser session; a harness sends ordered JSONL commands and receives machine-readable results for navigation, native pointer/keyboard/touch input, tabs, JavaScript evaluation, semantic DOM capture, screenshots, downloads, state import/export, and close.

The runtime is intentionally smaller than a complete browser-agent framework. It includes no model, reasoning loop, account, database, proxy network, or hosted control plane. Native input, DOM state, and a fresh screenshot come from the same runtime, while versioned tool declarations let an embedding harness expose only the operations it chooses.


Agent-facing interfaces

How agents onboard

Interaction pattern: self-hosted container runtime with an ordered JSONL stdio protocol. Docker and curl are enough for the bounded acceptance proof:

curl -fsSL https://raw.githubusercontent.com/masakaai/jet-browser/main/scripts/try-jet.sh | sh

See the full onboarding section in the dossier.

Protocol surface

Interface Detail
JSONL stdio Core create → navigate → native input → inspect → screenshot → close protocol, usable from any subprocess supervisor
Agent tool schemas Versioned JSON Schema declarations in sdk/tools.mjs
MCP stdio verifier Two bounded tools for capability discovery and immutable network-disabled runtime acceptance
OCI image Public linux/amd64 runtime at ghcr.io/masakaai/jet-browser:0.8.0; pin its digest in production
GitHub Action masakaai/jet-browser@v0.8.0 runs the acceptance proof in CI
Agent plugins Codex, Claude Code, and Hermes integration metadata around the same runtime boundary

Verification

Last verified 2026-10-11.

Sources: