Academy → Using HermesOfficial documentation · clear explanation

Inspecting Hermes Desktop Dom — Read the live Hermes desktop DOM/CSS over CDP

Inspecting Hermes Desktop Dom — Read the live Hermes desktop DOM/CSS over CDP

Intermediate10 minutes3 questions2026-08-09
The idea in one minute

Start with meaning, then move to detail.

This lesson explains Inspecting Hermes Desktop Dom — Read the live Hermes desktop DOM/CSS over CDP as part of extending Hermes and connecting external tools. 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 Skill metadata, Reference: full SKILL.md, Overview, then verify failure modes and version compatibility.

What do you need first?

Complete installation and one successful task before adding new capabilities.

What will you know?

A clear outcome before you read.

  • Understand Inspecting Hermes Desktop Dom — Read the live Hermes desktop DOM/CSS over CDP 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.

Skill
An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Browser / CDP
A layer for programmatic browser control and page or event inspection.
Official page description

Read the live Hermes desktop DOM/CSS over CDP

Topic map

What does the source say, and in what order?

  1. 01
    Skill metadata

    Start here to understand the core idea or structure.

  2. 02
    Reference: full SKILL.md

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

  3. 03
    Overview

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

  4. 04
    When to Use

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

  5. 05
    The port

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

  6. 06
    Reading the DOM

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

  7. 07
    The question this is best at: which rule won?

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

  8. 08
    Your own isolated instance

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

  9. 09
    Pitfalls

    Finish here to verify the result and special cases.

Examples from the official page

Copy only after you understand the effect.

curl -s --max-time 3 http://127.0.0.1:${HERMES_DESKTOP_CDP_PORT:-9222}/json/version
cd apps/desktop node scripts/eval.mjs "document.querySelectorAll('[data-slot]').length"
`SELECTORS` in `scripts/perf/lib/cdp.mjs` holds the stable `data-slot` hooks (composer, thread viewport, assistant message, turn pair, profile rail). Prefer them over inventing a `querySelector` — they are updated as a unit when components move. ## The question this is best at: which rule won? Editing every call site because a style "isn't applying" is the classic waste. Read the real node first:
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 “Inspecting Hermes Desktop Dom — Read the live Hermes desktop DOM/CSS over CDP” 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?