Cairn
NousResearch/hermes-agent

Handle 401 on desktop readiness probe endpoints

Cluster 71514. Data as of

Nothing open on GitHub. Fix merged in #71714 on 26 Jul 2026. Check it covers your case.

The short answer

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

These items address how the desktop client handles 401 responses from gated readiness probe endpoints, including authentication, fallback behavior, and keeping the reauth overlay interactive.

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.

  • #71714 fix(desktop): connect to gated remote gateways that 401 the readiness probe

    merged to main

    files: apps/desktop/electron/backend-health.test.ts, apps/desktop/electron/backend-health.ts, apps/desktop/electron/backend-start-failure.test.ts, apps/desktop/electron/backend-start-failure.ts, apps/desktop/electron/main.ts, apps/desktop/electron/native-auth-decisions.test.ts, apps/desktop/electron/native-auth-decisions.ts, contributors/emails/[redacted:email], contributors/emails/[redacted:email], contributors/emails/[redacted:email], contributors/emails/[redacted:email]

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #71449 fix(desktop): authenticate the boot readiness probe and keep the reauth overlay clickable · superseded by another PR → #71714
Closed issues · 1
  • Closed#71514Desktop cloud/remote readiness loops on 401 from gated /api/health; should fall back to public /api/status
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
#71714
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
26 Jul 2026

For your agent

The same facts, typed.

cluster/71514.json
cluster/71514.md