Releases
v0.0.47
v0.0.47 - Browser Profiles
Compare
Sorry, something went wrong.
No results found
Published Packages
@evolvingmachines/e2b@0.0.47
@evolvingmachines/daytona@0.0.47
@evolvingmachines/modal@0.0.47
@evolvingmachines/sdk@0.0.47
evolve-sdk==0.0.47
Highlights
Added first-class managed browser profile support for reusable authenticated browser state.
Added .withBrowser({ profile: "..." }) for managed remote agent-browser runs.
Added browser profile clients for TypeScript and Python so users can list and delete reusable browser profiles from the SDK.
SDK
Added Evolve.browserProfiles().list() and Evolve.browserProfiles().delete({ profile }) in TypeScript.
Added Python browser profile helpers via evolve.browser_profiles.
Enforced that browser profiles are available only in managed remote browser mode.
Kept browser profile metadata scoped to the authenticated Evolve user and free of provider internals.
Profile Lifecycle
First use auto-creates an empty server-side browser profile for the authenticated Evolve user.
Existing profiles are reused by name and update their last-used metadata.
Browser state changes, including successful logins, are saved when the managed browser is stopped; callers should use kill() when done.
Profiles appear in Dashboard Secrets under Browser Profiles and in the SDK list APIs; raw cookies and storage stay server-side.
Documentation
Documented managed browser profile usage and lifecycle in the TypeScript and Python browser automation sections.
Synced Evolve skill reference docs from the updated public docs.
You can’t perform that action at this time.