NousResearch/hermes-agent

Linux GPU-child init failure and CPU retry loop

Cluster 124843. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #128206 on 1 Oct 2026. Check it covers your case.

open issues

open PRs

items grouped

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

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

Read #128206 Pick up a Lab task

A bug report and two related fixes addressing GPU child process initialization failures on Linux Mesa/Wayland, where a retry loop causes excessive CPU usage. The fixes introduce sandbox recovery steps and a one-shot software fallback to prevent indefinite looping.

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.

#128206 fix(desktop): bound Linux GPU-child recovery — sandbox ladder first, software fallback on relapse

merged to main

files: apps/desktop/electron/linux-gpu-fallback.test.ts, apps/desktop/electron/linux-gpu-fallback.ts, apps/desktop/electron/main.ts, apps/desktop/electron/windows-sandbox-fallback.test.ts, apps/desktop/electron/windows-sandbox-fallback.ts

1 PR closed without merging

From the close comments: superseded by another PR 1

#124898 fix(desktop): one-shot software fallback for Linux GPU-child init failures · superseded by another PR → #128206, #124843

Closed issues · 1

Closed#124843[Bug]: Desktop GPU child never initializes on Mesa/Wayland - sub-zygote burns ~350% CPU in init-retry loop from launch, survives restart + update + cache clear

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.67: 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: #128206
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 1 Oct 2026

For your agent

The same facts, typed.

cluster/124843.json
cluster/124843.md