Browserbase Sessions Skill

Browserbase Sessions Skill

Manage persistent cloud browser sessions via Browserbase. This skill creates browser sessions that preserve authentication (cookies, local storage) across interactions, automatically solve CAPTCHAs, and record sessions for later review.

Agent Checklist (Be Proactive)

• If BROWSERBASE_API_KEY or BROWSERBASE_PROJECT_ID is missing, ask the user for them (and tell them where to find them). Do not run Browserbase commands until both are configured.
• If commands fail due to missing Python deps (ImportError for browserbase / playwright), run:
  • python3 {baseDir}/scripts/browserbase_manager.py install
  • Then retry the original command.
• Ask the user what they want to persist and how they want to organize it:
  • Workspace per app/site (isolation): github, slack, stripe
  • Workspace per task/project (multi-site workflow): invoice-run, lead-gen, expense-recon
• Workspaces persist:
  • Login state via Browserbase Contexts (cookies + storage)
  • Open tabs (URL + title snapshot) so you can restore where you left off
• Prefer workspace commands (create-workspace, start-workspace, resume-workspace, stop-workspace) over raw session commands when the user wants the browser to stay open across chat turns.
• Prefer direct interaction commands (list-tabs, new-tab, switch-tab, close-tab, click, type, press, wait-for, go-back, go-forward, reload, read-page) before falling back to execute-js.
• If a workspace/session has a pending_handoff, check it first before doing anything else:
  • python3 {baseDir}/scripts/browserbase_manager.py handoff --action check --workspace <ws>
  • If not done, resend suggested_user_message and stop.
• Whenever a browser is opened (start-workspace, resume-workspace, or create-session), immediately share the human remote-control link:
  • Prefer human_handoff.share_url from command output.
  • Prefer human_handoff.share_text / human_handoff.share_markdown when replying to the user.
  • Fallback to human_control_url.
  • If missing, run live-url and share its human_handoff.share_url.
• When you need the user to perform a manual step (SSO/MFA/captcha/consent screens), use a handoff with a completion check:
  • Set: python3 {baseDir}/scripts/browserbase_manager.py handoff --action set --workspace <ws> --instructions "<what to do>" --url-contains "<post-step url fragment>" (or --selector/--text/--cookie-name/...)
  • Verify later: python3 {baseDir}/scripts/browserbase_manager.py handoff --action check --workspace <ws> (or --action wait)
• When closing, use stop-workspace (not terminate-session) so tabs are snapshotted and auth state is persisted.

Prompt-Optimized Response Patterns

Use short, consistent responses so users always know next actions.

When credentials are missing:

I need your Browserbase credentials before I can open a browser.
Please provide:
1) BROWSERBASE_API_KEY