Changelog #036

Announcing Changelog #036

Hey everyone. This one covers a longer stretch than usual: mostly billing and Wallet work, more detail in the session viewer, and a run of reliability fixes across session routing, archives, and browser connections.

⭐ New

  • Wallet now has purchase history and payment-method management: printable invoices and receipts, default-card selection, and removal of any card that is not the default.

🔧 Improvements

  • The Sessions API now returns active, remaining, and total concurrency quota as response headers, both when a session is created and when a request hits the concurrency limit.

  • The session viewer has a fullscreen live view and keyboard seeking, plus reworked session details and timeline controls.

  • A new Sessions API configuration guide collects recipes for proxies, CAPTCHA solving, timeouts, browser behavior, and network identity.

  • The billing dashboard shows assigned Enterprise credits and usage rates, and session details now include proxy analytics per session.

🐛 Bug Fixes

  • Fixed routing, authentication, and WebSocket forwarding for session logs and agent traces on Box-backed sessions.

  • Fixed WebSocket proxy cleanup so heavy connection load no longer exhausts API file descriptors, which caused timeouts and failed upgrades.

  • Fixed session archive downloads so file changes trigger a fresh archive and concurrent downloads wait for the latest rebuild.

  • Fixed repeated /context polling that could saturate browser file operations and slow down the whole browser machine.

  • Fixed three billing problems: a restored balance now clears funds-based blocks automatically, a temporary Metronome failure no longer blanks the full billing dashboard, and concurrent signup requests no longer leave organizations blocked.

  • Corrected region validation so requests targeting regions without live capacity return a clear validation error instead of a retryable 503.

  • Fixed log redaction so credentials inside URL values are stripped before API and managed-browser telemetry is recorded.