Cairn

Desktop remote/WSL file path routing and rendering corrections

NousResearch/hermes-agent · cluster 44523 · apps/desktop

Data as of

Nothing open on GitHub. Fix merged in #123049. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #123049. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #123049. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address broken file links and inline media rendering issues in desktop remote mode, where WSL or gateway path mismatches produce dead file:// URLs or missing artifacts. The work routes file access through the fs bridge and corrects Windows+WSL POSIX path handling.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #123049 fix(desktop): bridge WSL paths for the remaining file-read handlers on Windows

    merged to main

    files: apps/desktop/electron/local-read-path.test.ts, apps/desktop/electron/local-read-path.ts, apps/desktop/electron/main.ts

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #44538 fix(desktop): remote-mode chat file links download via the fs bridge instead of dead file:// URLs · done elsewhere → 03406ae
  • #64074 fix(desktop): route Windows+WSL POSIX media paths through gateway (#63669) · other → #71783
Closed issues · 2
  • Closed#44523[Bug]: Desktop remote mode: chat file links are silent dead ends (file:// fallback targets the gateway's path on the client; no display path for PDFs/non-images)
  • Closed#63669[Desktop] Newly generated MEDIA images fail to render inline — WSL path routing race and fallback convergence
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.34: 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
apps/desktop
Merged PRs
#123049
Closed issues
2
Attempts
2 PRs closed without merging
Fix link checked
25 Sep 2026

For your agent

The same facts, typed.

cluster/44523.json
cluster/44523.md