Persistent Authenticated Sessions

Persistent identity slots let an agent return to a browser state you prepared or authenticated yourself. Only save and reload sessions for accounts you own or are authorized to operate.

Save a session

After signing in through an authorized workflow, call:

browser_save_session(name: "customer-portal-main", slot: YOUR_SLOT)

Shade stores cookies and local storage so a later run can resume without repeating the login ceremony.

Load a session in a later run

browser_claim_slot(session_id: "portal-maintenance")
browser_load_session(name: "customer-portal-main", slot: YOUR_SLOT)
browser_navigate(url: "https://portal.example/dashboard", slot: YOUR_SLOT)

If a site binds anti-bot clearance cookies to a short-lived challenge, drop those cookies during restore:

browser_load_session(name: "customer-portal-main", drop_cookie_names: "cf_clearance", slot: YOUR_SLOT)

Clone a prepared session

Clone only when the target account and site rules allow parallel browser identities:

browser_clone_session(name: "customer-portal-main", slots: "[2,3,4]")

Use cloned sessions for authorized agent runs that need the same prepared starting state across multiple slots.