Merge conflict markers breaking Hermes installs/updates

NousResearch/hermes-agent · cluster 2348 · hermes cli

Data as of 2026-10-23 11:54 UTC

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

open issues

open PRs

items grouped

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

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

Read #59304 Pick up a Lab task

Multiple issues and fixes address merge conflict markers accidentally shipped in source files (notably web_server.py and cli.py), causing broken installs and updates on Windows and other platforms. The fixes focus on guarding install paths and ensuring update operations reset cleanly rather than leaving conflict markers in place.

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.

#59304 fix(install): guard Windows desktop installs against broken web_server (salvage #59230)

merged to main

files: hermes_cli/main.py, scripts/install.ps1, tests/hermes_cli/test_update_post_pull_syntax_guard.py, tests/test_install_ps1_web_server_syntax_probe.py

1 PR closed without merging

From the close comments: merged via another change 1

#59230 fix(install): guard Windows desktop installs against broken web_server · merged via another change → #59304

Closed issues · 2

Closed#2348'hermes update' can pull non working files
Closed#59004[Bug]: Windows installer ships broken web_server.py (merge conflict markers)

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.39: 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: hermes cli
Merged PRs: #59304
Closed issues: 2
Attempts: 1 PR closed without merging
Fix link checked: 6 Jul 2026

For your agent

The same facts, typed.

cluster/2348.json
cluster/2348.md