Issue Station
Sign In
Tools hereToolbox

openclaw - ✅(Solved) Fix [Bug]: browser tool screenshot fails with ENOENT — temp directory created by chrome-mcp bridge not actually created [1 pull requests, 1 comments, 2 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
openclaw/openclaw#77222•Fetched 2026-05-05 05:51:03
View on GitHub
Comments
1
Participants
2
Timeline
9
Reactions
2
Author
SatoMiniSatoMini
Participants
clawsweeper[bot]clawsweeper[bot]SatoMiniSatoMini
Timeline (top)
labeled ×2mentioned ×2subscribed ×2commented ×1

The browser tool's screenshot action fails with ENOENT: no such file or directory when using Chrome DevTools MCP (profile="user").

Error Message

  1. The tool call returns an error: ENOENT: no such file or directory, open '/tmp/openclaw/openclaw-chrome-mcp-XXXXXX/UUID' The tool returns error: ENOENT no such file or directory. The screenshot is never captured.

Root Cause

The browser tool's screenshot action fails with ENOENT: no such file or directory when using Chrome DevTools MCP (profile="user").

Fix Action

Fixed

PR fix notes

PR #74685: fix(browser): read Chrome MCP screenshot extension

Description (problem / solution / changelog)

Summary

  • read Chrome DevTools MCP screenshot output from the extension-suffixed path
  • use the requested/default screenshot format when building the file path
  • add a regression test covering the extension-suffixed screenshot file

Why

chrome-devtools-mcp writes screenshots to <filePath>.<format>, but OpenClaw was reading the bare temporary filePath. That caused screenshot reads to fail with ENOENT even though the MCP tool had written the image successfully.

Test

  • node scripts/run-vitest.mjs run --config test/vitest/vitest.unit.config.ts extensions/browser/src/browser/chrome-mcp.test.ts

Changed files

  • CHANGELOG.md (modified, +1/-0)
  • extensions/browser/src/browser/chrome-mcp.test.ts (modified, +24/-0)
  • extensions/browser/src/browser/chrome-mcp.ts (modified, +2/-1)
RAW_BUFFERClick to expand / collapse

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

The browser tool's screenshot action fails with ENOENT: no such file or directory when using Chrome DevTools MCP (profile="user").

Steps to reproduce

  1. Use Chrome DevTools MCP (Chrome browser with chrome-devtools-mcp extension) and navigate to any page
  2. Call the browser tool with action="screenshot" and profile="user" pointing to an existing tab
  3. The tool call returns an error: ENOENT: no such file or directory, open '/tmp/openclaw/openclaw-chrome-mcp-XXXXXX/UUID'
  4. The temp directory is never actually created, but the path string is returned as if it should exist

Expected behavior

The screenshot should be captured and returned as image data, without errors.

Actual behavior

The tool returns error: ENOENT no such file or directory. The screenshot is never captured.

OpenClaw version

2026.5.3 (06d46f7)

Operating system

Ubuntu 24.04.3 LTS (Linux 6.17.0-19-generic x86_64)

Install method

npm install -g openclaw (Node.js v24.13.0 via nvm)

Model

minimax-paid/MiniMax-M2.7

Provider / routing chain

Direct API call to MiniMax (no gateway/proxy/router)

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The browser tool's screenshot action may fail due to incorrect temp directory creation when using Chrome DevTools MCP with the "user" profile.

Guidance

  • Verify that the temp directory path /tmp/openclaw/openclaw-chrome-mcp-XXXXXX/ is correctly generated and exists before attempting to capture the screenshot.
  • Check the permissions of the /tmp directory to ensure that the openclaw process has write access.
  • Investigate the openclaw code to determine why the temp directory is not being created as expected.
  • Consider using a different temp directory or modifying the openclaw configuration to use an existing directory.

Example

No code snippet is provided as the issue does not contain sufficient information about the openclaw codebase.

Notes

The issue may be related to the openclaw version (2026.5.3) or the Node.js version (v24.13.0) used. Further investigation is needed to determine the root cause.

Recommendation

Apply a workaround by modifying the temp directory path or configuration to use an existing directory, as the root cause of the issue is unclear.

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…

FAQ

Expected behavior

The screenshot should be captured and returned as image data, without errors.

#api#ssr#memory leak#API versioning#request timeout

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix [Bug]: browser tool screenshot fails with ENOENT — temp directory created by chrome-mcp bridge not actually created [1 pull requests, 1 comments, 2 participants]