AsyncOpenAI/httpx deadlock in gateway-mode vision tool execution
Cluster 2681 · agent. Data as of
Nothing open on GitHub. Fix merged in #2701 on 26 Mar 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 #2701. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #2701. That is separate from the fix event. - Still open
- Nothing open on GitHub.
The three members all concern an AsyncOpenAI/httpx deadlock reported in gateway mode, particularly during vision tool execution. Two are fix-oriented pull requests (a cross-loop deadlock prevention and a switch to a sync call_llm), and one is an issue describing the problem; their titles do not show whether the problem has been fixed or is still open.
Open issues0
Open PRs0
Fixes on record
-
#2701 fix(agent): prevent AsyncOpenAI/httpx cross-loop deadlock in gateway mode
files:
agent/auxiliary_client.py,tests/test_crossloop_client_cache.py,tools/session_search_tool.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#2682 fix(vision): use sync call_llm to avoid AsyncOpenAI deadlock in gateway mode · superseded by another PR →
#2701
Closed issues · 1
- Closed#2681AsyncOpenAI/httpx deadlocks during vision tool execution in gateway mode
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
- agent
- Merged PRs
- #2701
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 26 Mar 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.