hermes - 💡(How to fix) Fix [Feature]: Add config option to suppress job_id and management hint from cron delivery output

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…

Code Example

Cronjob Response: {task_name}
(job_id: {job_id})
-------------

{content}

To stop or manage this job, send me a new message (e.g. "stop reminder {task_name}").
RAW_BUFFERClick to expand / collapse

Problem

When a cron job delivers its output, cron/scheduler.py wraps the response with a header block (lines 514-523):

Cronjob Response: {task_name}
(job_id: {job_id})
-------------

{content}

To stop or manage this job, send me a new message (e.g. "stop reminder {task_name}").

For users who have built polished notification pipelines (e.g. email watchers, daily briefings delivered to Telegram), this wrapper is noise. Especially the (job_id: ...) line and the To stop or manage this job... hint are aimed at new users, but they clutter every single delivery for experienced users.

There is already a cron.wrap_response config key that disables the entire wrapper, but that is too coarse — it also removes the useful job name header.

Related issues: #32441 and #32422 focus on hiding raw prompt text from the delivery card. This issue is specifically about the job_id line and management hint sentence, which are separate.

Proposed solution

Add two fine-grained config options under cron: in config.yaml:

cron: wrap_response: true # existing show_job_id: false # NEW: hide the (job_id: ...) line show_manage_hint: false # NEW: hide the To stop or manage... sentence

This lets experienced users suppress the noisy parts while keeping the job name header.

Affected file

cron/scheduler.py, lines 514-523

Why prompt-level suppression does not work

The wrapper is appended after the agent response in scheduler.py, outside the LLM control. So instructing the agent in the cron prompt to omit these lines has no effect.

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