Astra 1.0.0

Astra 1.0.0

Astra 1.0 is the first complete product slice: a stranger can launch a packaged build, browse real sites, organize tabs into isolated named workspaces, jump through the local command bar, and inspect real privacy/resource signals. It adds split browsing, hibernation, Alt-hover Peek, reviewed unpacked MV3 extensions, encrypted per-site Boosts and a fully optional local page assistant.

Verification

The release candidate must pass npm run verify, the separate packaged executable smoke test, npm audit --omit=dev, and SHA-256 generation before artifacts are published. Linux verification is performed locally and in CI; Windows x64 and macOS x64/arm64 packages are built and exercised on native GitHub runners.

Local Linux verification passed on 2026-09-09. Astra-1.0.0.AppImage SHA-256 is 46529078fb4b776b7c6e617a416479d78f48e6cec9ed4a327d2d86ca49f6e5e0; astra-browser_1.0.0_amd64.deb SHA-256 is de365152b086a6e58dc92d5f009aced0acefe16f43c8bf6ca793b6b6f1c39278. The actual AppImage passed packaged browsing, sandbox isolation, license and command-bar checks.

Native CI run 34382766909 passed on Windows x64, macOS Apple Silicon and macOS Intel. Every job ran the full source suite, built its native installers, launched the packaged executable, rendered a real local HTTP page in Chromium, checked renderer isolation and exercised the command bar. The Linux browser gate also passed on the exact release commit. Checksums for every attached artifact are included in SHA256SUMS-1.0.0.txt.

Trust and limitations

There is no telemetry, updater, account or cloud dependency. Records persist only when an OS key store or passphrase vault can protect them. Website state is ephemeral. The tracker list is a baseline. Extensions are unpacked-only and limited by Electron's Chrome API compatibility. Community binaries are not commercially signed/notarized. The assistant is local extractive software, not an autonomous agent. These limits are visible because overstating them would violate Astra's transparency goal.