--- title: "dev (@rotiferdev) | Hashnode" description: "dev (@rotiferdev) writes on Hashnode. Read their latest articles and follow their work." url: "https://hashnode.com/@rotiferdev" --- @rotiferdev # dev @rotiferdev · Joined March 2026 ### [Rotifer v0.9.4: Agents get a memory of their own (npm 0.33.0)](https://rotifer.hashnode.dev/rotifer-v0-9-4-agents-get-a-memory-of-their-own-npm-0-33-0?utm_source=hashnode&utm_medium=feed) An agent now keeps a memory its genes read and write between runs. It belongs to the agent, so swapping a gene keeps it. Four categories, a quota with a fixed cleanup order, access scopes and retention, all stored on your machine. 7 min read · [rotifer.hashnode.dev](https://rotifer.hashnode.dev/rotifer-v0-9-4-agents-get-a-memory-of-their-own-npm-0-33-0?utm_source=hashnode&utm_medium=feed) [Nov 1](https://hashnode.com/posts/rotifer-v0-9-4-agents-get-a-memory-of-their-own-npm-0-33-0/6af469c7ee3296df916855a4) ### [Rotifer v0.9.3: Genes scored against the season, run with the permissions they declare (npm 0.30.0)](https://rotifer.hashnode.dev/rotifer-v0-9-3-genes-scored-against-the-season-run-with-the-permissions-they-declare-npm-0-30-0?utm_source=hashnode&utm_medium=feed) Arena F(g) now compares a gene's measured latency and cost with the season median of its peers. Every CLI path runs a gene with exactly the permissions its phenotype declares, and each outbound request is checked before it is sent. 5 min read · [rotifer.hashnode.dev](https://rotifer.hashnode.dev/rotifer-v0-9-3-genes-scored-against-the-season-run-with-the-permissions-they-declare-npm-0-30-0?utm_source=hashnode&utm_medium=feed) [Oct 24](https://hashnode.com/posts/rotifer-v0-9-3-genes-scored-against-the-season-run-with-the-permissions-they-declare-npm-0-30-0/6ae4489175d75056f311c780) ### [Rotifer v0.9.2: Export an agent to one file, rebuild it on another machine (npm 0.29.0)](https://rotifer.hashnode.dev/rotifer-v0-9-2-export-an-agent-to-one-file-rebuild-it-on-another-machine-npm-0-29-0?utm_source=hashnode&utm_medium=feed) rotifer genome export writes an agent's genome to a .rgenome file; rotifer genome import rebuilds it from the Registry and says, gene by gene, what it installed and why. Four changes in 0.29.0 may affect existing use. 8 min read · [rotifer.hashnode.dev](https://rotifer.hashnode.dev/rotifer-v0-9-2-export-an-agent-to-one-file-rebuild-it-on-another-machine-npm-0-29-0?utm_source=hashnode&utm_medium=feed) [Oct 21](https://hashnode.com/posts/rotifer-v0-9-2-export-an-agent-to-one-file-rebuild-it-on-another-machine-npm-0-29-0/6af1447bd4187a8a94129de2) ### [Rotifer v0.9.1: Content-derived gene IDs for the LAN P2P node (npm 0.27.0)](https://rotifer.hashnode.dev/rotifer-v0-9-1-content-derived-gene-ids-for-the-lan-p2p-node-npm-0-27-0?utm_source=hashnode&utm_medium=feed) A gene's ID now comes from its content, not its name. The LAN P2P wire format is frozen and validated before relay. Two machines, one Wi-Fi, 1.4 s. 7 min read · [rotifer.hashnode.dev](https://rotifer.hashnode.dev/rotifer-v0-9-1-content-derived-gene-ids-for-the-lan-p2p-node-npm-0-27-0?utm_source=hashnode&utm_medium=feed) [Oct 19](https://hashnode.com/posts/rotifer-v0-9-1-content-derived-gene-ids-for-the-lan-p2p-node-npm-0-27-0/6af13582c06d737e50fab73d) ### [Rotifer Now Installs into DeepSeek Harness](https://rotifer.hashnode.dev/rotifer-now-installs-into-deepseek-harness?utm_source=hashnode&utm_medium=feed) DeepSeek Harness is in developer preview and says openly it will make breaking changes. We shipped into it by declaring configuration that mounts the harness's own components — so there is nothing of ours for an API change to break. 7 min read · [rotifer.hashnode.dev](https://rotifer.hashnode.dev/rotifer-now-installs-into-deepseek-harness?utm_source=hashnode&utm_medium=feed) [Aug 18](https://hashnode.com/posts/rotifer-now-installs-into-deepseek-harness/6af125153f5c2161bacf6a10)