preview-v0.6.3

Tabora Browser 0.6.3

Windows x64 preview with a bundled runtime, MCP browser control and signed package updates. Git and a system Node installation are not required.

Install

1. Download tabora-0.6.3-windows-x64.zip and extract the complete archive.

2. From the extracted folder, run:

   .\tabora.exe install --channel preview --auto-update

3. In the intended Chrome/Edge profile, open its extensions page, enable Developer mode and select Load unpacked. Choose the installed extension-unpacked directory printed by setup.

4. Reconnect your MCP client and verify:

   & "$env:LOCALAPPDATA\Programs\TaboraBrowser\tabora.exe" doctor --require-profile

Chrome Web Store installation is not required for this path. The Store item is awaiting review and is not published.

Updates

--auto-update enables verified installation of newer preview/stable releases between tasks. Omit it for notifications only. While the broker runs, checks start after 30 seconds and repeat every six hours. The updater verifies the signed release manifest, hashes and payload inventory, then coordinates host activation and unpacked-extension reload.

Reconnect your MCP client when requested to load the new server code. Changed browser permissions or missing profile connections can require user action. Automatic installation is not a guarantee of uninterrupted MCP connections.

Existing standalone users can opt in without resetting profile or vault settings:

& "$env:LOCALAPPDATA\Programs\TaboraBrowser\tabora.exe" install --channel preview --auto-update

Changes

• Separate Store upload ZIP and exact Store identity support.
• Explicit, reversible migration between unpacked and Store distributions.
• Store-channel host updates retain legacy unpacked files and preserve local data.

Browser CI and standalone packaging/update checks passed for this release. Preview ZIP manifests use Ed25519 signatures; this release does not include an Authenticode-signed setup EXE. The extension UI is Czech.

Installation, updates and recovery · Full changelog

preview-v0.6.2

Windows x64 preview of standalone installation and signed remote updates.

Install without Git or Node

1. Download tabora-0.6.2-windows-x64.zip below and extract the complete archive.
2. Run tabora.exe install --channel preview. Updates default to notifications; add --auto-update to opt into installation between tasks.
3. In the intended Chrome profile, use Load unpacked once with the printed extension-unpacked directory. Keep the same extension identity when migrating an existing installation.
4. Reconnect your MCP client and run the installed tabora.exe doctor --require-profile.

Existing source installation: run the extracted package with install --migrate-from "C:\permanent\tabora-browser" --channel preview. Finish active work first. Profile settings, origin restrictions and the separate encrypted vault are retained; the vault is not automatically unlocked.

Updates and verification

The exact release-manifest.json bytes are signed with Ed25519; the public trust root is embedded in the package and committed in release-trust.json. The host verifies the signature, platform/contract, release sequence, payload size, SHA-256 and file inventory before activation. Checksums alone do not authenticate the publisher.

MCP exposes browser_update_check, browser_update_prepare, browser_update_apply and browser_update_status. A running older MCP process requires reconnect after activation. Browser verification remains pending until a compatible profile is actually connected; interrupted writes are never replayed automatically.

This is a ZIP-only preview. There is no Authenticode-signed Windows installer or Chrome Web Store package in this release. Stable publication remains gated on the Windows signing certificate and installer validation.

The release pipeline tests the real ZIP without system Node/Git on PATH and exercises an offline version transition, program repair, native messaging and interactive MCP. These tests do not replace full clean-Windows installer validation.

See installation and release operations.

Fixes in 0.6.2

• Large payload downloads now have one bounded 15-minute deadline across redirects and streaming. Small metadata checks retain a two-minute deadline. Signature, size, hash and archive checks are unchanged.
• Timeout failures report update_download_timeout instead of a generic preparation error. The issue was reproduced on a real client: a 382 MB package had downloaded 284 MB when the previous two-minute limit aborted it.
• Source browser integration tests now refuse packaged/foreign native launchers before starting a test profile. A packaged launcher intentionally uses its installation's state directory; a test environment override cannot isolate that host.
• Source tests passed: 190 unit tests, 4 setup tests and full Windows browser/native/MCP CI. Packaged install/repair and offline update checks also passed before publication.

If an older updater hits the two-minute limit, download/extract this ZIP and use its fresh tabora.exe install --root ORIGINAL_INSTALL_DIRECTORY to bootstrap the corrected version. Finish active work first. Do not remove an existing extension or discard its data. A legacy source broker may still require a one-time handoff before coordinated maintenance is available.

Connected-profile verification

