Concept
Authenticated state that outlives one navigation.
A session is the authenticated browser state a workflow leaves behind or reuses — stored cookies and profile state that a later health action can confirm remains usable.
Definition#
In production runs the executor retains the authenticated state a completed login produced; a later health action confirms the stored session remained usable rather than logging in again. Locally, the CLI exposes the same idea through the browser profile directory: pass --user-data-dir <dir> to weles open to reuse a persistent profile across navigations.
Imported session references stay on one host#
An imported trajectory can retain browser, os, locale, headless, proxy, and session_label configuration. Weles imports the label, not the browser profile or cookies behind it, and binds the new draft to one exact managed worker hostname. If that draft is later reviewed and activated, saved-task execution refuses it on a different OS hostname before starting a browser.
Credentials never enter prompts or logs#
Sessions authenticate through scoped Skarbiec grants. API keys and passwords move through the Skarbiec lifecycle — acquire, adopt, rotate, reset, verify — without plaintext ever touching a prompt or a log. Workflow input carries opaque credentialRefs only; their resolution belongs to the executor's secret boundary.