One-shot mode file logging fix

NousResearch/hermes-agent · cluster 103056 · hermes cli

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 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 2 PRs.

A bug where one-shot (hermes -z) mode suppressed file logging to agent.log and errors.log, along with multiple fix attempts addressing stderr silencing without breaking file output.

Open issues1

  • Issue#103056[Bug]: `hermes -z` writes nothing to agent.log or errors.log

Open PRs2

  • PR#103065fix(cli): one-shot runs must still write agent.log and errors.log (#103056)
  • PR#103699fix(cli): keep file logging alive in one-shot mode

1 PR closed without merging

From the close comments: duplicate 1

  • #103972 fix(cli): silence stderr without disabling file logging in oneshot (#103056) · duplicate → #103699, #103065, #103056
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.50: 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
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.