# NousResearch/hermes-agent · Configurable per-worker systemd MemoryMax limit

## Open now

- 1 issue, 2 PRs open on GitHub.
- #103670: \[Feature\]: Make per-worker systemd memory limit configurable
- PR #103684: fix(terminal): let local workers exceed the fixed 4 GiB ceiling
- PR #139941: feat(tools): allow widening the per-worker MemoryMax cap via config or env

The three members all concern the fixed per-worker memory ceiling (described as 4 GiB) under systemd and propose making it configurable or raisable, via config or environment settings. One is a feature request and two are changes that appear to implement it; their status is not stated in the titles.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 2 open PR(s), 0 merged PR(s), 0 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. 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.

## Open related issues

- #103670: \[Feature\]: Make per-worker systemd memory limit configurable

## Prior & competing PRs

- **#103684: fix(terminal): let local workers exceed the fixed 4 GiB ceiling**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `cli-config.yaml.example`, `hermes_cli/config_defaults.py`, `tests/tools/test_process_registry.py`, `tools/process_registry.py`, `website/docs/user-guide/configuration.md`
- **#139941: feat(tools): allow widening the per-worker MemoryMax cap via config or env**. open
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `337f374426`
  - files: `cli-config.yaml.example`, `hermes_cli/config_defaults.py`, `tests/tools/test_process_registry_memory.py`, `tools/process_registry.py`, `tools/process_registry_memory.py`, `website/docs/reference/environment-variables.md`, `website/docs/user-guide/configuration.md`

## Fix status

- No merged fix on record.
- Subsystem: `agent`