hermes-computer-use
PulseGate's liveness check found it on 13 Sep 2026; it is registered on GitHub and PyPI and has been in the index since 27 Jun 2026. How this is checked
hermes-computer-use is an open-source MCP server for pixel-level browser automation in WSL2 environments. It enables automation of Chrome using screenshots and xdotool, bypassing the Chrome DevTools Protocol. Designed for automation engineers and developers.
Inferred · not functionally tested
Overview
5 featuresPurpose: Automating browser interactions at the pixel level in WSL2 environments without using Chrome DevTools Protocol.
Inferred · not functionally tested
Audience: Automation engineers and developers
Inferred · not functionally tested
Functions: browser_automation
Inferred · not functionally tested
Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: unknown
Recorded constraints: pricing: open_source · license: MIT · platforms: CLI · deployment: cli, api_only
Constraint provenance is unknown; confirm requirements with the publisher.
Record sources: github.com. These links do not verify the individual claims.
In the Browser DevTools & extensions space, hermes-computer-use takes a focused approach. Inferred · not functionally tested: It focuses on automating browser interactions at the pixel level in WSL2 environments without using Chrome DevTools Protocol. Inferred · not functionally tested: hermes-computer-use is an open-source project aimed at automation engineers and developers. Basis unknown · not verified: hermes-computer-use is open source under the MIT license. Basis unknown · not verified: hermes-computer-use is available on the command line and API.
Behind hermes-computer-use is Noah3521, and it first shipped in 2026. Development happens publicly on GitHub with 11 commits in the last 90 days. Inferred · not functionally tested: Key capabilities include browser automation, pixel-level control, and MCP server. Inferred · not functionally tested: Catalogued interfaces include an MCP server.
Summary written by a language model from the project’s public pages.
Tasks: Inferred · not functionally tested
- Browser automation
- Pixel-level control
- MCP server
- WSL2 support
- Screenshot automation
Topics: Inferred · not functionally tested
Built with & integrations
Trust & compliance
Indexing history
What PulseGate has recorded for this listing
Frequently asked questions about hermes-computer-use
- What is hermes-computer-use?
- Inferred · not functionally tested: Hermes-computer-use focuses on automating browser interactions at the pixel level in WSL2 environments without using Chrome DevTools Protocol. It is catalogued under Browser DevTools & extensions on PulseGate.
- Who is hermes-computer-use for?
- Inferred · not functionally tested: hermes-computer-use is an open-source project built for automation engineers and developers.
- Is hermes-computer-use free?
- Basis unknown · not verified: Yes — hermes-computer-use is open source under the MIT license and free to use.
- What platforms does hermes-computer-use run on?
- Basis unknown · not verified: hermes-computer-use runs on the command line and API.
- Is hermes-computer-use still active?
- PulseGate's liveness check found it on 13 Sep 2026. Its GitHub repository shows 11 commits in the last 90 days.
- What are alternatives to hermes-computer-use?
- Similar projects tracked by PulseGate include hermesd, hermescheck, and hermes-council.hermesdhermescheckhermes-council
- Who makes hermes-computer-use?
- hermes-computer-use is developed by Noah3521.
- When did hermes-computer-use launch?
- hermes-computer-use first shipped in 2026.
Similar projects
Closest matches by what these projects do