You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -109,9 +109,9 @@ For compact AI/coding-agent troubleshooting context, use
109
109
project links and prompts.
110
110
111
111
- The first-run troubleshooting checklist walks through `browsertrace doctor`, `browsertrace demo`, `browsertrace list`, `browsertrace show`, and public-safe export; see the [checklist](examples/#first-run-troubleshooting-checklist).
112
-
- The live static demo and public-safe demo export let you inspect a trace before installing anything; open the [live static demo](https://aaronlab.github.io/browsertrace/) or download [`browsertrace-demo-public.html`](https://github.com/aaronlab/browsertrace/releases/download/v0.1.14/browsertrace-demo-public.html).
112
+
- The live static demo and public-safe demo export let you inspect a trace before installing anything; open the [live static demo](https://aaronlab.github.io/browsertrace/) or download [`browsertrace-demo-public.html`](https://github.com/aaronlab/browsertrace/releases/download/v0.1.15/browsertrace-demo-public.html).
113
113
- The command cheat sheet summarizes `browsertrace doctor`, `browsertrace demo`, `browsertrace list`, `browsertrace show`, and public-safe export commands; see the [cheat sheet](examples/#browsertrace-command-cheat-sheet).
114
-
- The v0.1.14 release notes summarize what changed in the pinned GitHub tag; read the [v0.1.14 release notes](https://github.com/aaronlab/browsertrace/releases/tag/v0.1.14).
114
+
- The v0.1.15 release notes summarize what changed in the pinned GitHub tag; read the [v0.1.15 release notes](https://github.com/aaronlab/browsertrace/releases/tag/v0.1.15).
115
115
- The PyPI tracking issue is the source for publishing status while install commands stay pinned to the GitHub tag; follow the [PyPI tracking issue](https://github.com/aaronlab/browsertrace/issues/5).
116
116
-`uvx` is the no-install trial path, and pinned GitHub-tag `pip install` is the persistent install path.
117
117
-`[ui]` is needed for the local web UI, while SDK-only install is enough for trace capture integrations.
@@ -147,13 +147,13 @@ If install or demo startup fails, use the
<p>Open <code>http://127.0.0.1:3000</code>, then inspect <code>demo: checkout agent fails on disabled button</code>. From a source checkout, <code>python examples/browser_use_callback_demo.py</code> records Browser Use-shaped callback steps without installing Browser Use.</p>
269
269
</section>
@@ -286,7 +286,16 @@ <h2>Attach it to a Browser Use agent</h2>
286
286
<section>
287
287
<h2>Callback compatibility</h2>
288
288
<p><code>attach_tracer</code> supports Browser Use agents that expose <code>register_new_step_callback</code>, plus older or forked agents with <code>on_step_start</code>, <code>on_step</code>, or <code>_new_step_callback</code> attributes.</p>
289
-
<p>Current Browser Use examples may also pass <code>on_step_start</code> or <code>on_step_end</code> directly to <code>agent.run(...)</code>. If your app is run-hook-only and does not expose an attachable agent callback, keep using <code>run.snapshot(...)</code> manually for now and comment on issue #11 with the Browser Use version and hook shape you need.</p>
289
+
<p>Current Browser Use examples may also pass <code>on_step_start</code> or <code>on_step_end</code> directly to <code>agent.run(...)</code>. For that run-hook-only path, use <code>create_run_hooks</code>:</p>
290
+
<pre><code>from browsertrace import Tracer
291
+
from browsertrace.integrations.browser_use import create_run_hooks
<p>The run-hook helper reads Browser Use history and browser-session summaries when they are available, then records the latest thought, action, extracted content, URL, title, tabs, and screenshot flag into the same local timeline. If your Browser Use version exposes a different hook shape, comment on issue #11 with the version and callback surface.</p>
0 commit comments