skills.rest
atomeam
atomeamCOMMUNITY
Explore all skills by this author →
GitHub

Persistent Browser Service

Maintain a persistent background browser process with an HTTP API for automation.

2|Updated May 16, 2026
Search Tags:#browser automation#web scraping#playwright#HTTP API#session persistence#automation scripts#persistent sessions
One-click install
npx skills add https://github.com/atomeam/Aether --skill persistent-browser-service
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Persistent Browser Service
Source: https://github.com/atomeam/Aether/tree/main/.devin/skills/persistent-browser-service
Command: npx skills add https://github.com/atomeam/Aether --skill persistent-browser-service

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill eliminates the frustration of repeated browser window creation, lost login sessions, and broken state in browser automation workflows by providing a way to keep a single browser instance running across multiple script executions.

Core Features & Use Cases

  • Persistent Background Browser: Runs a single browser process that stays alive even after individual automation scripts finish, surviving shell exits and script failures.
  • Automatic Session Persistence: Saves browser session data (cookies, local storage) to disk automatically, so you stay logged into websites across separate script runs.
  • Simple HTTP API: Exposes easy-to-use endpoints for navigating to URLs, clicking elements, and filling form fields that work with any programming language or command-line tool.
  • Use Case: Perfect for long-running automation tasks like managing social media accounts, scraping large volumes of web content, or completing multi-step form submissions that require maintaining a logged-in state over time.

Quick Start

Use this skill to automate a series of browser actions on a target website while preserving your login session and avoiding the overhead of launching a new browser window for each individual task.

Frequently Asked Questions about Persistent Browser Service

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

FAQPage Schema
How do I keep my browser session persistent across multiple automation scripts?▼

Persistent browser sessions are maintained by running a single long-running background browser process that automatically saves cookies and local storage to disk, ensuring your login state survives across multiple separate script executions.

Can I use an HTTP API for web scraping instead of launching a new Playwright browser instance every time?▼

Yes, web scraping can be executed via a language-agnostic HTTP API that controls a single background browser process, eliminating the redundant overhead of launching new Playwright browser instances for each individual scraping task.

How does a persistent background browser help with multi-step form filling automation?▼

Multi-step form filling automation benefits from a persistent background browser by maintaining state continuity across script runs, allowing you to execute sequential URL navigation and element interaction tasks without losing your current progress or session data.

Does this browser automation approach work with command-line tools and any programming language?▼

Yes, browser automation works with any programming language or command-line tool because the background browser process exposes a simple, language-agnostic HTTP API for navigating URLs, clicking elements, and filling form fields.

What is the best way to manage social media accounts without losing login state between script runs?▼

Managing social media accounts without losing login state is best achieved by reusing a single persistent browser instance that automatically saves session data to disk, ensuring your authenticated state remains continuous across separate automation script invocations.

Why does my Playwright automation script lose its logged-in state after the shell exits?▼

Playwright automation scripts lose their logged-in state after shell exits because standard browser instances close when scripts finish, whereas a persistent background browser process saves session data to survive script failures and shell exits.

Related Skills

Explore More Software Engineering Skills→
TurnaboutHeroTurnaboutHero
12

playwright-master

Automate browser testing and web scraping with Playwright across Chromium, Firefox, and WebKit.

Community
Intermediate
solibluesoliblue
2

manifold

Search Manifold Markets and retrieve market details via read-only API requests.

Community
Basic
junchenghuojunchenghuo
3

agent-browser

Automate browser interactions via command-line interface for AI agents.

Community
Advanced
VoDaiLoczVoDaiLocz
24

chrome-devtools

Automate browser tasks with Puppeteer CLI scripts for navigation, screenshots, and performance analysis.

Community
Advanced