adopt-session

Adopt Session

Safety Rule

Only use this for the user's own authorized accounts and active owner-approved session portability. Never print cookies, tokens, storage values, auth headers, or raw browser state.

Required Consent

Every browser_adopt_session call must pass:

{"i_authorize_this_session": true}

This is an explicit owner-consent gate. Do not set it unless the user has asked to move their own authenticated session into their own Shade slot.

Live Handoff Prerequisite

live_handoff cannot attach to a normal browser that was already launched without remote debugging. The owner must launch the source Chromium-family browser with a CDP port, or use a Shade-provided helper that does the same.

Example source launch shape:

google-chrome --remote-debugging-port=9222 --user-data-dir="$HOME/.cache/shade-auth-source"

Then pass:

{"source_cdp_endpoint": "http://127.0.0.1:9222"}

Workflow

1. Confirm the account/workspace and that the user owns or is authorized to use the session being moved.
2. Confirm the target Shade slot is owned by this session.
3. If using hosted HTTP mode, check that the tenant has explicitly been granted browser_adopt_session; the tool is gated off by default.
4. For live handoff, have the owner log in through the CDP-enabled source browser, then call:

{
  "mode": "live_handoff",
  "slot": 0,
  "domains": "example.com",
  "source_cdp_endpoint": "http://127.0.0.1:9222",
  "i_authorize_this_session": true
}

1. For local profile import, call:

{
  "mode": "profile_import",
  "slot": 0,
  "domains": "example.com",
  "browser": "auto",
  "profile": "auto",
  "i_authorize_this_session": true
}

1. Verify by safe navigation or a read-only readiness check. Report only counts, domains/origins, cookie names, and pass/fail status.