Cairn

Desktop OAuth net.request header errors and fixes

NousResearch/hermes-agent · cluster 40069 · apps/desktop

Data as of

Nothing open on GitHub. Fix merged in #40628. Check it covers your case.

The short answer

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

These items cluster around ERR_INVALID_ARGUMENT errors on Electron's net.request caused by manually setting restricted headers (notably Content-Length) in the desktop OAuth and session request paths, along with related header-handling edge cases and regression tests.

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.

  • #40628 test(desktop): regression-guard fetchJsonViaOauthSession headers (#40069)

    merged to main

    files: apps/desktop/electron/oauth-session-request.test.cjs, apps/desktop/package.json

4 PRs closed without merging

From the close comments: superseded by another PR 1 · other 3

  • #40115 fix(desktop): let oauth net requests set length · superseded by another PR → #40242
  • #40118 fix(desktop): drop manual Content-Length on Electron net.request OAuth path · other → #40115
  • #40242 test(desktop): cover oauth session request headers · other → #40628
  • #64059 fix(desktop): fetchJson omits X-Hermes-Session-Token when token is nullish (#63707) · other → #71783
Closed issues · 3
  • Closed#40069Desktop (remote gateway, OAuth mode): saving settings fails with net::ERR_INVALID_ARGUMENT — manual Content-Length on Electron net.request
  • Closed#40215[Desktop]: error invoking remote method 'hermes:api': Error: net::ERR_INVALID_ARGUMENT
  • Closed#63707Desktop remote gateway (password auth): session mutations fail with net::ERR_INVALID_ARGUMENT
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.20: 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
apps/desktop
Merged PRs
#40628
Closed issues
3
Attempts
4 PRs closed without merging
Fix link checked
6 Jul 2026

For your agent

The same facts, typed.

cluster/40069.json
cluster/40069.md