Building a QA Agent That Persists Browser Sessions with the Claude Agent SDK
10/15/2026 — 10/15, 22:24·1 sources (all)·1 reports (all)
Key takeaways
- This article explores how to build a QA testing agent using the Claude Agent SDK while adopting Devin's approach of persisting browser profi…
Background & analysis
On October 13, 2026, DEV Community's AI section published a technical article on building persistent QA testing agents by combining the Claude Agent SDK with a browser-state technique borrowed from Devin, Cognition's AI software engineer. The piece addresses a friction point familiar to anyone doing test automation: having to sign in over and over on every run.
The article draws on Devin's documentation to explain the origin of the idea. Most web apps worth testing sit behind a login, and those docs describe how Devin gets past one without asking every time: a person signs in once through Devin's interactive browser, in the session's Desktop tab, personally handling SSO redirects, MFA prompts, and CAPTCHAs. When asked to 'save the browser profile,' Devin packages the browser's cookies, localStorage, and the rest of the Chrome profile into an archive for later reuse. Login credentials, site cookies, and TOTP codes for two-factor authentication can also be kept separately as Secrets.
The proposed approach applies the same persistence idea to a QA agent built on the Claude Agent SDK: cookie and localStorage state is saved between runs, so the agent can skip the login flow instead of repeating it each time. According to the author, this removes the recurring chore of dealing with SSO and CAPTCHAs at the start of every run and makes automated testing more efficient.
As of now, this is the only coverage of the topic — a single community tutorial describing a technique rather than a product launch — and no follow-up developments have been reported.
AI-generated from 1 reports · updated 6 hours ago
Latest turnThis article explores how to build a QA testing agent using the Claude Agent SDK while adopting Devin's approach of persisting browser profiles. By saving cookies and localStorage, the agent bypasses repetitive logins, SSO redirects, and CAPTCHAs across test runs.
Related AI tools
- Heat index
- 25
- All sources
- 1
- All reports
- 1
- First seen
- 6 hours ago
Reports on this story headlines open the original
This article explores how to build a QA testing agent using the Claude Agent SDK while adopting Devin's approach of persisting browser profiles. By saving cookies and localStorage, the agent bypasses repetitive logins, SSO redirects, and CAPTCHAs across test runs.
DEV Community · AIAI score 60
Other stories people are talking about
- Heat index 182NewAccenture caps employee Claude spending at $29 per month2 sources
- Heat index 205Claude Code Agent Bypasses Isolation and Deletes Files5 sources
- Heat index 98NewDeveloper compares commands across Claude Code, Codex, Gemini CLI1 sources
- Heat index 56Linus Torvalds Pushes Linux Kernel Patch Written With Claude Code1 sources
- Heat index 78Tutorial: building an auto-shop admin system with Claude Code1 sources
How is heat calculated?About the methodHide
Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.
This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.
- Surge
- Discussion rising fast
- New
- First report within 6 hours
- Rising
- Still gathering discussion
