NousResearch/hermes-agent

Mistral list payload and padding field bug fixes

Cluster 106006. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #121534 on 24 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #121534. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: Nothing open on GitHub.

Next step: read #121534, then check it covers your case.

Read #121534 Pick up a Lab task

These issues and fixes address bugs caused by Mistral's 'p' padding field and list-shaped thinking/tool argument payloads breaking streaming and reasoning extraction. The fixes handle stripping, flattening, and type-checking for these unexpected list values in custom provider contexts.

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.

#121534 fix(agent): strip stray arg tags to the line boundary, keep glued-name strip; flatten list thinking payloads

merged to main

files: agent/agent_runtime_helpers.py, contributors/emails/[email protected], hermes_cli/cli_render.py, tests/agent/test_run_agent.py, tests/agent/test_strip_reasoning_tags_cli.py

2 PRs closed without merging

From the close comments: merged via another change 1 · stale or abandoned 1

#106015 fix(agent): flatten list-shaped thinking block payloads in extract_reasoning · merged via another change → cf8b08e, #121534, #106006
#106933 fix(stream): handle Mistral p padding and list tool args for custom providers (#106006) · stale or abandoned

Closed issues · 1

Closed#106006[Bug]: Custom provider (Mistral) streaming breaks after Mistral added `p` padding field — 'list' object has no attribute 'strip' + false "network error" retry loop

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.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

Merged PRs: #121534
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 24 Sep 2026

For your agent

The same facts, typed.

cluster/106006.json
cluster/106006.md