NousResearch/hermes-agent

Windows PTY bytes/str handling and pywinpty support

Cluster 31675 · environments. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 2 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items concern PTY input/output failures on Windows related to bytes-versus-string type mismatches when writing to pywinpty, along with associated fixes and detached WebSocket frame handling. The group centers on making PTY functionality work correctly on Windows.

Open issues0

No open issues.

Open PRs0

No open pull requests.

1 PR closed without merging

From the close comments: done elsewhere 1

  • #31697 fix(tools): use str on Windows pywinpty PTY write · done elsewhere → #31675
Closed issues · 2
  • Closed#31675[BUG] PTY write/submit fails on Windows/MSYS (bytes/str conversion)
  • Closed#35356PTY stdin write fails: 'bytes' object cannot be converted to 'PyString'
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.45: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem
environments
Closed issues
2
Attempts
1 PR closed without merging

For your agent

The same facts, typed.