Dovra Beta — beta-20260925

Dovra Beta — beta-20260925

Toolkit-only batch. The browser is unchanged: use the browser package of batch beta-20260924 (Chromium technical version 153.0.8010.48). This is a Beta, not a stable release or a formal Dovra product version.

What changed since beta-20260924

• The companion toolkit adds cli/, the dovra integration command line. A program that manages browser environments can validate a JSON launch configuration (dovra config validate / resolve), ask what the exact browser build supports (dovra capabilities), start one instance per profile and wait for the browser's own handshake (dovra launch), query it (dovra status), and close it with a definite result (dovra close; dovra kill is a separate, recorded forced termination).
  • The configuration is organised by purpose — profile, identity, network, instance, control — and accepts no raw browser switches. Unknown fields, duplicate keys and out-of-range values are rejected with a JSON Pointer to the field.
  • Every command prints one JSON object; decisions are made on stable error codes and exit codes (listed in cli/README.md).
  • The browser opens no debugging port. Control goes through a loopback endpoint that requires a capability issued by dovra; connections carrying a web Origin header are refused; issuing a new capability disconnects the previous controller. Other programs running as the same Windows user are outside this protection.
  • Retrying launch with the same idempotency key returns the original instance instead of starting a second one.
  • Defined but not available in this version, and refused with UNSUPPORTED_CAPABILITY rather than accepted without effect: device/region blueprints, proxies, a standard diagnostics mode, native storage export/import, restoring the last session, ephemeral profile copies, extensions.
  • It is a Node.js program (Node.js 18 or later), not a standalone executable. Capabilities are keyed to the SHA-256 of the browser files; this version knows the beta-20260924 browser.
• skills/dovra-browser/scripts/launch.js no longer falls back silently to bare settings when a profile preset cannot be resolved, and no longer rewrites profile-id characters (two different ids could share one data folder); it now stops with an error in both cases.

Downloads

• Dovra-Toolkit-beta-20260925.zip: companion toolkit with the integration command line; no browser included (168599 bytes, SHA-256 0cb94960df0466f7337c94bd80fb6a8fee6b1b0da62389dfc09e5be2f3c801b5).
• SHA256SUMS.txt: SHA-256 checksum of this batch's file.
• Browser (unchanged): Dovra-Beta-20260924-win-x64.zip (179475974 bytes, SHA-256 8aa6517d307f509a14c4aec49aa871c337a0ce7fbbedb7c28e509432e87d18a0), with its component source, relinking and LGPL modification archives under https://dl.dovra.dev/beta-20260924/ as listed in SOURCE-MATERIALS.md.

Verified scope

Tested environment: Windows Server 2022 x64 (OS build 20348), Node.js 24.12, playwright-core 1.63.0, browser files of batch beta-20260924 (chrome.dll SHA-256 411c27ab…3991, chrome.exe e409e52a…93fd).

• The toolkit's own test suite (node cli/test/run-tests.js --browser-dir <browser package> --playwright <playwright-core>) passed 38 checks against that browser: strict configuration and path rules (including a junction in the profile path, device names, UNC paths, and spaces, commas and CJK characters), unknown builds, headless and windowed launches, Playwright connectOverCDP through the control endpoint, capability, Origin and Host rejection, one controller at a time, idempotent retries including two simultaneous launches with one key, a second launch on a busy profile, a browser started outside dovra on the same folder, normal close, forced termination, an externally terminated browser (reported as crashed) and a lost supervisor process (reported as lost).
• The suite was also run from the extracted toolkit archive itself (same SHA-256 as the download), and dovra capabilities, launch with a start URL and close (clean exit, saved) were run against the extracted Dovra-Beta-20260924-win-x64.zip package layout.
• Closing an instance that crashed or was terminated is reported as CLOSED_UNSAVED rather than success.
• An independent review of the command line was performed before release (three rounds; the first found a blocking issue in how the command line authenticates to its per-instance supervisor, fixed before release).
• Not exercised: the startup-timeout path (the handshake completed in about half a second on the test machine), clean Windows 10/11 client machines, other Node.js versions.

Known limitation carried over from the browser: Playwright page.setContent() times out because this build does not report console events; use page.goto() or page.evaluate().

Use Dovra for your own applications, authorized tests and automation permitted by the service you access. See the use principles.