Cairn
NousResearch/hermes-agent

Google Chat per-user OAuth token key mismatch

Cluster 75492 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

A bug where the /setup-files flow stores the per-user OAuth token under a key that the send path cannot look up, along with two related fix attempts keying the token by email or canonical identity.

Open issues1

  • Issue#75492[Bug]: Google Chat /setup-files stores the per-user OAuth token under a key the send path can never read

Open PRs1

  • PR#75527fix(google_chat): use canonical identity for per-user OAuth token key (#75492)

2 PRs closed without merging

From the close comments: duplicate 1 · partial fix 1

  • #75524 fix(google_chat): key /setup-files OAuth token by email, not resource name (#75492) · partial fix → #75527, #75492, #27016
  • #113587 fix(google_chat): use canonical identity for per-user OAuth token key · duplicate → #27016, #75527, #75492
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

Subsystem
gateway
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/75492.json
cluster/75492.md