hermes - ✅(Solved) Fix fix: only set HERMES_INTERACTIVE when stdin/stdout are real terminals [1 pull requests, 3 comments, 2 participants]

hermes2026-04-29 17:29:51

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.

GitHub issue URL

Helpful · Quick feedback

GitHub stats

NousResearch/hermes-agent#17575•Fetched 2026-04-30 06:46:38

View on GitHub

Comments

Participants

Timeline

Reactions

Author

cxgreat2014

Participants

alt-glitch

cxgreat2014

Timeline (top)

labeled ×4commented ×3cross-referenced ×1referenced ×1

RAW_BUFFERClick to expand / collapse

Problem

In containerized environments (Docker, Paperclip integrations, cron), Hermes Agent is invoked via hermes chat -q with piped stdin/stdout. The cli_main() function unconditionally sets HERMES_INTERACTIVE=1, triggering sudo password prompts and approval prompts even when no user is present. Each prompt waits 45s before timing out.

Expected Behavior

HERMES_INTERACTIVE should only be set when both stdin and stdout are real TTYs. Piped callers should never see interactive prompts.

Steps to Reproduce

echo 'hello' | hermes chat -q — eventually times out after 45s
Run via Paperclip adapter heartbeat — hangs on approval prompt

Proposed Fix

Gate HERMES_INTERACTIVE=1 behind sys.stdin.isatty() && sys.stdout.isatty(). Also handle PermissionError when ~/.hermes/.env is unreadable in non-root container setups.

PR: #16529

extent analysis

TL;DR

Set HERMES_INTERACTIVE based on the presence of a TTY for both stdin and stdout to prevent unnecessary prompts in non-interactive environments.

Guidance

Check the cli_main() function to ensure it correctly sets HERMES_INTERACTIVE only when both sys.stdin.isatty() and sys.stdout.isatty() return True.
Verify that the proposed fix handles PermissionError when ~/.hermes/.env is unreadable in non-root container setups.
Test the fix using the provided steps to reproduce, such as echo 'hello' | hermes chat -q, to ensure it no longer times out.
Consider reviewing PR #16529 for the specific implementation details of the proposed fix.

Example

import sys

def cli_main():
    if sys.stdin.isatty() and sys.stdout.isatty():
        os.environ['HERMES_INTERACTIVE'] = '1'
    # ... rest of the function ...

Notes

The fix assumes that the presence of a TTY for both stdin and stdout is a reliable indicator of an interactive environment. This may not be the case in all scenarios, and additional checks may be necessary.

Recommendation

Apply the proposed fix from PR #16529, as it addresses the root cause of the issue and provides a clear solution to the problem.

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?

#conversation history #tool integration #LLM response #prompt template #container setup

Still need to ship something?

×6

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

hermes - ✅(Solved) Fix fix: only set HERMES_INTERACTIVE when stdin/stdout are real terminals [1 pull requests, 3 comments, 2 participants]

Recommended Tools

GitHub issue graph ai analysis

Fix Action

Fixed

PR fix notes

PR #16529: fix: only set HERMES_INTERACTIVE when stdin/stdout are real terminals

Description (problem / solution / changelog)

What does this PR do?

Related Issue

Type of Change

Changes Made

How to Test

Checklist

Code

Documentation & Housekeeping

For New Skills

Screenshots / Logs

Changed files