NousResearch/hermes-agent

Desktop font controls disabled after config/profile changes

Cluster 111963. Data as of 2026-10-24 04:06 UTC

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

open issues

open PRs

items grouped

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

Next step: read #112204, then check it covers your case.

Read #112204 Pick up a Lab task

These issues and fixes relate to font control UI elements in the desktop client remaining disabled or unresponsive after configuration refetches or profile switches. The work involves reseeding font controls to restore their enabled state in these scenarios.

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.

#112204 fix(desktop): Chat Font and Terminal Font controls re-enable after startup and profile switches (#111963, salvage #111969)

merged to main

files: apps/desktop/src/app/hooks/use-profile-switch-latch.test.ts, apps/desktop/src/app/hooks/use-profile-switch-latch.ts, apps/desktop/src/app/settings/chat-font-setting.test.tsx, apps/desktop/src/app/settings/chat-font-setting.tsx, apps/desktop/src/app/settings/terminal-font-setting.test.tsx, apps/desktop/src/app/settings/terminal-font-setting.tsx, apps/desktop/src/app/skills/mcp-tab.tsx

2 PRs closed without merging

From the close comments: merged via another change 2

#111969 fix(desktop): reseed font controls after config refetch · merged via another change → 66f9f36, #112204
#111991 fix(desktop): reseed font controls after profile switches · merged via another change → 66f9f36, #112204

Closed issues · 1

Closed#111963Desktop font controls can remain disabled after config refetch reuses the cached record

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: #112204
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 16 Sep 2026

For your agent

The same facts, typed.

cluster/111963.json
cluster/111963.md