Dev wires a daily Hermes agent to triage Sentry errors, but it keeps 'forgetting' context

pauljasperdev · reddit · 2026-10-03

A developer describes a duct-taped agent pipeline: a daily Hermes job reads Sentry issues, checks the codebase for existing fixes, cross-references Linear tickets, and files new ones when needed.

The pain points are familiar to anyone running agents in production: the job sometimes fails to run, there's no clear tracking of which fixes are in staging vs. shipped, and the agent intermittently 'forgets' how to access Cloudflare logs or the original Sentry issue mid-task.

The post is asking how others handle state persistence and memory for production-triage agents — a recurring pain point in self-built agent workflows.

Original post →

More from coding & agent

coding & agent channel →