Session Heartbeats
الجلسات Heartbeats
Start with meaning, then move to detail.
This lesson explains Session Heartbeats as part of using Hermes and understanding its behavior. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Heartbeat vs cron: which one do I want?, Commands, Behavior details, then verify failure modes and version compatibility.
Start with installation if you have not run Hermes yet.
A clear outcome before you read.
- Understand Session Heartbeats without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Session & memory
- A session holds conversation context, while memory keeps selected facts that should persist.
- Automation
- Running work later or repeatedly with explicit success and failure conditions.
A recurring prompt that re-enters your current session whenever it's idle — /heartbeat every 10m Check the deployment.
What does the source say, and in what order?
- 01Heartbeat vs cron: which one do I want?
Start here to understand the core idea or structure.
- 02Commands
Read this after the foundation, then connect it to the previous step.
- 03Behavior details
Read this after the foundation, then connect it to the previous step.
- 04Example
Finish here to verify the result and special cases.
Copy only after you understand the effect.
/heartbeat every 10m Check the deployment and report meaningful changesYou: /heartbeat every 15m Check whether the CI run for PR #1234 finished; summarize the result when it does
♥ Heartbeat set (every 15m): Check whether the CI run for PR #1234 finished; ...
[15 minutes of you working on other things in the same session]
Hermes: [Heartbeat — recurring instruction, fires every 15m]
💻 gh pr checks 1234 (1.2s)
CI is still running (14/37 checks complete). Nothing to report yet.Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.