diff --git a/docs/browser-use-debugging.html b/docs/browser-use-debugging.html index 2111760b..d6c780c9 100644 --- a/docs/browser-use-debugging.html +++ b/docs/browser-use-debugging.html @@ -423,6 +423,7 @@

Compare failed and successful Browser Us browsertrace compare <failed_run_id> <success_run_id> --json

While the local BrowserTrace UI is running, local wrappers and tools can request the same first-divergence payload through the web API:

curl http://127.0.0.1:3000/api/compare/<failed_run_id>/<success_run_id>
+

The API endpoint is useful for local dashboards, scripts, or automation preflight checks that need the same first-divergence JSON payload.

Example compare output:

$ browsertrace compare failed-local-html-upload good-local-html-upload
 First divergent step: 3
diff --git a/tests/test_metadata.py b/tests/test_metadata.py
index 0b7cf249..d8b3c8b4 100644
--- a/tests/test_metadata.py
+++ b/tests/test_metadata.py
@@ -4004,6 +4004,8 @@ def test_browser_use_guide_documents_compare_run_metadata_checklist():
     )
     assert "local BrowserTrace UI is running" in section
     assert "same first-divergence payload" in section
+    assert "local dashboards, scripts, or automation preflight checks" in section
+    assert "same first-divergence JSON payload" in section
     assert "first divergent step" in section
     assert "Example compare output:" in section
     assert "$ browsertrace compare failed-local-html-upload good-local-html-upload" in section