hermes - 💡(How to fix) Fix Agent: missing newline before continuation when output is truncated [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…

Root Cause

When the LLM output is split across two messages (truncation + continuation), the second message starts directly appended to the first with no newline at the boundary.

Fix Action

Fixed

Code Example

Update DCBugs high

---

Update DC
Bugs high
RAW_BUFFERClick to expand / collapse

Bug: Missing Newline Before Continuation on Truncated Output

Problem

When the agent's response gets truncated by the output length limit, the system sends a "Continue exactly where you left off" message. The agent's continuation text then merges directly into the last line of the previous output, creating garbled text.

Example

✅ Update DC⬜ Bugs high

Should be:

✅ Update DC
⬜ Bugs high

Most visible example from user report: "Update PMCDCWaiting for the remaining 6 fields!" — where "Update PMCDC" was the last item in the truncated output and "Waiting for the remaining 6 fields!" was the continuation with no line break between them.

Root Cause

When the LLM output is split across two messages (truncation + continuation), the second message starts directly appended to the first with no newline at the boundary.

Reproduction

  1. Use Hermes agent via Telegram gateway
  2. Generate a response long enough to trigger truncation
  3. Observe the continuation message merges into the last line of truncated output

Expected Behavior

Continuation should start on a fresh line, preserving formatting of both parts.

Suggested Fix Options

  1. The agent should prefix continuation with \n when responding to "Continue exactly where you left off"
  2. The gateway should ensure a newline boundary between truncated first part and appended continuation
  3. The system prompt for continuation messages should explicitly instruct: "Start your continuation with a newline"

Environment

  • Hermes Agent (latest, commit d62808c37)
  • Telegram gateway
  • Observed across multiple model providers

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