MoA aggregator ignoring custom provider context length
Cluster 56749 · agent. Data as of
Nothing open on GitHub. Fix merged in #70162 on 23 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #70162. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #70162. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs concern a bug where MoA mode fails to forward custom provider context length configuration to the aggregator, causing it to fall back to a 256K default. Multiple fix attempts address how context metadata is passed through the aggregator resolution path.
Open issues0
Open PRs0
Fixes on record
-
#70162 fix(moa): thread custom-provider context metadata into aggregator context-length resolution (salvage #67071)
files:
agent/model_metadata.py,tests/agent/test_model_metadata.py
2 PRs closed without merging
From the close comments: merged via another change 1 · other 1
Closed issues · 1
- Closed#56749MoA mode: get_model_context_length() does not forward config_context_length/custom_providers to aggregator, forcing 256k default
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.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
- #70162
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 23 Jul 2026