Cairn
NousResearch/hermes-agent

Updater's gh auth token capture polluted by wrapper stdout

Cluster 138444 · hermes cli. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

The members concern the update check using raw gh auth token stdout as a GitHub Bearer credential, which can include extra output from a stdout-printing gh wrapper and lead to an "Invalid header value" error. One item is a bug report and two are fix pull requests that propose keeping such output out of the credential or treating it as no token.

Open issues1

  • Issue#138444[Bug]: updater sends raw `gh auth token` stdout as the Bearer token — any stdout-printing wrapper breaks every update with "Invalid header value"

Open PRs2

  • PR#138457fix(cli): treat a wrapper-polluted gh auth token capture as no token
  • PR#138485fix(update-check): keep a stdout-printing gh wrapper out of the GitHub credential
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

Subsystem
hermes cli
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/138444.json
cluster/138444.md