<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Automation on emsenn.net</title>
    <link>https://emsenn.net/tags/automation/</link>
    <description>Recent content in Automation on emsenn.net</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 09 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://emsenn.net/tags/automation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>OpenClaw HEARTBEAT.md</title>
      <link>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/artificial-intelligence/domains/agents/terms/openclaw-heartbeat/</link>
      <pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/artificial-intelligence/domains/agents/terms/openclaw-heartbeat/</guid>
      <description>&lt;p&gt;OpenClaw HEARTBEAT.md is an optional workspace file that defines what&#xA;the assistant should check or notice when it is idle. It is the main&#xA;configuration surface for low-frequency proactive behavior.&lt;/p&gt;&#xA;&lt;h2 id=&#34;role&#34;&gt;&lt;a href=&#34;#role&#34; class=&#34;heading-anchor&#34; aria-label=&#34;Link to this section&#34;&gt;¶&lt;/a&gt;Role&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;The official heartbeat documentation describes &lt;code&gt;HEARTBEAT.md&lt;/code&gt; as a&#xA;small checklist that the default prompt reads on a regular heartbeat.&#xA;Independent guides distinguish it from cron: cron handles scheduled&#xA;tasks at exact times, while &lt;code&gt;HEARTBEAT.md&lt;/code&gt; handles opportunistic&#xA;awareness and gentle proactive suggestions.&lt;/p&gt;</description>
    </item>
    <item>
      <title>OpenClaw Hook</title>
      <link>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/artificial-intelligence/domains/agents/terms/openclaw-hook/</link>
      <pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/domains/artificial-intelligence/domains/agents/terms/openclaw-hook/</guid>
      <description>&lt;p&gt;An OpenClaw hook is a directory-discovered event handler that runs when&#xA;command or lifecycle events fire inside the Gateway. Hooks are the&#xA;event-driven automation layer of OpenClaw.&lt;/p&gt;&#xA;&lt;h2 id=&#34;structure&#34;&gt;&lt;a href=&#34;#structure&#34; class=&#34;heading-anchor&#34; aria-label=&#34;Link to this section&#34;&gt;¶&lt;/a&gt;Structure&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;The official hooks docs describe a hook as a directory containing&#xA;&lt;code&gt;HOOK.md&lt;/code&gt; plus a TypeScript handler. Hooks are discovered from&#xA;workspace, managed, and bundled directories, with workspace hooks&#xA;having highest precedence.&lt;/p&gt;&#xA;&lt;h2 id=&#34;role&#34;&gt;&lt;a href=&#34;#role&#34; class=&#34;heading-anchor&#34; aria-label=&#34;Link to this section&#34;&gt;¶&lt;/a&gt;Role&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Hooks let operators attach automation to events such as &lt;code&gt;/new&lt;/code&gt;,&#xA;bootstrap, or gateway startup. The bundled &lt;code&gt;session-memory&lt;/code&gt;,&#xA;&lt;code&gt;bootstrap-extra-files&lt;/code&gt;, &lt;code&gt;command-logger&lt;/code&gt;, and &lt;code&gt;boot-md&lt;/code&gt; hooks show the&#xA;main current uses: memory capture, workspace augmentation, audit&#xA;logging, and startup actions.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
