Browser CDP Supervisor
مراقبة المتصفح عبر CDP
Start with meaning, then move to detail.
This lesson explains Browser CDP Supervisor 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 Backend support, Architecture, CDPSupervisor, 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 CDP Supervisor 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.
- 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 Hermes detects and responds to native JS dialogs and interacts with cross-origin iframes via a persistent CDP connection.
What does the source say, and in what order?
- 01Backend support
Start here to understand the core idea or structure.
- 02Architecture
Read this after the foundation, then connect it to the previous step.
- 03CDPSupervisor
Read this after the foundation, then connect it to the previous step.
- 04Lifecycle
Read this after the foundation, then connect it to the previous step.
- 05Dialog policy
Read this after the foundation, then connect it to the previous step.
- 06Agent surface
Read this after the foundation, then connect it to the previous step.
- 07browserdialog tool
Read this after the foundation, then connect it to the previous step.
- 08browsersnapshot extension
Read this after the foundation, then connect it to the previous step.
- 09Availability gating
Read this after the foundation, then connect it to the previous step.
- 10Cross-origin iframe interaction
Finish here to verify the result and special cases.
Copy only after you understand the effect.
browser_dialog(action, prompt_text=None, dialog_id=None){
"pending_dialogs": [
{"id": "d-1", "type": "alert", "message": "Hello", "opened_at": 1650000000.0}
],
"recent_dialogs": [
{"id": "d-1", "type": "alert", "message": "...", "opened_at": 1650000000.0,
"closed_at": 1650000000.1, "closed_by": "remote"}
],
"frame_tree": {
"top": {"frame_id": "FRAME_A", "url": "https://example.com/", "origin": "https://example.com"},
"children": [
{"frame_id": "FRAME_B", "url": "about:srcdoc", "is_oopif": false},
{"frame_id": "FRAME_C", "url": "https://ads.example.net/", "is_oopif": true, "session_id": "SID_C"}
],
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.