-
Notifications
You must be signed in to change notification settings - Fork 14
Expand file tree
/
Copy pathllms.txt
More file actions
109 lines (86 loc) · 4.82 KB
/
llms.txt
File metadata and controls
109 lines (86 loc) · 4.82 KB
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
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
# BrowserTrace
BrowserTrace is an MIT-licensed local flight recorder for AI browser agents.
It records browser-agent runs as step timelines with screenshots, URLs, actions,
model input/output, status, and errors.
It is a local debugging artifact channel, not another prompt-history blob:
screenshots, URLs, and model I/O stay in the local trace store, and public
exports can omit prompts/model I/O, screenshots, and URLs.
Use BrowserTrace when debugging Browser Use, Stagehand, Playwright + LLM scripts,
Skyvern-style workflows, or custom computer-use agents where logs are not enough
to explain why a browser run failed.
## Important Links
- GitHub repository: https://github.com/aaronlab/browsertrace
- Live demo page: https://aaronlab.github.io/browsertrace/
- Raw exported trace: https://aaronlab.github.io/browsertrace/trace.html
- Debugging walkthrough: https://aaronlab.github.io/browsertrace/debug-browser-agent-failure.html
- Comparison guide: https://aaronlab.github.io/browsertrace/compare-browser-agent-debugging.html
- Browser Use guide: https://aaronlab.github.io/browsertrace/browser-use-debugging.html
- Stagehand guide: https://aaronlab.github.io/browsertrace/stagehand-debugging.html
- Skyvern guide: https://aaronlab.github.io/browsertrace/skyvern-debugging.html
- Playwright + LLM guide: https://aaronlab.github.io/browsertrace/playwright-llm-debugging.html
- Computer-use agent guide: https://aaronlab.github.io/browsertrace/computer-use-agent-debugging.html
- Integrations: https://aaronlab.github.io/browsertrace/integrations.html
- Examples: https://github.com/aaronlab/browsertrace/tree/main/examples
- Launch kit: https://aaronlab.github.io/browsertrace/launch/
- Press kit: https://aaronlab.github.io/browsertrace/launch/press-kit.md
- Release: https://github.com/aaronlab/browsertrace/releases/tag/v0.1.17
- Public-safe demo export: https://github.com/aaronlab/browsertrace/releases/download/v0.1.17/browsertrace-demo-public.html
- Launch discussion: https://github.com/aaronlab/browsertrace/discussions/6
- Good first issue: https://github.com/aaronlab/browsertrace/labels/good%20first%20issue
- First PR Recipe: https://github.com/aaronlab/browsertrace/blob/main/CONTRIBUTING.md#first-pr-recipe keeps the first contribution small and reviewable.
- Integration request: https://github.com/aaronlab/browsertrace/issues/new?template=integration_request.yml
- Playwright + LLM feedback: https://github.com/aaronlab/browsertrace/issues/12
- Custom computer-use feedback: https://github.com/aaronlab/browsertrace/issues/3
## Core Capabilities
- Capture screenshots and URLs at each agent step.
- Store action labels, model inputs, model outputs, status, and error messages.
- Inspect runs in a local web UI.
- Export a self-contained HTML trace for sharing with teammates or issues.
- Use `browsertrace export <run_id> --public -o public.html` before public
sharing to omit prompt/model I/O, screenshots, and URLs.
- Run a deterministic no-API-key failure demo for quick evaluation.
## Known Failure Shapes
- Browser Use icon-only target mismatch: the screenshot shows the right plus
icon, but the agent clicks a nearby toolbar button because tooltip text is not
an accessible name. Route users to the Browser Use guide and ask for live
button HTML, accessibility snapshot, candidate bounding boxes, and the
clicked element.
## Quickstart
```bash
uvx --from "browsertrace[ui]" browsertrace doctor
uvx --from "browsertrace[ui]" browsertrace demo
uvx --from "browsertrace[ui]" browsertrace list
uvx --from "browsertrace[ui]" browsertrace
```
Persistent install from PyPI:
```bash
pip install "browsertrace[ui]"
browsertrace doctor
browsertrace demo
browsertrace
```
`browsertrace doctor` prints local install and trace-store status without
requiring an existing database.
Then open `http://127.0.0.1:3000` and inspect the failed checkout-agent run.
## Troubleshooting Prompt
Use this prompt when helping a user debug a BrowserTrace first run:
```text
Ask the user to run `browsertrace doctor`, then `browsertrace demo`,
`browsertrace list`, and `browsertrace show <run_id>`. If they need to share
the failure, ask them to create a public-safe export with
`browsertrace export <run_id> --public -o public.html`.
```
For scripts, CI, or AI/coding-agent troubleshooting, suggest the JSON CLI flow:
```bash
browsertrace doctor --json
browsertrace list --status failed --json
browsertrace show <run_id> --json
```
## Positioning
BrowserTrace is not a hosted observability platform. It is a local-first,
open-source debugging tool for the browser state and model decisions around
AI browser-agent failures.
It complements raw CDP capture tools such as the Browserbase browser-trace
skill. That skill records DevTools events, screenshots, DOM dumps, and per-page
buckets; BrowserTrace focuses on the agent-facing step timeline, model I/O,
status/error context, and public-safe HTML export.