hermes - 💡(How to fix) Fix [Bug]: cannot read local file in windows system( no WSL) [2 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
NousResearch/hermes-agent#17753Fetched 2026-05-01 05:56:08
View on GitHub
Comments
2
Participants
2
Timeline
9
Reactions
0
Author
Participants
Timeline (top)
labeled ×5commented ×2cross-referenced ×1renamed ×1

The system cannot read any local file in windows system. however, it can write to the file correctly.

Error Message

Additional Logs / Traceback (optional)

Root Cause

Root Cause Analysis (optional)

Code Example

NA

---
RAW_BUFFERClick to expand / collapse

Bug Description

Summary

The system cannot read any local file in windows system. however, it can write to the file correctly.

when i asked Hermes to read user.md.....

● Read the content of user.md under C:.hermes\memories
Initializing agent... ──────────────────────────────────────── ┊ 💻 preparing terminal… ┊ 💻 $ powershell -Command "Get-Content -LiteralPath 'C:.hermes\memories\user.md' -Encoding UTF8" 1.2s ┊ 💻 $ powershell -Command "Get-ChildItem -Path 'C:.hermes\memories' -Filter user.md -Recurse | Select-Object -ExpandProperty FullName" 0.5s ┊ 💻 preparing terminal… ┊ 💻 $ powershell -Command "Get-ChildItem -Path 'C:.hermes\memories'" 0.5s ┊ 💻 preparing terminal… ┊ 💻 $ powershell -Command "Get-Location" 0.5s ┊ 💻 preparing terminal… ┊ 💻 $ powershell -Command "if (Test-Path '.\memories\user.md') { Get-Content -LiteralPath '.\memories\user.md' -Encoding UTF8 } else { Get-ChildItem -Path . -Recurse | Where-Object { $_.FullName -like 'user.md' } | Select-Object -ExpandProperty FullName }" 0.6s

The system will get 'File not found at path.' but actually the user.md file is there and the client can write content to the file.

Steps to Reproduce

  1. Run hermes on a Windows installation (not installed on WSL )
  2. Issue a order to read any local file.
  3. hermes will say it cannot find the file or the file content is empty

Expected Behavior

The system shall be able to find the file and read it.

Actual Behavior

Hermes can write content to the file, but cannot read it.

Affected Component

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

Messaging Platform (if gateway-related)

N/A (CLI only)

Debug Report

NA

Operating System

WIndows 10

Python Version

3.11.5

Hermes Version

0.11.0 (2026.4.23)

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

Is this because of the sandbox mechanism?

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 be resolved by ensuring the correct file path is used when reading the file, potentially due to differences in how file paths are handled between writing and reading operations.

Guidance

  • Verify that the file path used for reading the file is correct and consistent with the path used for writing, considering any potential differences in path resolution between the two operations.
  • Check if the issue is related to the sandbox mechanism, as suggested in the Root Cause Analysis, and explore potential workarounds or configurations to address this.
  • Test reading the file using an absolute path to rule out any issues with relative path resolution.
  • Review the implementation of file reading and writing operations in the Hermes code to identify any discrepancies or potential bugs.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The issue may be specific to the Windows environment, and testing on other platforms could help determine if the issue is platform-specific. Additionally, the fact that writing to the file works but reading does not suggests a potential issue with file path handling or permissions.

Recommendation

Apply a workaround by ensuring consistent file path handling for both reading and writing operations, as the root cause is likely related to this inconsistency.

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…

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]: cannot read local file in windows system( no WSL) [2 comments, 2 participants]