glass-browser 0.2.6

Local, revision-safe Chrome automation runtime for agents, with semantic observation, verified workflows, MCP, CLI, TUI, and Rust APIs
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

# Platform support and target certification

The release path publishes the crates.io package and a source-only GitHub
Release containing generated notes. It does not build or publish native release
binaries. Cross-compilation or source-level CI proves that code can build; it
does not prove browser launch, terminal startup, Unix-socket behavior,
filesystem permissions, or native sandbox behavior on another OS.

## Declared target inventory

The feature parity file is a declared implementation inventory. It does not
certify these targets by itself:

| Target | Native runner | Rust target | Browser source |
|---|---|---|---|
| Linux x86-64 | `ubuntu-latest` | `x86_64-unknown-linux-gnu` | Managed Chrome for Testing |
| Linux arm64 | `ubuntu-24.04-arm` | `aarch64-unknown-linux-gnu` | Installed system Chromium |
| macOS x86-64 | `macos-15-intel` | `x86_64-apple-darwin` | Managed Chrome for Testing |
| macOS arm64 | `macos-14` | `aarch64-apple-darwin` | Managed Chrome for Testing |

Linux ARM64 may also be reproduced on the project’s native OCI ARM64
environment when the hosted ARM64 runner is unavailable. That evidence is a
separate Linux ARM64 row. It must not replace the Linux x86-64 or macOS rows,
and it must record the installed Chromium package and version.

## Recorded Linux ARM64 evidence

A native Linux ARM64 check has been recorded for one validation environment.
Its scope is the checked-out source, the matching Rust target, and the
installed Chromium runtime. Other target rows require their own native checks.

Record the target environment, Rust target, browser version, and commands when
refreshing the evidence. See [Release evidence](release-evidence.md) for the
crates.io package and GitHub Release boundaries.

## Local reproduction

Run the platform-independent checks locally:

```console
cargo fmt --all -- --check
cargo test --all-targets --locked
python3 scripts/check-feature-parity.py
```

Run the native browser row only on a machine with the matching target and a
supported Chrome or Chromium installation:

```console
GLASS_E2E=1 cargo test --test browser_smoke --locked -- --nocapture --test-threads=1
```

Do not mark another target `certified` from a cross-compiled binary or
emulated browser run alone. A Linux ARM64 check is not a cross-platform release
claim.