Aluvia

Browser-host compatibility and test evidence

This page as markdown: https://aluvia.io/compatibility.md

Updated · Aluvia

Aluvia is a local CLI and proxy daemon. It needs command access to the machine running a usable Chrome or Chromium browser and Node.js 18 or later. A browser on an inaccessible remote service cannot be configured from a separate agent container.

The table separates recorded tests from setup guidance. It does not certify every agent product or establish access to any target website.

Recorded verification

Runtime or use caseEvidence and dateWhat the evidence covers
Debian 12, Node 22.23.2, Chromium 152.0.7977.82 on Xvfb2026-09-07: packed CLI browser smoke reportCLI 1.4.12 configured real Chromium, kept the tested profile/cookie and debugging port, installed the skill and reused the session on repeat setup. Network services were local fixtures, not a production trial.
Node 18.20.8, 20.20.2 and 22.23.22026-09-07: automated runtime checks202 automated tests passed per runtime; three Windows-only tests skipped. These are not browser tests on every operating system.
macOS Chrome2026-09-07: recorded test limitsDocumented product platform; no end-to-end macOS browser restart evidence in this report. Check setup output and the actual browser task.
Grok Bot, Codex, Cursor, Claude, OpenClaw and Hermes2026-09-08: host-specific guidesConditional setup guidance, not end-to-end integration certification. The agent needs a shell on its browser host; model availability and built-in search routing are separate.
Playwright2026-09-08: browser/context prerequisitesCheck the specific browser and context proxy configuration. The Linux smoke test does not certify every Playwright launch, remote browser or pipe-based controller.

Inspect the skill before setup

Read the current source skill and the skill bundled with published CLI 1.4.12. A source update is not a package release. Setup installs the copy bundled with the version you run.

Try an eligible browser task

First 10 MB free without an account, API key or payment; then $2/GB. Initial setup can restart Chrome. Follow the quickstart: inspect setup, select an available country if needed, reload the page and check the actual content. ready: true confirms the proxy path, not task success.