NousResearch/hermes-agent

Desktop local backend profile scoping bugs

Cluster 119894. Data as of

Nothing open on GitHub. Fix merged in #120099 on 23 Sep 2026. Check it covers your case.

The short answer

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

These issues and fixes concern the Desktop app incorrectly scoping registry API requests, capabilities, and settings to the default or launch profile rather than the user-selected 'Applies to' profile on a shared local backend.

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.

  • #120099 fix(desktop): Settings and Capabilities follow the "Applies to" profile on the shared local backend (salvage #118941)

    merged to main

    files: apps/desktop/electron/connection-config.test.ts, apps/desktop/electron/connection-config.ts, contributors/emails/[redacted:email]

2 PRs closed without merging

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

  • #120022 fix(desktop): scope local registry API requests to the profile (#119894) · done elsewhere → 1750cfb, #119894, #120099, #118941
  • #120101 Desktop: registry-pinned local requests reach the selected profile, not the backend's launch profile (#119411, #119415, #119894; salvage #119513) · superseded by another PR → 1750cfb, #120099, #118941, #119411, #119415, #119894, #119513
Closed issues · 1
  • Closed#119894Desktop Capabilities pane shows default profile's skills/toolsets/MCP for all profiles; toggles write to default profile
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

Merged PRs
#120099
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
23 Sep 2026

For your agent

The same facts, typed.