Saved sessions

A session is a saved browser identity — a logged-in account Bureau can drive. Once saved, you pass its id to scrape, browser_act, and the social_* tools to act as that account. Sessions live under ~/.agentproto/bureau/sessions (override with BUREAU_SESSIONS_DIR).

Discover and save

# See which Chrome profiles look like usable identities
bureau session scan

# List the platform accounts a profile is logged into
bureau session accounts "Profile 1"

# Bridge a Chrome profile's cookies into a saved session
bureau session save my-x --profile "Profile 1" --platform x

# Or mint a Bureau-owned login (no Chrome cookie bridging)
bureau session login my-linkedin --platform linkedin --auto

Supported platforms include x, linkedin, reddit, tiktok, and more, depending on the adapter.

Inspect and manage

bureau session list           # list saved sessions
bureau session show my-x      # session details + live login status
bureau session solve my-x --url <url>   # human-in-the-loop: clear an anti-bot wall
bureau session rm my-x        # remove a saved session

Keeping sessions fresh

Two mechanisms, exposed as CLI commands and as MCP tools:

• Re-sync from Chrome (session_sync_from_chrome) — for chrome-sourced sessions, re-pull and re-decrypt the declared domains' cookies from the pinned Chrome profile and stamp the refresh time. Secret-free. Owned/Guilde sessions return no-chrome-strategy — use re-auth instead.
• Re-authenticate (session_reauth) — for Bureau-owned sessions, log back in from a stored credential (resolved server-side from env or Keychain, never passed in). If a 2FA/challenge is hit, it returns needsHuman:true with the headful command to finish by hand. Store a credential first with bureau creds set — see Credentials.

Seeing what's live

The bureau_sessions MCP tool lists saved identities (metadata only — no cookies), and bureau_tabs lists the tabs currently open per session. See MCP tools · Sessions & credentials.