Browser Provider Plugins
إضافة مزوّد متصفح
Start with meaning, then move to detail.
This lesson explains Browser Provider Plugins 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, 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 practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect How it fits together, Discovery, Directory structure, then verify failure modes and version compatibility.
Know Python, Git, and basic project structure before changing code.
A clear outcome before you read.
- Understand Browser Provider Plugins 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.
Short definitions before the details.
- Provider
- The service that runs or provides access and authentication to a model.
- Session & memory
- A session holds conversation context, while memory keeps selected facts that should persist.
- Tool
- A structured action the agent can call to read or change something.
- Browser / CDP
- A layer for programmatic browser control and page or event inspection.
How to build a cloud browser backend plugin for Hermes Agent
What does the source say, and in what order?
- 01How it fits together
Start here to understand the core idea or structure.
- 02Discovery
Read this after the foundation, then connect it to the previous step.
- 03Directory structure
Read this after the foundation, then connect it to the previous step.
- 04The BrowserProvider ABC
Read this after the foundation, then connect it to the previous step.
- 05The session-metadata contract
Read this after the foundation, then connect it to the previous step.
- 06getsetupschema() — the hermes tools picker row
Read this after the foundation, then connect it to the previous step.
- 07Users configure it
Read this after the foundation, then connect it to the previous step.
- 08Reference implementations
Read this after the foundation, then connect it to the previous step.
- 09Checklist
Finish here to verify the result and special cases.
Copy only after you understand the effect.
plugins/browser/my-backend/
├── __init__.py # register() entry point
├── provider.py # BrowserProvider subclass
└── plugin.yaml # Manifest with kind: backend and provides_browser_providersname: browser-my-backend
version: 1.0.0
description: "My cloud browser backend. Requires MY_BACKEND_API_KEY."
author: you
kind: backend
provides_browser_providers:
- my-backend## The BrowserProvider ABC
Implement `agent.browser_provider.BrowserProvider`. Three lifecycle methods plus identity: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.