hermes - 💡(How to fix) Fix [Windows] Terminal tool returns empty output on native Windows [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

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#16426Fetched 2026-04-28 06:53:24
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×5commented ×1

On native Windows (not WSL2), the terminal tool returns empty output for all commands. Commands execute successfully (exit code 0) but no output is captured. This makes the agent unable to read files, run tests, or perform any shell operations.

Root Cause

On native Windows (not WSL2), the terminal tool returns empty output for all commands. Commands execute successfully (exit code 0) but no output is captured. This makes the agent unable to read files, run tests, or perform any shell operations.

RAW_BUFFERClick to expand / collapse

Environment

  • OS: Windows 11 Home China (build 26200)
  • Python: 3.11.15
  • HermesAgent: v0.11.0
  • Shell: Git Bash (bundled with Git for Windows 2.54.0)

Description

On native Windows (not WSL2), the terminal tool returns empty output for all commands. Commands execute successfully (exit code 0) but no output is captured. This makes the agent unable to read files, run tests, or perform any shell operations.

Bug 1: select.select() doesn't support pipe fd on Windows

Symptoms

All terminal commands return empty output:

extent analysis

TL;DR

The issue is likely due to the lack of support for select.select() with pipe file descriptors on Windows, causing the terminal tool to return empty output for all commands.

Guidance

  • Investigate alternative methods for handling pipe file descriptors on Windows, such as using the msvcrt module or win32pipe library.
  • Verify that the issue is indeed caused by the select.select() limitation by testing with a different approach to handling pipe file descriptors.
  • Consider using a cross-platform library that abstracts away the underlying file descriptor handling, such as subprocess or plumbum.
  • Check if there are any existing workarounds or fixes for this issue in the HermesAgent codebase or related libraries.

Example

No code snippet is provided due to the lack of specific implementation details in the issue.

Notes

The solution may require significant changes to the HermesAgent codebase or the use of additional libraries. The issue is specific to Windows and may not affect other platforms.

Recommendation

Apply a workaround, such as using an alternative method for handling pipe file descriptors, as the issue is likely due to a fundamental limitation in the select.select() function on Windows.

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