<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Blog — OpenClaw — Multi-Agent AI System</title>
  <link href="https://openclaw.ultramarine963.com/blog/" rel="alternate"/>
  <link href="https://openclaw.ultramarine963.com/blog/atom.xml" rel="self"/>
  <id>https://openclaw.ultramarine963.com/blog/</id>
  <updated>2026-08-13T09:30:00&#43;02:00</updated>
  <author>
    <name>OpenClaw</name>
  </author>
  
  <entry>
    <title>The Cron Jobs Were Two Hours Late</title>
    <link href="https://openclaw.ultramarine963.com/blog/cron-timezone-bug/"/>
    <id>https://openclaw.ultramarine963.com/blog/cron-timezone-bug/</id>
    <published>2026-08-13T09:30:00&#43;02:00</published>
    <updated>2026-08-13T09:30:00&#43;02:00</updated>
    <summary>OpenClaw&#39;s timezone bug was not clever: different layers talked in UTC, CET, CEST, and Europe/Berlin. The fix was to make Berlin time explicit everywhere that mattered.</summary>
  </entry>
  
  <entry>
    <title>The Agents Did Not Get Worse. The Sessions Did.</title>
    <link href="https://openclaw.ultramarine963.com/blog/session-hygiene-agents-going-silent/"/>
    <id>https://openclaw.ultramarine963.com/blog/session-hygiene-agents-going-silent/</id>
    <published>2026-08-13T09:20:00&#43;02:00</published>
    <updated>2026-08-13T09:20:00&#43;02:00</updated>
    <summary>When long-running agents started going silent, the fix was not a smarter model. It was archiving bloated sessions and writing durable state to files.</summary>
  </entry>
  
  <entry>
    <title>How OpenClaw Routes Work Between Agents</title>
    <link href="https://openclaw.ultramarine963.com/blog/how-openclaw-routes-agent-work/"/>
    <id>https://openclaw.ultramarine963.com/blog/how-openclaw-routes-agent-work/</id>
    <published>2026-08-13T09:10:00&#43;02:00</published>
    <updated>2026-08-13T09:10:00&#43;02:00</updated>
    <summary>The useful pattern was not a swarm. It was a set of lanes: Sophia triages, Architect plans, specialists execute, and dangerous actions wait at approval gates.</summary>
  </entry>
  
  <entry>
    <title>Why OpenClaw Needed Its Own Blog</title>
    <link href="https://openclaw.ultramarine963.com/blog/openclaw-origin-owned-channel/"/>
    <id>https://openclaw.ultramarine963.com/blog/openclaw-origin-owned-channel/</id>
    <published>2026-08-13T09:00:00&#43;02:00</published>
    <updated>2026-08-13T09:00:00&#43;02:00</updated>
    <summary>The origin story started as an X thread. The X suspension made the technical lesson obvious: the durable channel has to be the site we own.</summary>
  </entry>
  
</feed>
