<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>The Loop by Bytefo</title><description>A public R&amp;D notebook: self-set challenges, shipped in the open.</description><link>https://loop.bytefo.com/</link><language>en-gb</language><item><title>Issue 03: If you mock the shell, you aren’t testing the agent.</title><link>https://loop.bytefo.com/issues/03-rooklight/</link><guid isPermaLink="true">https://loop.bytefo.com/issues/03-rooklight/</guid><description>A test harness for an autonomous coding agent has to wait on real jobs, assert on tool trajectories, and refuse to stub the filesystem. The first version slept for thirty seconds and called that engineering. We still do not know how to cache the fixtures.</description><pubDate>Thu, 10 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Issue 02: The UI is calm. The intelligence is under the hood.</title><link>https://loop.bytefo.com/issues/02-save4later/</link><guid isPermaLink="true">https://loop.bytefo.com/issues/02-save4later/</guid><description>An Android-first personal knowledge corpus. Capture is almost free; synthesis is expensive; the library on the phone and the graph on the server tell different stories. We nearly wiped a live Room database to make a demo green.</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Issue 01: The planner that thinks like a local.</title><link>https://loop.bytefo.com/issues/01-travel-ruter/</link><guid isPermaLink="true">https://loop.bytefo.com/issues/01-travel-ruter/</guid><description>An AI travel planner that has to look local while every upstream API is late, rate-limited, or politely wrong. We used to block the map on live data. Now the itinerary is a document with timestamps, and the live calls are a sprinkle. We still do not have a language for ‘this might be stale.’</description><pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate></item></channel></rss>