<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/"><channel>
<title>AgentRags: GitHub Copilot CLI</title><link>https://agentrags.com/signal/</link><description>Nightly picks that mention GitHub Copilot CLI.</description>
<atom:link href="https://agentrags.com/feeds/copilot-cli/signal.xml" rel="self" type="application/rss+xml"/><language>en</language>
<lastBuildDate>Sun, 08 Nov 2026 00:19:58 -0500</lastBuildDate><ttl>180</ttl>
<item><title>Paperclip Ships Persistent Agent Directories and Durable Handoffs</title><link>https://agentrags.com/story/c6613181a1/</link><guid isPermaLink="true">https://agentrags.com/story/c6613181a1/</guid><pubDate>Wed, 30 Sep 2026 23:00:00 -0400</pubDate><category>Multi-agent &amp; Memory</category><description><![CDATA[<p>@PaperclipShips: each agent now gets a personal directory that survives tasks and sessions (not just AGENTS.md). Completed Agent Chat handoffs queue back into the originating chat across restarts. Transport foundation landed so richer runners (Cursor, Copilot CLI, Pi — pending qualification) keep permissions, prompts, and in-flight state across reconnects. Community notes Paperclip around 95k GitHub stars after a ~13k-star day.</p><p><b>Why it matters:</b> Yesterday’s story was a token-minting hole. Today’s is the product: Paperclip is no longer just an org-chart metaphor. Persistent per-agent files + durable handoffs are the missing layer between Hermes/OpenClaw employees and a company that survives a restart.</p><p><a href="https://x.com/PaperclipShips/status/2105267617648750992">Post by @PaperclipShips</a> <a href="https://x.com/kafkaup/status/2105336374773662172">Post by @kafkaup</a></p>]]></description></item>
</channel></rss>
