Repository navigation
Oya Browser v1.0.211
Deployment status
The web/server and cloud browser runtime are live at v1.0.211. Production health and readiness return HTTP 200, and SiteTwin can reach the Oya API. The official browser snapshot passed a fresh CDP capture/replay smoke test.
Desktop installers are pending: Windows needs an approved Azure Public Trust signing profile; GitHub could not allocate a hosted macOS runner. Existing production desktop downloads and update feeds are preserved. SDK, CLI and MCP publication remain pending the full release workflow.
Server deployment: https://github.com/OyadotAI/oya-browser/actions/runs/42086211332
Changed
- Added equal Technical setup choices for Oya sign-in, local agents and model API keys. Local-agent status now matches this browser, launch actions keep a practical GitHub test prompt ready, and Gemini, Claude API and OpenRouter keys receive a bounded provider test.
- Simplified desktop setup into illustrated Technical, Non-technical and AI expert choices, with short instructions, confirmed connection progress, Claude Code subscription guidance and a visual control-plane walkthrough. Import and default-browser choices no longer interrupt first use.
- Required timestamped Windows signing and verified installer/application signatures before release upload. Windows releases now fail when signing credentials are missing.
Fixed
- Restored standard CDP browser-session attachment so clients can create independent page CDP sessions, with scoped events and cleanup that preserve other attachments. Iframe and nested worker sessions now keep independent identities for each page attachment. Approved page commands run concurrently within a fixed limit, so an unfinished response-body read cannot stall the crawl. Response fulfillment now unblocks intercepted navigations instead of waiting behind them.
- Prepared Windows releases for protected Azure managed signing with GitHub OIDC, exact publisher verification and a non-publishing signing probe.
- Corrected meeting microphone, camera and screen-sharing permission routing across browser windows. Added device-specific macOS recovery and distinguished permission denial from unavailable desktop sources.
- Opened macOS development sessions through Launch Services so Oya receives its own microphone and camera consent, with private startup logs and explicit application lifetime.
- Added local Chrome/Edge bookmarks and history import with explicit profile selection, partial-result reporting and no external SQLite dependency. Protected Windows signed-in sessions still require signing in directly in Oya.
- Corrected Windows local-agent executable discovery and VS Code configuration paths while keeping credentials out of shell commands.
All release notes: https://oyabrowser.com/release-notes