Cairn

DeepSeek API limits and toolset config bugs

NousResearch/hermes-agent · cluster 29418 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

2open issues
1open PR
7items grouped
Known?
Yes. 7 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 3 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
2 issues and 1 PR.

Several issues address DeepSeek-specific API constraints including body size preflight checks, reasoning timeout floors, and streaming/protocol errors, plus separate toolset configuration bugs where YAML string values are incorrectly iterated character-by-character.

Open issues2

  • Issue#30771No preflight size check before DeepSeek API calls — silent 400 on bodies over ~880KB
  • Issue#61264[Bug]: NVIDIA NIM (deepseek-ai/deepseek-v4-pro) fails with RemoteProtocolError while direct API calls succeed

Open PRs1

  • PR#114685fix(agent): preflight body-size check for DeepSeek API (#30771) (salvage of #30809)

3 PRs closed without merging

From the close comments: done elsewhere 1 · stale or abandoned 1 · superseded by another PR 1

  • #30809 fix(agent): preflight body-size check for DeepSeek API (#30771) · superseded by another PR → #114685
  • #61324 fix(tools): normalize disabled_toolsets from YAML to prevent silent toolset config loss (#61264) · stale or abandoned
  • #65452 fix(toolsets): coerce string-typed toolset lists instead of iterating characters · done elsewhere → 309cf2c
Closed issues · 1
  • Closed#29418[Bug]: Nous inference API streaming times out on agent-sized payloads — non-streaming works fine
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.22: 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
Closed issues
1
Attempts
3 PRs closed without merging

For your agent

The same facts, typed.

cluster/29418.json
cluster/29418.md