Issue Station
Sign In
Tools hereToolbox

hermes - 💡(How to fix) Fix [Bug]: Auto-launch failed: Chrome not found error when running hermes-cli with official Docker image [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#15697•Fetched 2026-04-26 05:25:46
View on GitHub
Comments
1
Participants
1
Timeline
5
Reactions
0
Author
firstl15htfirstl15ht
Participants
firstl15htfirstl15ht
Timeline (top)
labeled ×4commented ×1

Error Message

I am new to hermes-agent. After pulling the latest official docker image and going through the basic setup, I launched into the hermes cli mode and prompted the agent for "What are the top trending repos on GitHub right now?". The agent encountered the following error: Agent reported that it "encountered a dependency error while trying to navigate to GitHub's trending page (Chrome not found)" and when asked to show the raw error log, it responded as follows: Here is the raw error log from the attempt to navigate to GitHub: {"success": false, "error": "Auto-launch failed: Chrome not found. Checked:\n - agent-browser cache: /opt/data/.agent-browser/browsers\n - System Chrome installations\n - Puppeteer browser cache\n - Playwright browser cache\nRun agent-browser install to download Chrome, or use --executable-path."}

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Code Example

Here is the raw error log from the attempt to navigate to GitHub:

    json
    {"success": false, "error": "Auto-launch failed: Chrome not found. Checked:\n  - agent-browser cache: /opt/data/.agent-browser/browsers\n  - System Chrome installations\n  - Puppeteer browser cache\n  - Playwright browser cache\nRun agent-browser install to download Chrome, or use --executable-path."}


    This confirms the issue: the agent cannot launch the required browser environment (Chrome). To proceed with any task requiring live web browsing (like checking trending repos), this dependency must be resolved.

    If you can resolve the dependency issue (e.g., by running agent-browser install), please let me know, and I will immediately try accessing the GitHub page again.

---

Report     https://paste.rs/czz14
agent.log  https://paste.rs/tfpEE

---
RAW_BUFFERClick to expand / collapse

Bug Description

Hi,

I am new to hermes-agent. After pulling the latest official docker image and going through the basic setup, I launched into the hermes cli mode and prompted the agent for "What are the top trending repos on GitHub right now?". The agent encountered the following error:

Auto-launch failed: Chrome not found. Checked:\n - agent-browser cache: /opt/data/.agent-browser/browsers\n - System Chrome installations\n - Puppeteer browser cache\n - Playwright browser cache\nRun agent-browser install to download Chrome, or use --executable-path.

After checking the Dockerfile in Github and exploring the container, it appears that chromium is installed under /opt/hermes/.playwright, agent-browser was installed as part of the package.json and agent-browser install was never run. I am guessing the intent is to install chromium via playwright and have agent-browser use the existing chromium rather than installing its own. If this is indeed the intent, how do we set or pass the --executable-path to the agent-browser call?

Steps to Reproduce

  1. Run docker pull nousresearch/hermes-agent:latest
  2. Run through the basic setup
  3. Launch hermes cli docker run -it --rm --name hermes-cli -v ~/docker/volumes/hermes/:/opt/data nousresearch/hermes-agent
  4. Prompt the agent "What are the top trending repos on GitHub right now?"

Expected Behavior

Use agent-browser to get the top trending repos on GitHub.

Actual Behavior

Agent reported that it "encountered a dependency error while trying to navigate to GitHub's trending page (Chrome not found)" and when asked to show the raw error log, it responded as follows:

 Here is the raw error log from the attempt to navigate to GitHub:

    json
    {"success": false, "error": "Auto-launch failed: Chrome not found. Checked:\n  - agent-browser cache: /opt/data/.agent-browser/browsers\n  - System Chrome installations\n  - Puppeteer browser cache\n  - Playwright browser cache\nRun agent-browser install to download Chrome, or use --executable-path."}


    This confirms the issue: the agent cannot launch the required browser environment (Chrome). To proceed with any task requiring live web browsing (like checking trending repos), this dependency must be resolved.

    If you can resolve the dependency issue (e.g., by running agent-browser install), please let me know, and I will immediately try accessing the GitHub page again.

Affected Component

Tools (terminal, file ops, web, code execution, etc.)

Messaging Platform (if gateway-related)

No response

Debug Report

Report     https://paste.rs/czz14
agent.log  https://paste.rs/tfpEE

Operating System

docker

Python Version

No response

Hermes Version

v0.11.0 (2026.4.23)

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

  • I'd like to fix this myself and submit a PR

extent analysis

TL;DR

The issue can likely be resolved by setting the --executable-path to the existing Chromium installation when calling agent-browser.

Guidance

  • The error message suggests that agent-browser is unable to find a Chrome installation, despite Chromium being installed via Playwright.
  • To resolve this, you can try setting the --executable-path to the existing Chromium installation when calling agent-browser, which is located at /opt/hermes/.playwright.
  • You can verify if the Chromium installation is correct by checking the contents of the /opt/hermes/.playwright directory.
  • Before attempting a fix, ensure that the agent-browser version is compatible with the installed Chromium version.

Example

No code snippet is provided as the issue is related to configuration and environment setup.

Notes

The issue seems to be related to the agent-browser configuration and its inability to find the existing Chromium installation. The proposed fix assumes that the Chromium installation via Playwright is correct and compatible with agent-browser.

Recommendation

Apply workaround: set the --executable-path to the existing Chromium installation when calling agent-browser, as this is a more targeted solution to the specific error message and environment setup.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#installation#model loading#dependency error#configuration error#environment variable

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix [Bug]: Auto-launch failed: Chrome not found error when running hermes-cli with official Docker image [1 comments, 1 participants]