<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Claude Cowork on The road</title><link>https://kane.mx/tags/claude-cowork/</link><description>Recent content in Claude Cowork on The road</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 13 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://kane.mx/tags/claude-cowork/index.xml" rel="self" type="application/rss+xml"/><item><title>Own Your Agents' Memory: Self-Hosted mem9 on AWS</title><link>https://kane.mx/posts/2026/self-hosted-agent-memory-mem9-on-aws/</link><pubDate>Thu, 13 Aug 2026 00:00:00 +0000</pubDate><guid>https://kane.mx/posts/2026/self-hosted-agent-memory-mem9-on-aws/</guid><description>
&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>Every agent session starts amnesic. You explain your deployment topology to Claude Code on Monday, and on Tuesday Codex asks the same question. You tell one agent that Aurora MySQL cannot run your vector workload, and the next agent cheerfully proposes it. The knowledge that actually compounds — decisions and their rationale, environment quirks, the gotcha that cost you an afternoon — evaporates at the end of every context window.&lt;/p>
&lt;p>&lt;a href="https://kane.mx/posts/2026/self-hosted-agent-memory-mem9-on-aws/">Read More&lt;/a>&lt;/p></description></item></channel></rss>