hermes - 💡(How to fix) Fix bug: oneshot fails closed without final response while chat -q -Q succeeds [1 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Latest main contains the fail-closed fix for empty oneshot responses, but hermes -z still does not produce a final response for the same Copilot/gpt-5.5 path where hermes chat -q -Q succeeds.

This is a follow-up to the closed empty-success issue: the command now exits nonzero, which is good, but the oneshot path still is not usable as a successful no-edit foreground smoke path for this provider/model.

Root Cause

Latest main contains the fail-closed fix for empty oneshot responses, but hermes -z still does not produce a final response for the same Copilot/gpt-5.5 path where hermes chat -q -Q succeeds.

This is a follow-up to the closed empty-success issue: the command now exits nonzero, which is good, but the oneshot path still is not usable as a successful no-edit foreground smoke path for this provider/model.

Fix Action

Fixed

Code Example

timeout 180 uv run hermes --provider copilot -m gpt-5.5 -z "Reply with exactly: HERMES_Z_OK"

---

timeout 180 uv run hermes -z "Reply with exactly: HERMES_Z_OK" --provider copilot -m gpt-5.5
timeout 180 uv run hermes -m gpt-5.5 --provider copilot -z "Reply with exactly: HERMES_Z_OK"

---

timeout 240 uv run hermes chat --provider copilot -m gpt-5.5 -q "Reply with exactly: HERMES_CHAT_OK" -Q
RAW_BUFFERClick to expand / collapse

Summary

Latest main contains the fail-closed fix for empty oneshot responses, but hermes -z still does not produce a final response for the same Copilot/gpt-5.5 path where hermes chat -q -Q succeeds.

This is a follow-up to the closed empty-success issue: the command now exits nonzero, which is good, but the oneshot path still is not usable as a successful no-edit foreground smoke path for this provider/model.

Environment

  • Repository: isolated fresh clone of NousResearch/hermes-agent
  • HEAD: 1044d9f25d63b48c51fe40af0a4cfeea3b6de516
  • Contains fix commit: 9fbde54b5176b6a2fef198b6d870704a3fd994d6
  • uv run --extra dev pytest tests/hermes_cli/test_tui_resume_flow.py -q: 45 passed
  • Campaign context: briancl2/build-meta-analysis#164 Hermes sidecar reconciliation proof

Reproduce

timeout 180 uv run hermes --provider copilot -m gpt-5.5 -z "Reply with exactly: HERMES_Z_OK"

Also tried equivalent argument orderings:

timeout 180 uv run hermes -z "Reply with exactly: HERMES_Z_OK" --provider copilot -m gpt-5.5
timeout 180 uv run hermes -m gpt-5.5 --provider copilot -z "Reply with exactly: HERMES_Z_OK"

Observed

All three -z invocations:

  • exit status: 1
  • stdout: empty
  • stderr: hermes -z: no final response was produced; treating the run as failed.

Control That Succeeds

timeout 240 uv run hermes chat --provider copilot -m gpt-5.5 -q "Reply with exactly: HERMES_CHAT_OK" -Q

Observed:

  • exit status: 0
  • stdout: HERMES_CHAT_OK
  • BMA foreground stdout validator: PASS
  • stderr only included a session_id line

Expected

If the provider/model can produce a final response through chat -q -Q, oneshot should either:

  1. produce the same final response text to stdout and exit 0; or
  2. surface enough diagnostic context to explain why oneshot cannot use that path.

Boundaries

This report asks for a foreground CLI contract repair only. It does not request retries, queues, schedulers, daemons, controllers, background jobs, or broader autonomy behavior.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix bug: oneshot fails closed without final response while chat -q -Q succeeds [1 pull requests]