Cairn

Kimi CN brotli streaming decompression returns empty responses

NousResearch/hermes-agent · cluster 28043 · agent

Data as of

Nothing open on GitHub. Fix merged in #121511. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 3 issues already closed.
Fix event
A fix was merged to main in PR #121511. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #121511. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues report a bug where brotli-encoded streaming responses from the Kimi CN API (api.moonshot.cn) result in empty output. A proposed workaround involves overriding Accept-Encoding to request gzip instead.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #121511 fix(streaming): Kimi gzip-only streams, 16 MiB LSP stderr lines, serving provider in stream-drop logs

    merged to main

    files: agent/api_request_hooks.py, agent/chat_completion_helpers.py, agent/lsp/client.py, agent/stream_diag.py, contributors/emails/[redacted:email], plugins/model-providers/kimi-coding/__init__.py, tests/agent/lsp/_mock_lsp_server.py, tests/agent/lsp/test_client_e2e.py, tests/agent/test_stream_serving_provider.py, tests/plugins/model_providers/test_kimi_profile.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #71068 fix(kimi): exclude brotli from Accept-Encoding to work around httpx/brotlicffi streaming decode bug · merged via another change → 56096cb, #121511, #28043
Closed issues · 3
  • Closed#28043[Bug]: Kimi CN (api.moonshot.cn) brotli streaming decompression causes empty responses
  • Closed#28049[Bug]: Kimi CN (api.moonshot.cn) brotli streaming decompression causes empty responses
  • Closed#48428kimi-coding provider: brotli streaming decode bug — need Accept-Encoding: gzip workaround
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.31: 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
agent
Merged PRs
#121511
Closed issues
3
Attempts
1 PR closed without merging
Fix link checked
24 Sep 2026

For your agent

The same facts, typed.

cluster/28043.json
cluster/28043.md