Computer Use
Computer Use
Start with meaning, then move to detail.
This lesson explains Computer Use 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, 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 works, Enabling, Permission modes and logged-in browser profiles, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Computer Use 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.
- 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.
What does the source say, and in what order?
- 01How it works
Start here to understand the core idea or structure.
- 02Enabling
Read this after the foundation, then connect it to the previous step.
- 03Permission modes and logged-in browser profiles
Read this after the foundation, then connect it to the previous step.
- 04hermes computer-use doctor — your first triage stop
Read this after the foundation, then connect it to the previous step.
- 05The agent cursor and sessions
Read this after the foundation, then connect it to the previous step.
- 06Going deeper — the cua-driver skill pack
Read this after the foundation, then connect it to the previous step.
- 07Quick example
Read this after the foundation, then connect it to the previous step.
- 08Provider compatibility
Read this after the foundation, then connect it to the previous step.
- 09Safety
Read this after the foundation, then connect it to the previous step.
- 10Token efficiency
Finish here to verify the result and special cases.
Copy only after you understand the effect.
hermes computer-use installhermes -t computer_use chat$ hermes computer-use doctor
⚠️ cua-driver 0.5.8 on darwin — degraded
✅ binary_version: cua-driver 0.5.8
✅ platform_supported: macOS 26.4.1 (arm64)
✅ session_active: MCP session is active.
❌ bundle_identity: Process has no CFBundleIdentifier.
→ Run the binary inside CuaDriver.app so TCC grants attribute correctly.
✅ tcc_accessibility: Accessibility is granted.
✅ tcc_screen_recording: Screen Recording is granted.
✅ ax_capability: AX is trusted and reachable.
✅ screen_capture_capability: ScreenCaptureKit reachable; 1 display(s) shareable.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.