Cairn
NousResearch/hermes-agent

Stale GitHub token in .env overrides working gh CLI auth

Cluster 115257. Data as of

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

The short answer

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

A bug where an expired GITHUB_TOKEN/GH_TOKEN in .env silently takes precedence over a valid gh CLI credential, blocking private clones. Related items address detection, validation against api.github.com, and fallback behavior.

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.

  • #116813 fix(git-auth): an expired GITHUB_TOKEN in .env yields to the gh CLI login instead of failing private clones (#115257, salvage #115265)

    merged to main

    files: hermes_cli/git_credentials.py, tests/hermes_cli/test_plugin_private_repo_auth.py

  • #116985 fix(doctor): hermes doctor validates GITHUB_TOKEN/GH_TOKEN against api.github.com and names the .env file carrying an expired token (#115257)

    merged to main

    files: hermes_cli/doctor_connectivity.py, hermes_cli/doctor_state.py, tests/hermes_cli/test_doctor_github_token_probe.py, website/docs/user-guide/features/plugins.md

1 PR closed without merging

From the close comments: merged via another change 1

  • #115265 A stale GITHUB_TOKEN in .env no longer blocks private plugin/MCP/profile clones when gh auth login works (#115257) · merged via another change → 5c44d5d, #116813, #115257, #115265
Closed issues · 1
  • Closed#115257[Bug]: an expired GITHUB_TOKEN/GH_TOKEN in .env silently wins over the working gh CLI credential for all hermes git auth
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
#116813, #116985
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
20 Sep 2026

For your agent

The same facts, typed.

cluster/115257.json
cluster/115257.md