Google Chat multiplex profile scoping fix
Cluster 73439 · gateway. Data as of
Nothing open on GitHub. Fix merged in #101253 on 2 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #101253. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #101253. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items identify and address a bug where Google Chat adapter multiplex profiles incorrectly resolve to the active profile's credentials instead of their own scoped config paths. The fix PR also bundles several adjacent gateway and adapter corrections.
Open issues0
Open PRs0
Fixes on record
-
#101253 fix(gateway): Google Chat scoped + ADC fail-closed, runner bound on all adapters, WhatsApp alias routes, relay profile carry (#73439, salvage #73445 #70831 #85081 #61012)
files:
docs/relay-connector-contract.md,gateway/platform_registry.py,gateway/platforms/ADDING_A_PLATFORM.md,gateway/profile_routing.py,gateway/relay/adapter.py,gateway/relay/ws_transport.py,gateway/run.py,plugins/platforms/google_chat/adapter.py,tests/gateway/relay/test_relay_passthrough.py,tests/gateway/test_google_chat.py,tests/gateway/test_profile_resolution.py,tests/gateway/test_profile_routing.py,website/docs/developer-guide/adding-platform-adapters.md,website/docs/user-guide/messaging/google_chat.md,website/docs/user-guide/multi-profile-gateways.md,website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/developer-guide/adding-platform-adapters.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#73445 fix(google-chat): scope multiplex profile config · merged via another change →
3fcfa64,#101253
Closed issues · 1
- Closed#73439Google Chat adapter has no scoped config path — multiplex profiles all resolve the active profile's credentials
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.00means 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 LabAt a glance
- Subsystem
- gateway
- Merged PRs
- #101253
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 2 Sep 2026