# NousResearch/hermes-agent · asyncio RuntimeWarning from get_event_loop in CLI thread

## Open now

- Nothing open on GitHub.

A bug report and related fix attempts address a noisy RuntimeWarning caused by using get_event_loop() instead of get_running_loop() in the CLI's process_loop thread. The warning is described as harmless but visible on startup.

## 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 #21293. Verify it addresses your case.
- **Recommended:** read PR #21293 (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-21293`. 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

- #19285: \[BUG\] process_loop thread lacks asyncio event loop → RuntimeWarning on startup, harmless but noisy

## Prior & competing PRs

- **#21293: fix(cli): replace get_event_loop() with get_running_loop() (salvage #19435)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `cli.py`, `scripts/release.py`, `tests/test_process_loop_event_loop_warning.py`
- **#19435: fix(cli): replace get_event_loop() with get_running_loop() to silence RuntimeWarning in process_loop thread**. closed without merge
  - maintainer direction: category `silent_close`; implication `active`

## Fix status

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