glass-browser 0.2.2

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
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76

# Bot protection and consent controls

Glass does not hide browser automation. It does not spoof fingerprints, solve
CAPTCHAs, evade bot checks, or rotate identities.

Use a site-approved access path.

## If you operate the site

Register Glass as an allowed client. Possible controls include:

- verified bot registration;
- IP allowlisting for a known CI or staging range;
- an application token checked by site middleware; and
- a documented API.

Use the site API when it provides the required operation. An API has a versioned
contract and does not depend on page layout.

## Use an authenticated profile

A site may allow an authenticated session where it blocks an unauthenticated
browser. Use a persistent profile only when your deployment policy permits it:

```console
glass profiles create work
glass --headed --profile work navigate https://example.com/login
glass --profile work navigate https://example.com/dashboard
```

Profiles contain cookies and storage. Protect them.

Glass does not automate multi-factor authentication as a bypass. If the site
requires a new verification step, stop and complete the approved flow.

## Consent controls

Glass has bounded helpers for recognized OneTrust and Cookiebot controls.

| Framework | Control |
|---|---|
| OneTrust | A recognized visible consent button. |
| Cookiebot | A recognized visible consent button. |

The helper returns `dismissed`, `no_consent_found`, or
`unrecognized_framework`. It does not click generic text matches.

A consent helper is a page interaction. It is not a bot-protection bypass.

## Polite policy

Use the optional `polite` policy for public pages:

```console
glass --policy polite navigate https://example.com/public-page
```

The policy checks `robots.txt`, applies a bounded delay, and identifies
requests with the Glass user agent. A robots error or disallowed path fails
closed.

The policy does not bypass bot protection.

## Unsupported actions

Glass does not provide:

- fingerprint spoofing;
- CAPTCHA solving;
- anti-bot evasion;
- `navigator.webdriver` removal;
- user-agent rotation; or
- proxy identity rotation.

If a site blocks the supported access path, contact the site operator or use its
documented API.