SESSIONS & CONTROL
Reuse a prepared browser with profile templates
A profile template is a snapshot of a browser you have already prepared. New browsers can copy it, including its saved logins, when you grant the required permission.
Choose between reuse and a copy
Start by deciding whether you need a copy. If the next task belongs in the same signed-in workspace, reopen the existing browser and let the agent continue there, with the cookies and local storage the previous task left behind.
A template is useful when several new browsers need the same starting setup, such as a prepared test workspace. A clone receives the profile state captured in the snapshot and has its own profile after creation. Later changes in the source browser do not update that old snapshot.
Prepare and save the profile
Record signed-in site only adds an inventory note so agents can find a browser. It does not sign you in or copy cookies. Save profile copies all saved logins and storage, not just the sites in that inventory. Persistent browsers already keep their own state without this step.
Prepare the source browser
Create a browser, take control, and set up the sites needed for this workflow. Check the signed-in accounts and finish unsaved edits.
Save the profile
Choose Save profile. A running source briefly pauses and resumes. Saving again updates its linked snapshot; Save as new profile creates a separate one.
Grant the permissions needed
Agents need seed:use to load profiles and seed:write to save or update them. Both are opt-in. Saving requires ownership, and an agent must wait for human control to end.
Load and check the copy
Pass the saved profile ID when creating a browser. Visit the sites you need and check their sessions. Set the new browser's proxy separately, if needed.
Check the new browser's sessions
Open the clone and visit each site that matters to the task. Copied site records begin as expected. They become confirmed only after the new browser checks the authenticated page.
Some websites invalidate copied sessions. If that happens, take control and sign in inside the new browser. A template saves preparation work when the site accepts the copy; it cannot guarantee that the session transfers.
| Term | Meaning |
|---|---|
| Profile template / seed | A snapshot of a prepared Chrome profile. Proxy settings are not included. |
| seed:use | The explicit agent scope required to list and clone templates. |
| seed:write | The separate scope for saving or updating a snapshot from an owned browser. |
| Expected site access | A copied record that still needs a check in this browser. |
| Confirmed site access | Authenticated UI was observed at the recorded time. |
A template ID is not permission
Agents do not receive seed:use by default. Knowing a seed ID does not grant access to it. Give this scope only to agents you trust with all the sessions the template holds.
Review old templates when an account changes or a workflow ends. Removing an agent's access does not erase logins from profiles it already cloned. Handle those browsers and the site's own sessions separately.
Docs behind this guide
Based on Tallylamp's documented behaviour. See the source for API details and release-specific settings.