Cairn
NousResearch/hermes-agent

TERMINAL_TIMEOUT=0 causes instant timeout bug

Cluster 85809 · agent. 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.

A bug where setting TERMINAL_TIMEOUT to zero or a non-positive value is silently accepted, causing every command to immediately time out. The members cover the problem report and proposed fixes to fall back to the documented 180-second default in that case.

Open issues1

  • Issue#85809TERMINAL_TIMEOUT=0 silently accepted — causes every command to instantly timeout with 'timed out after 0s'

Open PRs1

  • PR#85811fix(tools): TERMINAL_TIMEOUT<=0 falls back to the documented 180s default

1 PR closed without merging

From the close comments: duplicate 1

  • #85958 fix(terminal): guard against TERMINAL_TIMEOUT=0 (instant timeout) · duplicate → #85811, #85809
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
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/85809.json
cluster/85809.md