<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Clawdline — Blog</title>
    <link>https://clawdline.com/blog/</link>
    <description>Writing about Clawdline: what the app is, why it is shaped the way it is, and what it is actually for.</description>
    <language>en</language>
    <atom:link href="https://clawdline.com/blog/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Claude Code agents fixing bugs you report from your phone, while they refactor</title>
      <link>https://clawdline.com/blog/bugs-from-the-phone/</link>
      <guid isPermaLink="true">https://clawdline.com/blog/bugs-from-the-phone/</guid>
      <description>Round two of refactoring Clawdline with Clawdline: four bugs reported from a phone, fixed in parallel, and a review that stopped a fix worse than the bug it fixed.</description>
      <pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Refactoring with Claude Code agents: one board, separate reviewers, a measurement per step</title>
      <link>https://clawdline.com/blog/refactor-with-an-agent-squad/</link>
      <guid isPermaLink="true">https://clawdline.com/blog/refactor-with-an-agent-squad/</guid>
      <description>How we used Clawdline&apos;s Board, built-in roles and review Sessions to refactor Clawdline itself in one day: daemon CPU from 12.6% to 1.3%, 4,383 lines of product code removed.</description>
      <pubDate>Sun, 18 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Clawdline vs Herdr: which fits the sessions you already run?</title>
      <link>https://clawdline.com/blog/clawdline-herdr/</link>
      <guid isPermaLink="true">https://clawdline.com/blog/clawdline-herdr/</guid>
      <description>Compare Clawdline and Herdr by where your Claude Code or Codex sessions run, how you reconnect from another machine or phone, and what happens after an agent finishes.</description>
      <pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Coding agents waiting on builds: what one night&apos;s callback estimate shows</title>
      <link>https://clawdline.com/blog/heavy-work-callback/</link>
      <guid isPermaLink="true">https://clawdline.com/blog/heavy-work-callback/</guid>
      <description>Clawdline&apos;s Heavy Work callback lets a coding agent stop checking a queued build. One night of polling records suggests 74.3% fewer tokens for those waiting turns.</description>
      <pubDate>Thu, 08 Oct 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Ten Claude Code sessions, one you open: what a session status lets you do</title>
      <link>https://clawdline.com/blog/session-status/</link>
      <guid isPermaLink="true">https://clawdline.com/blog/session-status/</guid>
      <description>Every Clawdline session status names one action, so a list of sessions tells you which one to answer, what you still owe, and which tab is safe to close without opening any of them.</description>
      <pubDate>Mon, 07 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Managing Claude Code and Codex together: Clawdline, Happy, Orca and the official remotes</title>
      <link>https://clawdline.com/blog/how-it-differs/</link>
      <guid isPermaLink="true">https://clawdline.com/blog/how-it-differs/</guid>
      <description>Compare how Clawdline, Happy, Orca, Anthropic Remote Control and Codex on mobile reach your existing sessions or start new work, and where each is limited.</description>
      <pubDate>Sat, 05 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Two Claude Code sessions, one checkout: stopping them committing each other&apos;s work</title>
      <link>https://clawdline.com/blog/rules-that-refuse/</link>
      <guid isPermaLink="true">https://clawdline.com/blog/rules-that-refuse/</guid>
      <description>Several agent sessions in one repository share one git index. The pre-commit check that refuses, the half that can only warn, and how Clawdline knows which line of work a path belongs to.</description>
      <pubDate>Thu, 03 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What a scheduled Claude Code task costs, and when a cron job is the right answer</title>
      <link>https://clawdline.com/blog/three-chores-a-day/</link>
      <guid isPermaLink="true">https://clawdline.com/blog/three-chores-a-day/</guid>
      <description>A timer costs nothing; the session it starts does. What a Clawdline schedule buys over a shell script on cron, which of your chores actually needs one, and the measurement behind both answers.</description>
      <pubDate>Tue, 01 Sep 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Claude Code context window full? Clawdline&apos;s handoff vs just messaging another session</title>
      <link>https://clawdline.com/blog/what-a-handoff-carries/</link>
      <guid isPermaLink="true">https://clawdline.com/blog/what-a-handoff-carries/</guid>
      <description>Why Clawdline has a handoff, what the mechanism is, and how it differs from sending a message to another session. The dividing line is whether they already have your context.</description>
      <pubDate>Sun, 30 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Can a Claude Code agent spawn its own agents? Clawdline gives it one level</title>
      <link>https://clawdline.com/blog/one-level-deep/</link>
      <guid isPermaLink="true">https://clawdline.com/blog/one-level-deep/</guid>
      <description>An agent that hands work out will eventually hand out work you did not ask about. Where Clawdline puts the depth limit so a session cannot argue its way past it, and what the worst case costs.</description>
      <pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Does Claude Code run locally or in the cloud? What leaves your machine, and what a stolen login gets</title>
      <link>https://clawdline.com/blog/where-the-work-runs/</link>
      <guid isPermaLink="true">https://clawdline.com/blog/where-the-work-runs/</guid>
      <description>Claude Code runs in your terminal, and Clawdline keeps it there while your phone watches. What the relay carries, what our side can see field by field, and what a key nobody else holds costs you.</description>
      <pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>What a runaway Claude Code task costs, and how Clawdline lets you cancel at minute three</title>
      <link>https://clawdline.com/blog/work-you-can-cancel/</link>
      <guid isPermaLink="true">https://clawdline.com/blog/work-you-can-cancel/</guid>
      <description>A task going the wrong way looks exactly like one going well. Clawdline asks every task it dispatches to state its plan before it starts, which is what moves the decision to minute three.</description>
      <pubDate>Mon, 24 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>When Claude Code says it&apos;s done: delivered, reviewed, or actually on main?</title>
      <link>https://clawdline.com/blog/delivered-is-not-landed/</link>
      <guid isPermaLink="true">https://clawdline.com/blog/delivered-is-not-landed/</guid>
      <description>One green tick hides four different facts. Clawdline keeps delivered, reviewed, landed and safe-to-close apart, and will not mark a task landed until git says the commit is on your branch.</description>
      <pubDate>Sat, 22 Aug 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>How to manage multiple Claude Code sessions: Clawdline attaches to the ones you already started</title>
      <link>https://clawdline.com/blog/what-clawdline-is/</link>
      <guid isPermaLink="true">https://clawdline.com/blog/what-clawdline-is/</guid>
      <description>A free local daemon and web console for macOS and Linux. Clawdline lists Claude Code and Codex sessions already running on your machine, with four separate statuses for each.</description>
      <pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>
