# NousResearch/hermes-agent · Cron job output visibility in agent sessions

## Open now

- 6 issues, 0 PRs open on GitHub.
- #5712: \[Feature\]: True Autonomy - Automatically Inject Cron Results into Live Gateway Chat Sessions
- #8793: \[Feature\]: Synchronize Cron Job outputs into interactive session history for seamless context-aware follow-ups
- #24246: Cron delivery knowledge gap: agent cannot see messages sent to user
- #37070: Agent has no awareness of information delivered by its own cron jobs
- #50987: Feature: optionally record cron/proactive deliveries into the live conversation session
- #52073: When opening the Hermes TUI (desktop app), the agent cannot proactively speak

These issues and PRs concern making cron job results and scheduled outputs observable within the agent's conversational session and memory, so the agent can reference or act on what its own scheduled jobs produced. A related thread covers injecting messages into live gateway/bridge sessions.

## TL;DR

- 13 member(s): 6 open issue(s), 3 closed issue(s), 0 open PR(s), 0 merged PR(s), 4 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_PARTIAL`): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
- Members outside that structural core may belong to a different underlying problem.
- Pairwise link density `0.12`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Open related issues

- #5712: \[Feature\]: True Autonomy - Automatically Inject Cron Results into Live Gateway Chat Sessions
- #8793: \[Feature\]: Synchronize Cron Job outputs into interactive session history for seamless context-aware follow-ups
- #24246: Cron delivery knowledge gap: agent cannot see messages sent to user
- #37070: Agent has no awareness of information delivered by its own cron jobs
- #50987: Feature: optionally record cron/proactive deliveries into the live conversation session
- #52073: When opening the Hermes TUI (desktop app), the agent cannot proactively speak

## Closed / duplicate issues

- #2704: feat: cron job execution results should be written back to conversational memory
- #2990: feat: conversational cron delivery - trigger agent response from scheduled jobs
- #4595: \[Feature Request\]: Cron Job Results Should Be Observable and Interactable by the Main Agent Session

## Prior & competing PRs

- **#2733: feat(cron): log execution results to memories/cron_log.md**. closed without merge
  - maintainer direction: category `volume_quota`; implication `active`
- **#4696: feat(cron): write execution summary to agent memory after job completion**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`
- **#5659: feat: conversational cron delivery — inject scheduled output into agent session**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `b693bee100bd163bd9e18e3c2c68179190bdc4ae`, `#2990`
- **#7400: feat(cron): add opt-in session history delivery**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`

## Fix status

- No merged fix on record.
- Subsystem: `apps/desktop`