Cairn
NousResearch/hermes-agent

Dashboard Files tab errors on non-Docker installs

Cluster 44116 · dashboard. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 3 issues already closed.
Fix event
No fix has been merged to main. 3 PRs 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.

Bug reports and fixes addressing the dashboard Files tab incorrectly forcing '/opt/data' as the file browser root on non-Docker host installs, causing 500 permission errors on Windows, WSL, and remote access scenarios.

Open issues0

No open issues.

Open PRs0

No open pull requests.

3 PRs closed without merging

From the close comments: superseded by another PR 2 · done elsewhere 1

  • #44139 fix(dashboard): don't force /opt/data files root for remote requests on host installs · superseded by another PR → #44116
  • #44480 fix(dashboard): use AND logic for managed files hosted policy to fix non-Docker remote access · done elsewhere → d206e1f, #44116, #44471
  • #44561 fix(dashboard): don't force /opt/data root for non-Docker remote access (#44471) · superseded by another PR → #44139, #44471
Closed issues · 3
  • Closed#44116[Bug]: Remote dashboard Files tab forces /opt/data on non-Docker host installs
  • Closed#44471Dashboard file browser 500s on non-Docker remote access: Permission denied '/opt/data'
  • Closed#45019Dashboard: Virgin install returns 500 "Managed files root is unavailable: [Errno 13] Permission denied: '/opt/data'" on Files tab (Windows + WSL)
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.27: 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
dashboard
Closed issues
3
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/44116.json
cluster/44116.md