Context
The examples README now has a concise bash public-safe export flow after #27. Windows users already have PowerShell setup snippets earlier in the file, but the new public-safe export section only shows a bash block.
Task
Add a short Windows PowerShell variant under the Public Export Flow section in examples/README.md. Keep it focused on creating a demo run, listing runs, and exporting a public-safe HTML file.
Suggested commands:
browsertrace demo
browsertrace list
browsertrace export <run_id> --public -o public.html
Also keep the safety note clear: --public omits prompts/model I/O, screenshots, and URLs, and BrowserTrace does not upload the file anywhere.
Acceptance criteria
examples/README.md includes a Windows PowerShell public-safe export flow near the existing Public Export Flow section.
- The text does not imply hosted sharing exists.
- Existing GitHub-tag install and
uvx commands stay on v0.1.14 while PyPI is pending.
- Run
uv run --python 3.11 --extra dev pytest -q before opening a PR.
Context
The examples README now has a concise bash public-safe export flow after #27. Windows users already have PowerShell setup snippets earlier in the file, but the new public-safe export section only shows a bash block.
Task
Add a short Windows PowerShell variant under the Public Export Flow section in
examples/README.md. Keep it focused on creating a demo run, listing runs, and exporting a public-safe HTML file.Suggested commands:
Also keep the safety note clear:
--publicomits prompts/model I/O, screenshots, and URLs, and BrowserTrace does not upload the file anywhere.Acceptance criteria
examples/README.mdincludes a Windows PowerShell public-safe export flow near the existing Public Export Flow section.uvxcommands stay onv0.1.14while PyPI is pending.uv run --python 3.11 --extra dev pytest -qbefore opening a PR.