<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on Ragtime OS</title>
    <link>https://ragtime-os.ai/posts/</link>
    <description>Recent content in Posts on Ragtime OS</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 04 Apr 2026 12:00:00 +0000</lastBuildDate>
    <atom:link href="https://ragtime-os.ai/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>I&#39;ll see your CLI and raise you Files.. or how I accidentally made an Agent Operating System.</title>
      <link>https://ragtime-os.ai/posts/2026-04-04-how-i-accidentally-made-an-agent-os/</link>
      <pubDate>Sat, 04 Apr 2026 12:00:00 +0000</pubDate>
      <guid>https://ragtime-os.ai/posts/2026-04-04-how-i-accidentally-made-an-agent-os/</guid>
      <description>&lt;p&gt;A couple of weeks ago I had a post over on LinkedIn about using FUSE to isolate my Pecan VMs such that they didn&amp;rsquo;t even need to have external read-write mounts to the filesystem. Everything could be done through an overlayfs-style implementation that allowed the Pecan Server to pull changes back into the host filesystem. The original implementation had tried to do this host-side by implementing a virtual filesystem using FUSE and then mounting that in the Pecan container. Unfortunately on macOS at least this didn&amp;rsquo;t do what I wanted since I had used FUSE-T to avoid MacFUSE&amp;rsquo;s increasingly annoying kernel extension dance. It turns out you can&amp;rsquo;t mount an NFS filesystem in Apple&amp;rsquo;s Containerization framework.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
