Skip to content

docs: clarify compare API use case for local automation#386

Closed
kaizeenn wants to merge 1 commit into
aaronlab:mainfrom
kaizeenn:docs/improve-cli-json-example-20260514
Closed

docs: clarify compare API use case for local automation#386
kaizeenn wants to merge 1 commit into
aaronlab:mainfrom
kaizeenn:docs/improve-cli-json-example-20260514

Conversation

@kaizeenn
Copy link
Copy Markdown
Contributor

Summary\n- add one sentence in Browser Use guide clarifying when local compare API is preferred over CLI output\n- mention local dashboards, scripts, and automation preflight checks needing the same first-divergence JSON payload\n- extend metadata test assertions to cover the new sentence\n\n## Linked issue\n- Closes #384\n\n## Verification\n- ✅\n- ⚠️ unavailable in this environment ()\n- ⚠️ unavailable in this environment ()

@aaronlab
Copy link
Copy Markdown
Owner

Thanks for sending this. This overlaps with #385, which was opened by the contributor who first claimed #384 and has now been merged.

I am closing this PR as a duplicate so the queue stays clear. The scope and direction were right; the only reason for closing is that the issue has already been resolved.

@aaronlab aaronlab closed this May 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Docs: explain compare API use case in Browser Use guide

2 participants