<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Grok on ssnowden.com</title>
    <link>https://ssnowden.com/tags/grok/</link>
    <description>Recent content in Grok on ssnowden.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>ssnowden</copyright>
    <lastBuildDate>Sat, 29 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ssnowden.com/tags/grok/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>From OpenClaw to Grok Bot</title>
      <link>https://ssnowden.com/posts/openclaw-to-grok-bot/</link>
      <pubDate>Sat, 29 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://ssnowden.com/posts/openclaw-to-grok-bot/</guid>
      <description>&lt;h1 id=&#34;from-openclaw-to-grok-bot&#34;&gt;From OpenClaw to Grok Bot&lt;/h1&gt;&#xA;&lt;p&gt;I ran &lt;a href=&#34;https://openclaw.ai&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;OpenClaw&lt;/a&gt;&#xA; on the home network for a while. It connected Claude, Grok, and GPT-4o to Telegram and the other chat apps, ran scheduled jobs, and kept a second brain in vector memory. It did real work. It was also pretty involved to open and keep going.&lt;/p&gt;&#xA;&lt;p&gt;Config lived in JSON. Jobs lived in more JSON. Channels, models, timeouts, cron, log files. If something drifted, it usually failed quiet. I wrote about that earlier: &lt;a href=&#34;https://ssnowden.com/posts/claude-code-openclaw-config/&#34; target=&#34;_blank&#34; rel=&#34;noopener noreferrer&#34;&gt;the best way I found to configure OpenClaw was another AI&lt;/a&gt;&#xA;. I put Claude Code on the same machine just to manage it. Describe the change in English, let Claude Code edit the files, validate, restart. That helped. It also meant I was running two systems so I could keep one of them alive.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
