How to Automate Browser Tasks with Skyvern AI

Skyvern is an open-source browser automation framework that reads pages with vision-language models instead of CSS selectors, so your scripts don’t break when a site changes its HTML.

If you have ever maintained a Selenium script that dies every time a vendor redesigns their portal, you already know the pain Skyvern targets. Instead of telling it “click #submit-btn-3”, you tell it “download last month’s invoice” and it works out the clicks. Setup takes about 15 minutes if you already have Docker running.

What is Skyvern and what does it replace?

It replaces selector-based automation tools. The agent takes a screenshot of the page, asks a vision model what to do next, then acts. That loop costs money on every step because each screenshot is an API call to a vision model, so budget accordingly. A self-hosted run is basically free apart from your own model costs; the managed cloud charges per task.

How do you install Skyvern with Docker?

The fast route is the compose file from the repository:

git clone https://github.com/Skyvern-AI/skyvern
cd skyvern
docker compose up -d

That starts the UI on port 8080 along with a Postgres database. You will need an LLM key (OpenAI, Anthropic, or a compatible endpoint) in the .env file, plus a second key for the vision step unless you route both to the same provider. First boot pulled roughly 3 GB of images on my test box.

How do you write your first Skyvern task?

Give it a plain-English goal and a starting URL. The syntax in a Python task file looks like this:

await skyvern.run_task(
    url="https://example.com/portal/login",
    prompt="Log in with the saved credentials and download the newest PDF statement",
)

Run it from the CLI with skyvern run or trigger it from the web UI. The run viewer shows each screenshot and the decision made, which is genuinely useful when a step fails on step seven of a twelve-step form.

What does Skyvern cost?

The software is free and self-hostable. Your real cost is model tokens: expect a few cents per task on a mid-tier vision model. The hosted version uses usage-based pricing, so heavy daily jobs are better self-hosted. There is no per-seat licence on the open-source core.

Who should not use Skyvern?

If you need millisecond-level speed or you are scraping a simple static page, plain HTTP requests or Playwright will be 10-50x cheaper. Vision calls add 1-3 seconds of latency per page. Skyvern earns its keep on messy, login-gated, constantly changing sites.

How does Skyvern compare with Selenium and Playwright?

Aspect	Skyvern	Selenium / Playwright
Selector fragility	Survives redesigns	Breaks on DOM changes
Cost per step	Vision API call	Free
Speed	1-3s per page	Milliseconds
Best for	Unknown or changing sites	Stable, known flows

The honest summary: use Skyvern for the jobs you dread maintaining, and use code-based tools for the jobs that will never change.

Key Takeaways

• Skyvern is open source and self-hostable with Docker Compose.
• It uses vision models to read pages, so CSS selectors are not needed.
• Plan for vision API costs and slower per-page execution.
• Best fit: portals, government forms, and invoice downloads on sites you do not control.