Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

Devin signs in once and remembers. Build a QA agent that tests behind your login with the Claude Agent SDK

Description and use

A QA agent that starts with a signed‑in browser profile and retrieves credentials from a vault outside the prompt speeds up testing and keeps passwords secure.

Problem

QA agents that log in on every run waste time on login pages and expose passwords in prompts.

Outcome

The QA agent runs quickly, never re‑enters passwords, and maintains authenticated state across CI runs.

Workflow

  • Create a Burrowbox machine with "browser":"full" to preserve sign‑in state across restarts.
  • Store the staging test account credentials in the machine’s vault using the browser_login tool.
  • Write a QA script that starts the machine, waits for it to be running, then uses the Claude Agent SDK to navigate the checklist, calling browser_login only when necessary.
  • Run the script in CI, letting the machine keep its state for 30 minutes before stopping automatically.

Evidence

A person logs in once through Devin's interactive browser, in the session's Desktop tab, and handles SSO redirects, MFA prompts and CAPTCHAs themselves. When they ask Devin to "save the browser profile", Devin zips the browser's cookies, localStorage and other Chrome profile data and attaches it to the organization's blueprint.

Source

The QA agent runs in your CI job with the Claude Agent SDK. It connects to a Burrowbox machine's MCP endpoint, works through a checklist in that machine's browser, and finishes with PASS or FAIL.

Source

  • Record date: 2026-10-13T15:41:23.887Z