NousResearch/hermes-agent

API server leaking per-request Codex app-server processes

Cluster 137451 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

The members concern an API server that reportedly leaves a codex app-server child process running for each request because the per-request agent is never freed, affecting thread resume. Two related fix-oriented pull requests propose freeing the agent's clients or closing each turn's child process when the turn ends.

Open issues1

  • Issue#137451API server leaks a `codex app-server` process per request (agent never released), breaking thread resume

Open PRs1

  • PR#137464fix(api-server): close each turn's Codex app-server child (#137451)

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #137463 fix(api-server): release the per-request agent's clients when its turn ends · superseded by another PR → #137464, #137451
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.67: 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
gateway
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.