domains / families / agent-tooling / jet-browser

jet-browser

authentic

Verify or integrate Jet Browser when a project needs isolated WPE WebKit sessions, native input, screenshots, ordered JSONL automation, or reproducible runtime checks.

When to use

• Use when a project needs a self-hosted browser process with an explicit container lifecycle.
• Use when a harness needs framework-neutral, ordered JSONL instead of a bundled agent loop.
• Use when native pointer, keyboard, touch, DOM, and screenshot evidence should share one runtime.
• Use when a repository needs a reproducible offline smoke test or GitHub Actions browser-runtime check.
• Do not use this skill to control an already-running personal Chrome or reuse its logged-in state; use the environment's permission-approved CDP workflow for that.

When not to use

• Jet Browser uses WPE WebKit, not Chromium. It does not implement Chrome-only extension, enterprise-policy, or CDP contracts.
• The published v0.9.0 manifest provides native `linux/amd64` and `linux/arm64` images. Other architectures need compatible emulation or a source build for the host architecture.
• Docker and Node.js 24+ are required for the documented standalone flow; source development also requires the repository's Rust toolchain.
• The standalone runtime does not include a hosted control plane, proxy network, account system, persistent daily-browser takeover, or model loop.
• The published ready-time and memory figures are medians from a pinned offline fixture. They do not measure public-site success, stealth, CAPTCHA handling, model accuracy, or long-running stability.
• This skill cannot validate a local run when the required runtime is unavailable; report the missing dependency or failed assertion instead.

Skill page

Source