# NousResearch/hermes-agent · Prevent duplicate managed router port binding

## Open now

- Nothing open on GitHub.

These items address a race condition where two local runtime desktop backends booting simultaneously both attempt to bind port 18434 and start separate managed routers. The work involves serializing the managed runtime boot process across processes so only one router starts.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #117600. Verify it addresses your case.
- **Recommended:** read PR #117600 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-117600`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #116682: Local runtime: two desktop backends booting together both bind 18434 and run two managed routers (cross-process cousin of #113325)

## Prior & competing PRs

- **#117600: fix(local-runtime): two backends booting together start one managed router, not two on 18434 (#116682, salvage #116742)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/local_runtime/bootstrap.py`, `tests/hermes_cli/test_local_runtime.py`
- **#116742: fix(local-runtime): serialize managed runtime boot across processes**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `56b7a0fb37`, `#117600`

## Fix status

- Merged to main in PR #117600 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-20`.