1. Create a profile
Give the profile a meaningfulname that is unique within your project.
2. Start a writer browser
Attach the profile byname or id. Set save_changes to true only when this browser owns writes to the profile.
3. Use and delete the browser
Navigate, authenticate, or complete the part of the workflow whose state you want to retain. Then delete the Kernel browser to save the state.4. Load the saved state
Create another browser with the same profile. Omitsave_changes to keep the stored profile unchanged during this run.
Control the starting tab
By default, a profile restores its saved tabs. Passstart_url to discard those restored tabs and open a specific page when the browser starts.
Managed Auth controls the tab state of profiles attached to auth connections. Each login or automatic reauthentication starts with one tab at the configured login URL, or at the domain homepage when no login URL is configured. Successful authentication saves the resulting tab state. Failed and canceled sessions leave the profile unchanged.Set
start_url when you create a browser if your automation requires a specific first page.Load a profile after browser creation
You can attach a profile to a running browser that was created without one. Loading the profile restarts Chromium, so reconnect your CDP or Playwright client afterward.start_url in the same update() call to collapse those restored tabs down to a single tab at the page you specify.