browser-session-persistence

Save and load Playwright browser session states for authenticated automation.

2|Updated May 16, 2026
One-click install
npx skills add https://github.com/atomeam/Aether --skill browser-session-persistence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-session-persistence
Source: https://github.com/atomeam/Aether/tree/main/.devin/skills/browser-session-persistence
Command: npx skills add https://github.com/atomeam/Aether --skill browser-session-persistence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the tedious and often impossible task of repeatedly logging into websites that require 2FA, passkeys, or MFA for automation, as these verification methods cannot be fully automated via scripts.

Core Features & Use Cases

  • One-Time Session Save: Manually log in to any authenticated site once, and the Skill automatically saves your full session state including cookies, local storage, and authentication tokens for future use.
  • Seamless Session Reuse: Load saved sessions into automation scripts to bypass login entirely, working as if you are already authenticated on the target site.
  • Real-World Use Case: Automate tasks on platforms like RapidAPI, GitHub, or AWS that require 2FA, without needing to enter verification codes every time you run a script.

Quick Start

Use the browser-session-persistence skill to save your RapidAPI session by running the provided login script, completing the 2FA prompt manually when the browser opens, and then reuse that saved session for all future RapidAPI automation tasks without any additional login steps.

Frequently Asked Questions about browser-session-persistence

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bypass 2FA and manual login in Playwright automation scripts?

You can bypass 2FA in Playwright automation by manually logging in once to save the full session state, including cookies and local storage, then loading this saved session into future scripts to reuse the authenticated browser context without repeated logins.

Can I save and reuse authenticated browser sessions for platforms like AWS or GitHub?

Yes, you can save and reuse authenticated browser sessions for platforms like AWS, GitHub, and RapidAPI. The Skill stores your session state and cookies after one manual login, allowing unattended automation scripts to bypass MFA or passkey requirements entirely.

What is the best way to handle passkey and MFA requirements for unattended web scraping?

The best way to handle passkey and MFA for web scraping is to perform a single manual login to capture the session state and cookies, then load this persistent session into your browser automation scripts to execute scraping tasks unauthenticated.

Does browser session persistence work with banking sites that require hard-coded 2FA tokens?

Yes, browser session persistence works with banking sites requiring hard-coded 2FA tokens. By completing the initial manual authentication and saving the browser context, you can reuse the authenticated session for subsequent automation without needing to re-enter verification codes.

How to save cookies and local storage in Playwright to skip redundant login steps?

To save cookies and local storage in Playwright, run the provided login script, complete the manual authentication in the opened browser, and the Skill will automatically store the session state for loading into future automation workflows to skip redundant logins.

Why does my Playwright web scraping script keep failing on sites with multi-factor authentication?

Playwright web scraping scripts fail on multi-factor authentication sites because MFA and passkeys cannot be fully automated via standard scripting, requiring you to implement session persistence to manually authenticate once and reuse the saved browser context.