Fix JSON serialization of list/dict terminal scope values
NousResearch/hermes-agent · cluster 101465
Data as of
Nothing open on GitHub. Fix merged in #103643. Check it covers your case.
The short answer
- Known?
- Yes. 7 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #103643. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #103643. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where list/dict config values in terminal profile scope were serialized with str() instead of json.dumps(), breaking docker_volumes and docker_env in certain backend profiles. Multiple fix attempts and related changes address this serialization issue.
Open issues0
Open PRs0
Fixes on record
-
#103643 fix(terminal): profile terminal scope serialises list/dict config as JSON, so docker_volumes/docker_env survive multiplexing (#101465, salvage #101479)
files:
tests/tools/test_terminal_scope_multiplex.py,tools/terminal_scope.py
5 PRs closed without merging
From the close comments: done elsewhere 2 · duplicate 2 · superseded by another PR 1
-
#101472 fix(terminal): serialize list/dict terminal scope values as JSON · done elsewhere →
179e988,#101465,#103643,#101479 -
#101479 fix(terminal): JSON-serialize list/dict values in profile terminal scope · done elsewhere →
179e988,#103643 -
#101546 fix(tools): serialize terminal-scope list/dict config values as JSON (#101465) · duplicate →
#101472 -
#102230 fix(tools): serialize list/dict terminal scope values as JSON · superseded by another PR →
#101472 -
#102293 fix(terminal): serialize list/dict terminal config values with json.dumps instead of str() (#101465) · duplicate →
#101472,#101465
Closed issues · 1
- Closed#101465[Bug]: build_profile_terminal_scope serializes list/dict config values with `str()` instead of `json.dumps()`, breaking terminal for docker-backend profiles served by the unified dashboard
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.29: 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
- Merged PRs
- #103643
- Closed issues
- 1
- Attempts
- 5 PRs closed without merging
- Fix link checked
- 5 Sep 2026