HermesBELARABI
العربيةSearch/CheckingSign in
AcademyDirectorySolutionsStudioProjectsComparePricing Sign in
Academy → Using HermesOfficial documentation · clear explanation

Browser Automation

التحكم في المتصفح

Developer27 minutes3 questions✓ 2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains Browser Automation as part of Hermes internals and extension points. You will learn what it does, when it matters, and the smallest safe test that proves it works.

If you are new

If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?

For hands-on use

For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.

For specialists

For advanced readers, inspect Overview, Setup, Browserbase cloud mode, then verify failure modes and version compatibility.

What do you need first?

Know Python, Git, and basic project structure before changing code.

What will you know?

A clear outcome before you read.

  • Understand Browser Automation without assumed prior knowledge.
  • Separate the source description from what still needs testing in your environment.
  • Read the first command and identify its inputs and outputs before copying it.
Lesson terms

Short definitions before the details.

Session & memory
A session holds conversation context, while memory keeps selected facts that should persist.
Browser / CDP
A layer for programmatic browser control and page or event inspection.
Automation
Running work later or repeatedly with explicit success and failure conditions.
Official page description

Control browsers with multiple providers, local Chromium-family browsers via CDP, or cloud browsers for web interaction, form filling, scraping, and more.

Topic map

What does the source say, and in what order?

  1. 01
    Overview

    Start here to understand the core idea or structure.

  2. 02
    Setup

    Read this after the foundation, then connect it to the previous step.

  3. 03
    Browserbase cloud mode

    Read this after the foundation, then connect it to the previous step.

  4. 04
    Browser Use cloud mode

    Read this after the foundation, then connect it to the previous step.

  5. 05
    Firecrawl cloud mode

    Read this after the foundation, then connect it to the previous step.

  6. 06
    Hybrid routing: cloud for public URLs, local for LAN/localhost

    Read this after the foundation, then connect it to the previous step.

  7. 07
    Camofox local mode

    Read this after the foundation, then connect it to the previous step.

  8. 08
    Persistent browser sessions

    Read this after the foundation, then connect it to the previous step.

  9. 09
    What Hermes does

    Read this after the foundation, then connect it to the previous step.

  10. 10
    What Hermes does not do

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

# Add to ~/.hermes/.env BROWSERBASE_API_KEY=*** BROWSERBASE_PROJECT_ID=your-project-id-here
# Add to ~/.hermes/.env BROWSER_USE_API_KEY=***
# Add to ~/.hermes/.env FIRECRAWL_API_KEY=fc-***
Try it now

Read the first command and identify its inputs and outputs before copying it.

Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.

Knowledge check

Three decisions before completion.

1. What is the source of truth when “Browser Automation” changes?
2. What is the best way to apply this lesson?
3. What should happen before a step can modify files or an external account?