PR #11868: fix(cli): redirect resume status lines to stderr in quiet mode (#11793)

• Repository: NousResearch/hermes-agent
• Author: malaiwah
• State: open | merged: False
• Link: https://github.com/NousResearch/hermes-agent/pull/11868

Description (problem / solution / changelog)

Summary

When hermes chat --quiet --resume <id> -q "..." is used, three status messages were written to stdout via ChatConsole / _cprint:

• ↻ Resumed session <id> (N user messages, M total messages)
• Session <id> found but has no messages. Starting fresh.
• Session not found: <id> / usage hint

This polluted the machine-readable stdout that automation scripts capture with $(...), making it impossible to cleanly separate the agent's answer from the resume banner.

Root cause

_init_agent() prints these messages unconditionally through the Rich console path (ChatConsole().print() → _cprint() → _pt_print() → stdout). Quiet mode only gates agent-internal output; the CLI's own resume diagnostics were not covered.

Fix

Detect quiet mode via getattr(self, "tool_progress_mode", "full") == "off" (set at line 10381 in the quiet-mode path before _init_agent() is called) and route all three messages to stderr as plain text — matching the existing convention for session_id:. Interactive mode is unchanged; it still renders through the Rich ChatConsole path.

Test plan

Tested on v0.10.0 (sha256:9f37fa3ff8d8d83ab9e1b529b1373c598c377b61ecdb90e26c3d310bf04f5904):

# Turn 1 — quiet single-shot (session history is persisted correctly)
SESSION=$(hermes chat --quiet -q "My favourite colour is blue." 2>&1 \
          | grep session_id | awk '{print $2}')

# Turn 2 — quiet resume
STDOUT=$(hermes chat --quiet --resume "$SESSION" \
         -q "What is my favourite colour? One word." 2>/dev/null)
echo "$STDOUT"   # Blue  ← only the answer, no banner

# stderr now carries the resume status (not mixed into stdout)
hermes chat --quiet --resume "$SESSION" \
  -q "What is my favourite colour? One word." 2>&1 >/dev/null
# stderr: ↻ Resumed session ... (N user messages, M total messages)
#         session_id: ...

Note: the underlying session persistence (SQLite write + resume read) was verified to be working correctly in v0.10.0. Both user and assistant messages are saved after a successful quiet single-shot turn, and --resume correctly restores them. The stdout pollution is the only confirmed bug in current code.

Closes #11793

🤖 Generated with Claude Code

Changed files

• cli.py (modified, +30/-11)