{"repo":"NousResearch/hermes-agent","public_id":"80227","display_label":"WSL2 socket path fix for Windows cua-driver.exe","summary":"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.","subsystem":"agent","counts":{"members":4,"open_issues":1,"open_issues_distinct":1,"open_prs":2,"closed_issues":0,"merged_prs":0,"attempt_prs":3},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.5},"fix_edges":[],"members":[{"kind":"issue","number":80227,"title":"computer_use WSL: _EmbeddedCuaDaemon generates Unix socket path for Windows-side cua-driver.exe (OS error 123)","url":null,"state":"open"},{"kind":"pr","number":80252,"title":"fix(computer_use): use Windows named pipe socket path for .exe cua-driver under WSL2","url":null,"state":"open","close_reason":{"category":"implemented_elsewhere","implication":"superseded"},"merged":false},{"kind":"pr","number":99175,"title":"fix(computer_use): use Windows named-pipe socket path when driver_cmd is a Windows .exe (WSL2)","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#80252","number":80252}],"category":"duplicate_of","implication":"duplicate"},"merged":false},{"kind":"pr","number":139111,"title":"fix(computer-use): support WSL Windows CUA driver interop (os error 123)","url":null,"state":"open","close_reason":{"category":"silent_close","implication":"active"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}