NousResearch/hermes-agent

WSL2 socket path fix for Windows cua-driver.exe

Cluster 80227 · agent. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 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
1 issue and 2 PRs.

These items address a bug where the embedded CUA daemon generates a Unix socket path instead of a Windows named-pipe path when the driver command is a Windows .exe running under WSL2, causing OS error 123. The work involves correcting the socket path logic to use the appropriate Windows named-pipe format in that context.

Open issues1

  • Issue#80227computer_use WSL: _EmbeddedCuaDaemon generates Unix socket path for Windows-side cua-driver.exe (OS error 123)

Open PRs2

  • PR#80252fix(computer_use): use Windows named pipe socket path for .exe cua-driver under WSL2
  • PR#139111fix(computer-use): support WSL Windows CUA driver interop (os error 123)

1 PR closed without merging

From the close comments: duplicate 1

  • #99175 fix(computer_use): use Windows named-pipe socket path when driver_cmd is a Windows .exe (WSL2) · duplicate → #80252
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.50: 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
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.