{"repo":"NousResearch/hermes-agent","public_id":"41923","display_label":"Cron silent-log accuracy when agent not invoked","summary":"These issues and PRs address a logging inaccuracy where the cron scheduler incorrectly logs 'agent returned [SILENT]' even when the agent was never invoked due to wakeAgent=false. The work focuses on distinguishing between an agent that ran and returned silent versus one that was skipped entirely.","subsystem":"cron","counts":{"members":4,"open_issues":1,"open_issues_distinct":1,"open_prs":3,"closed_issues":0,"merged_prs":0,"attempt_prs":3},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.5},"fix_edges":[],"members":[{"kind":"issue","number":41923,"title":"[Bug]: Cron scheduler logs “agent returned [SILENT]” when wakeAgent=false skipped the agent entirely","url":null,"state":"open"},{"kind":"pr","number":41928,"title":"fix(cron): distinguish wakeAgent=false from agent-returned [SILENT] in log","url":null,"state":"open","close_reason":{"refs":[{"kind":"commit","value":"f284d85efa308fa2a4169defc455e20d6b51336a","number":0}],"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":42017,"title":"fix(cron): preserve silent-delivery log semantics","url":null,"state":"open","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":42107,"title":"fix(cron): don't log \"agent returned [SILENT]\" when the agent was never invoked","url":null,"state":"open","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}