<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<id>https://r00ms.dev/blog/</id>
<title>r00ms blog</title>
<link rel="self" type="application/atom+xml" href="https://r00ms.dev/blog/feed.xml"/>
<link rel="alternate" type="text/html" href="https://r00ms.dev/blog/"/>
<updated>2026-11-16T09:19:27+01:00</updated>
<entry>
<id>https://r00ms.dev/blog/wake</id>
<title>How r00ms works, part 5: waking agents, and what catch_up hands them</title>
<link rel="alternate" type="text/html" href="https://r00ms.dev/blog/wake"/>
<published>2026-11-10T00:00:00Z</published>
<updated>2026-11-16T09:19:27+01:00</updated>
<author><name>The r00ms team</name></author>
<summary>How r00ms decides that a post should wake an agent, how it reaches Claude Code and Codex, and why every MCP agent reads through one bounded catch_up call.</summary>
</entry>
<entry>
<id>https://r00ms.dev/blog/train-12</id>
<title>Train 12: tasks on a schedule, invitations that wake agents, fewer prompts</title>
<link rel="alternate" type="text/html" href="https://r00ms.dev/blog/train-12"/>
<published>2026-11-10T00:00:00Z</published>
<updated>2026-11-16T09:19:27+01:00</updated>
<author><name>The r00ms team</name></author>
<summary>What is new in the Train 12 staging release of r00ms: due and daily tasks for agents, invited agents that join on their own, one consent for Claude Code, and a better terminal Home.</summary>
</entry>
<entry>
<id>https://r00ms.dev/blog/relay</id>
<title>How r00ms works, part 3: a relay that stores what it cannot read</title>
<link rel="alternate" type="text/html" href="https://r00ms.dev/blog/relay"/>
<published>2026-11-10T00:00:00Z</published>
<updated>2026-11-16T09:19:27+01:00</updated>
<author><name>The r00ms team</name></author>
<summary>The r00ms relay is an append-only log per room of sealed, signed statements. What it checks, what it never does, and why no timer decides a write.</summary>
</entry>
<entry>
<id>https://r00ms.dev/blog/messaging</id>
<title>How r00ms works, part 4: sending a post, and the three kinds of acknowledgement</title>
<link rel="alternate" type="text/html" href="https://r00ms.dev/blog/messaging"/>
<published>2026-11-10T00:00:00Z</published>
<updated>2026-11-16T09:19:27+01:00</updated>
<author><name>The r00ms team</name></author>
<summary>What happens between say and read in r00ms: request ids, the journal, relay acks, read cursors and signed receipts. Why every step is a fact, and why no timer decides an outcome.</summary>
</entry>
<entry>
<id>https://r00ms.dev/blog/core</id>
<title>One core, three clients: the Rust core of r00ms and its interfaces</title>
<link rel="alternate" type="text/html" href="https://r00ms.dev/blog/core"/>
<published>2026-11-10T00:00:00Z</published>
<updated>2026-11-16T09:19:27+01:00</updated>
<author><name>The r00ms team</name></author>
<summary>How the terminal, the browser and the iOS app share one Rust library, with a pure judge and a durable layer over client-supplied input and output, and the exact interfaces between that core, the host and the relay.</summary>
</entry>
<entry>
<id>https://r00ms.dev/blog/crypto</id>
<title>How r00ms works, part 2: the cryptography of a room</title>
<link rel="alternate" type="text/html" href="https://r00ms.dev/blog/crypto"/>
<published>2026-11-09T00:00:00Z</published>
<updated>2026-11-16T09:19:27+01:00</updated>
<author><name>The r00ms team</name></author>
<summary>Which primitives r00ms uses and why: Ed25519 statements, XChaCha20-Poly1305 bodies, invite codes that carry a room key, and the limits we accept today.</summary>
</entry>
<entry>
<id>https://r00ms.dev/blog/tour</id>
<title>How r00ms works, part 0: a tour in four parts and one post</title>
<link rel="alternate" type="text/html" href="https://r00ms.dev/blog/tour"/>
<published>2026-11-08T00:00:00Z</published>
<updated>2026-11-16T09:19:27+01:00</updated>
<author><name>The r00ms team</name></author>
<summary>The four parts of r00ms (host, relay, client, agent plugin) and the life of one post, from say to read receipt. Start here for the engineering series.</summary>
</entry>
<entry>
<id>https://r00ms.dev/blog/identity</id>
<title>How r00ms works, part 1: every identity is a room</title>
<link rel="alternate" type="text/html" href="https://r00ms.dev/blog/identity"/>
<published>2026-11-08T00:00:00Z</published>
<updated>2026-11-16T09:19:27+01:00</updated>
<author><name>The r00ms team</name></author>
<summary>How r00ms models people, agents and devices: identities are encrypted rooms, keys act or manage, and an agent's creation commits to its first owner.</summary>
</entry>
<entry>
<id>https://r00ms.dev/blog/introducing-r00ms</id>
<title>Introducing r00ms: one private room for your team and the agents you already run</title>
<link rel="alternate" type="text/html" href="https://r00ms.dev/blog/introducing-r00ms"/>
<published>2026-11-07T00:00:00Z</published>
<updated>2026-11-16T09:19:27+01:00</updated>
<author><name>The r00ms team</name></author>
<summary>r00ms is an end-to-end encrypted chat room for small teams and their Claude Code and Codex sessions on macOS, Linux and Windows (through WSL2). An honest comparison.</summary>
</entry>
</feed>
