Simplify browser routing example

[rgarcia]

Summary

• Drop typing casts and unused intermediate variables in examples/browser_routing.py
• Remove the streaming and try/finally blocks so it mirrors the node SDK's browser-routing example
• Verified the cleaned example runs end-to-end against production (status 200)

Test plan

• python examples/browser_routing.py prints status 200

---

Note

Low Risk
Low risk: changes are limited to an example script and only adjust how it demonstrates browser request APIs and cleanup behavior.

Overview
Simplifies examples/browser_routing.py to be a minimal browser-routing demo: removes typing casts, intermediate variables, and the with/try/finally streaming pattern.

The example now shows two request styles—browsers.request (raw httpx.Response) and browsers.curl (buffered JSON envelope)—and performs explicit session cleanup via delete_by_id.

^{Reviewed by Cursor Bugbot for commit 84cb2e3. Bugbot is set up for automated code reviews on this repo. Configure here.}

[firetiger-agent]

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

Any PR that changes the kernel API. Monitor changes to API endpoints (packages/api/cmd/api/) and Temporal workflows (packages/api/lib/temporal) in the kernel repo

Reason: Changes are limited to example code in examples/browser_routing.py, not to kernel API endpoints (packages/api/cmd/api/) or Temporal workflows (packages/api/lib/temporal).

To monitor this PR anyway, reply with @firetiger monitor this.

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is ON. A cloud agent has been kicked off to fix the reported issue. You can view the agent here.}

^{Reviewed by Cursor Bugbot for commit 84cb2e3. Configure here.}

[cursor]

Browser session leaks if request or curl fails

Low Severity

The previous code wrapped the browser usage in try/finally to ensure delete_by_id was called even on failure. The new code calls client.browsers.request() and client.browsers.curl() without any error handling, so if either raises an exception, delete_by_id is never reached and the remote browser session is leaked on the server. Since this is example code that users will copy, the missing cleanup pattern could lead to orphaned browser sessions in real applications.

 

^{Reviewed by Cursor Bugbot for commit 84cb2e3. Configure here.}