A direct browser connection should not pretend it is somewhere else. A Windows shutdown should not leave a browser tree behind. And if an agent is already looking at an authenticated PDF, it should be able to save that document without starting an unrelated fetch flow.
v1.16.0 makes those paths more honest and dependable. It also updates the bundled OpenClaw plugin for the current OpenClaw plugin API.
Direct connections use honest identity defaults
Direct sessions no longer default to a San Francisco location, en-US locale, or America/Los_Angeles timezone. Proxy-backed sessions keep Camoufox GeoIP identity behavior.
If you need a specific direct-session identity, set CAMOFOX_LOCALE and CAMOFOX_TIMEZONE together. Camofox validates that pair rather than applying a partial identity.
Windows cleanup reaches the browser tree
On Windows, server-owned Camoufox descendants are now cleaned up when the server shuts down. Cleanup checks the captured process tree and process start time before using a scoped taskkill /T /F, so it does not target unrelated browser processes.
The release is validated both with a focused Windows cleanup test and the complete browser E2E suite on GitHub-hosted Windows.
SOCKS4 and SOCKS5 proxies
Set PROXY_PROTOCOL to http, https, socks4, or socks5. The default remains http. The setting applies consistently to Playwright, rotating/backconnect proxies, and CLI proxy URLs.
Save the authenticated PDF already open in a tab
POST /tabs/:tabId/fetch-current-resource retrieves only the current HTTP(S) tab URL through that tab's authenticated request context, accepts PDFs only, and saves the artifact through the existing downloads API. Stored PDF artifacts are capped at 50 MB.
OpenClaw compatibility
The included OpenClaw plugin now uses the current scoped gateway-method API and logger contract. Its manifest uses the current supported schema, allowing the ClawHub validation to pass.
Follow along
For future Camofox updates, follow @pradeep24 on X.