hermes - 💡(How to fix) Fix [Feature]: Named/resumable sessions for cron jobs [1 participants]

- A job running every 20 minutes creates 72 new sessions per day
- A job running every hour creates 24 new sessions per day
- Over a month, a single cron job accumulates ~2,160 sessions

These sessions are meaningless monitoring/health-check sessions that carry no conversation history worth preserving. They pollute the session directory, consume disk space, and slow down session enumeration.

Expected Behavior

Cron jobs should support a session parameter that allows specifying a named session to reuse across invocations. For example:

yaml
job:
  name: "Gateway Health Monitor"
  session: "gateway_health_monitor"  # Reuse this session each run
  schedule: "every 20m"


With this, each run of the job appends to the same conversation thread instead of creating a new session. The session would still exist but remain lean — just a short log of each cron run rather than a full isolated conversation.

Benefits

1. Massive session reduction — 72 sessions/day → 1 session forever
2. Cleaner session directory — monitoring jobs no longer pollute session lists
3. Persistent short-term context — if the health check needs to remember the last state (e.g., "gateway was down 3 minutes ago"), it can without creating new sessions
4. Easier debugging — all health check runs are in one place, easy to review timeline of issues

Implementation Notes

- The session name should be a simple string identifier (no special characters)
- If the session doesn't exist on first run, create it
- The session could have a special marker/type to indicate it's a cron-reused session (for session cleanup/rotation logic)
- Optional: support a max_session_history to keep the reused session from growing unbounded