Persistent multi-Profile browser
Isolated browser Profiles, proxy assignment and local-first Profile state.
Product roadmap
This roadmap separates what is available now from near-term direction and longer-term exploration. Dates are not promised here; the Release Center is the source of truth for shipped builds.
Now
These are shipping product areas that should be evaluated as current capabilities, not roadmap promises.
Isolated browser Profiles, proxy assignment and local-first Profile state.
Reusable workflows, tasks, scheduling, concurrency, verification and recovery-oriented automation.
AI/tool integration through MCP plus developer access through CDP, User Scripts and Puppeteer.
Compatible browser extensions plus built-in trusted User Script workflows.
Support Center, diagnostics, known issues, Release Center and public changelog.
Windows 64-bit is the current published desktop platform.
Next
These are direction areas, not guaranteed release dates. Priorities can change based on reliability, compatibility and user feedback.
Continue hardening browser lifecycle, Profile state, automation recovery, extension compatibility and developer APIs.
Improve capability discovery, tool truth, stable resource identity, permissions and long-running workflow support.
Keep Browser API, Automation Studio, Support and product facts synchronized with the current build.
Improve large Profile sets, scheduling, diagnostics and management workflows without sacrificing local control.
Exploring
Exploration is not a commitment. These areas need product, engineering and support validation before any release promise.
macOS/Linux are not currently published and remain an exploration area rather than a promised date.
Potential collaboration/RBAC improvements beyond the current local-first product strengths.
Additional connectors and automation integrations where they can remain secure and maintainable.
Source of truth
The Release Center and changelog are the source of truth for what actually shipped.