NousResearch/hermes-agent

Empty-content assistant messages with tool_calls causing DeepSeek HTTP 400

Cluster 63200 · agent. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

The three members appear to concern assistant messages that have empty content alongside tool_calls, which is reported to cause an HTTP 400 error from the DeepSeek API. Two titles describe agent-side changes (stripping such messages or normalizing empty content to None); the titles alone do not show whether either approach works or has been merged.

Open issues1

  • Issue#63200Empty-content assistant messages with tool_calls break DeepSeek API (HTTP 400)

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: superseded by another PR 2

  • #63452 fix(agent): normalize empty content to None for assistant messages with tool_calls · superseded by another PR → #12737
  • #64087 fix(agent): strip empty-content+tool_calls assistant messages before API call (#63200) · superseded by another PR → #71787, #63552, #64661, #62353, #61508
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.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
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.