On 4 November 2026 the existing user installation was upgraded from 0.6.0 to 0.6.2 using the corrected maintenance downloader to bootstrap the old timeout, then the normal signed staged-update apply path. The ordinary Chrome extension reloaded automatically. A fresh installed MCP connection reported completed; doctor --require-profile passed and host/extension both reported version 0.6.2 with the same build fingerprint. Profile UUID/settings, the state directory, restored provider configuration and the encrypted vault bytes were preserved by this update. The previous program version remains available for rollback.

preview-v0.6.1

Windows x64 preview of standalone installation and signed remote updates.

Install without Git or Node

1. Download tabora-0.6.1-windows-x64.zip below and extract the complete archive.
2. Run tabora.exe install --channel preview. Updates default to notifications; add --auto-update to opt into installation between tasks.
3. In the intended Chrome profile, use Load unpacked once with the printed extension-unpacked directory. Keep the same extension identity when migrating an existing installation.
4. Reconnect your MCP client and run the installed tabora.exe doctor --require-profile.

Existing source installation: run the extracted package with install --migrate-from "C:\permanent\tabora-browser" --channel preview. Finish active work first. Profile settings, origin restrictions and the separate encrypted vault are retained; the vault is not automatically unlocked.

Updates and verification

The exact release-manifest.json bytes are signed with Ed25519; the public trust root is embedded in the package and committed in release-trust.json. The host verifies the signature, platform/contract, release sequence, payload size, SHA-256 and file inventory before activation. Checksums alone do not authenticate the publisher.

MCP exposes browser_update_check, browser_update_prepare, browser_update_apply and browser_update_status. A running older MCP process requires reconnect after activation. Browser verification remains pending until a compatible profile is actually connected; interrupted writes are never replayed automatically.

This is a ZIP-only preview. There is no Authenticode-signed Windows installer or Chrome Web Store package in this release. Stable publication remains gated on the Windows signing certificate and installer validation.

The release pipeline tests the real ZIP without system Node/Git on PATH and exercises an offline version transition, program repair, native messaging and interactive MCP. These tests do not replace full clean-Windows installer validation.

See installation and release operations.

Observed remote update result — 4 November 2026

A separately installed 0.6.0 package discovered this published 0.6.1 release through real MCP, emitted the update notice, downloaded the actual GitHub payload, verified its signature/hash/inventory and activated the new host. The state binding and previous rollback version were retained. The old MCP reported mcp_restart_required; a freshly started MCP reported profile_connection_required because this isolated update test had no connected browser. This is not a claim of a full ordinary-Chrome profile migration.

The packaged release checks and browser CI passed for this tag. The first tagged browser attempt exposed a catalog-fixture timing race; its rerun passed, and main now synchronizes the fixture on explicit refresh. Future publication also waits for passing browser CI on the exact tag.

preview-v0.6.0

Windows x64 preview of standalone installation and signed remote updates.

Install without Git or Node

1. Download tabora-0.6.0-windows-x64.zip below and extract the complete archive.
2. Run tabora.exe install --channel preview. Updates default to notifications; add --auto-update to opt into installation between tasks.
3. In the intended Chrome profile, use Load unpacked once with the printed extension-unpacked directory. Keep the same extension identity when migrating an existing installation.
4. Reconnect your MCP client and run the installed tabora.exe doctor --require-profile.

Existing source installation: run the extracted package with install --migrate-from "C:\permanent\tabora-browser" --channel preview. Finish active work first. Profile settings, origin restrictions and the separate encrypted vault are retained; the vault is not automatically unlocked.

Updates and verification

The exact release-manifest.json bytes are signed with Ed25519; the public trust root is embedded in the package and committed in release-trust.json. The host verifies the signature, platform/contract, release sequence, payload size, SHA-256 and file inventory before activation. Checksums alone do not authenticate the publisher.

MCP exposes browser_update_check, browser_update_prepare, browser_update_apply and browser_update_status. A running older MCP process requires reconnect after activation. Browser verification remains pending until a compatible profile is actually connected; interrupted writes are never replayed automatically.

This is a ZIP-only preview. There is no Authenticode-signed Windows installer or Chrome Web Store package in this release. Stable publication remains gated on the Windows signing certificate and installer validation.

The release pipeline tests the real ZIP without system Node/Git on PATH and exercises an offline version transition, program repair, native messaging and interactive MCP. These tests do not replace full clean-Windows installer validation.

See installation and release operations.

Initial packaging preview. Use preview-v0.6.1 for the browser test fix that makes missing-provider checks independent of SDK login.