Nothing open on GitHub. Fix merged in #93647 on 24 Aug 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 #93647. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #93647. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where PairingStore.generate_code() writes pairing codes to a path that approval surfaces never read, making DM pairing unusable. The members cover the issue report and two related fix attempts addressing the path resolution and lazy initialization.
Open issues0
Open PRs0
Fixes on record
-
#93647 fix(gateway): DM pairing codes are written where approval surfaces read them (#93449, salvage #93500)
files:
contributors/emails/[redacted:email],gateway/pairing.py,tests/gateway/test_pairing.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#93500 fix(gateway): resolve PairingStore's default pairing dir lazily, not at import time · merged via another change →
#93647
Closed issues · 1
- Closed#93449PairingStore.generate_code() writes pending pairing codes to a path never read back — DM pairing unusable on affected builds
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
- Merged PRs
- #93647
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 24 Aug 2026