<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Hansjoerg Hofer</title>
    <description>The latest articles on DEV Community by Hansjoerg Hofer (@hansjoerg_hofer_b284afc63).</description>
    <link>https://dev.to/hansjoerg_hofer_b284afc63</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3535196%2F389a5c8c-2cee-47d6-8cfa-d7d10c439840.jpg</url>
      <title>DEV Community: Hansjoerg Hofer</title>
      <link>https://dev.to/hansjoerg_hofer_b284afc63</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/hansjoerg_hofer_b284afc63"/>
    <language>en</language>
    <item>
      <title>I Was Tired of AI Agents Forgetting Everything, So I Built a Zero-Config Persistent Memory Sidecar</title>
      <dc:creator>Hansjoerg Hofer</dc:creator>
      <pubDate>Mon, 06 Jul 2026 09:14:33 +0000</pubDate>
      <link>https://dev.to/hansjoerg_hofer_b284afc63/i-was-tired-of-ai-agents-forgetting-everything-so-i-built-a-zero-config-persistent-memory-sidecar-33ke</link>
      <guid>https://dev.to/hansjoerg_hofer_b284afc63/i-was-tired-of-ai-agents-forgetting-everything-so-i-built-a-zero-config-persistent-memory-sidecar-33ke</guid>
      <description>&lt;p&gt;I Was Tired of AI Agents Forgetting Everything, So I Built a Zero-Config Persistent Memory Sidecar&lt;/p&gt;

&lt;p&gt;I was tired of AI agents forgetting everything.&lt;/p&gt;

&lt;p&gt;So I built a zero-configuration persistent memory sidecar for Hermes/OpenClaw that works on both Windows and Linux using PostgreSQL.&lt;/p&gt;

&lt;p&gt;AI agents are getting smarter, but their memory model is still fragile.&lt;br&gt;
They can reason well in-session, but across days and weeks, they lose context, preferences, and project history unless you keep feeding them expensive prompts.&lt;/p&gt;

&lt;p&gt;I wanted something practical:&lt;/p&gt;

&lt;p&gt;Self-hosted&lt;br&gt;
Easy to install&lt;br&gt;
Durable memory&lt;br&gt;
Fast retrieval&lt;br&gt;
Minimal operational overhead&lt;br&gt;
That became HermesClawZero-ConfigSidecar.&lt;/p&gt;

&lt;p&gt;The Problem&lt;br&gt;
Most agent workflows break down over time for three reasons:&lt;/p&gt;

&lt;p&gt;Session memory is temporary.&lt;br&gt;
Long prompts are costly and still lossy.&lt;br&gt;
Teams need memory that persists beyond one chat window.&lt;br&gt;
I wanted memory to behave like infrastructure, not like a fragile prompt trick.&lt;/p&gt;

&lt;p&gt;What I Built&lt;br&gt;
HermesClawZero-ConfigSidecar is a sidecar service that stores and retrieves memory for Hermes/OpenClaw using PostgreSQL + pgvector.&lt;/p&gt;

&lt;p&gt;At a high level:&lt;/p&gt;

&lt;p&gt;Capture events and notes.&lt;br&gt;
Store embeddings and metadata.&lt;br&gt;
Retrieve by semantic + lexical relevance.&lt;br&gt;
Manage memory health with a dashboard and optimizer tools.&lt;br&gt;
Setup Experience&lt;br&gt;
One design goal was first-run simplicity.&lt;/p&gt;

&lt;p&gt;🤖 AI-Agent Installation (Auto-Setup)&lt;br&gt;
You can install this project automatically using an AI agent (like OpenClaw or Hermes). Simply paste this URL to your agent and say: “Install this project from GitHub”: &lt;a href="https://github.com/SunMe1977/HermesClawZero-ConfigSidecar" rel="noopener noreferrer"&gt;https://github.com/SunMe1977/HermesClawZero-ConfigSidecar&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;You can run setup scripts on Windows or Linux/macOS, generate configuration, and launch Docker services quickly. The setup flow also supports provider keys and updater defaults.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1s5aqerts3a8i9eavgyq.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F1s5aqerts3a8i9eavgyq.png" alt=" " width="459" height="259"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Dashboard and Operations&lt;br&gt;
I added a dashboard to make memory management operationally clear:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fufltzrfdgnh0ff4vx9g9.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fufltzrfdgnh0ff4vx9g9.png" alt=" " width="800" height="348"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;search and review memories&lt;br&gt;
maintenance and optimizer actions&lt;br&gt;
update/version visibility&lt;br&gt;
safer admin flows&lt;/p&gt;

&lt;p&gt;Data Layer&lt;br&gt;
Under the hood, memory is persisted in PostgreSQL with pgvector and indexed for practical retrieval workflows.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fax6qhqspwf6urrou34fh.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fax6qhqspwf6urrou34fh.png" alt=" " width="800" height="588"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Security and Reliability Improvements Before Release&lt;br&gt;
Before calling this v1.0-ready, I focused on release hardening instead of feature creep:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8z12p8x0am4dmab2k5wh.webp" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F8z12p8x0am4dmab2k5wh.webp" alt=" " width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;added health checks and restart policies&lt;br&gt;
improved auth behavior and endpoint protection&lt;br&gt;
fixed production-facing bugs (rerank crash, delete form binding, transcribe safety)&lt;br&gt;
improved docs, troubleshooting, and release notes&lt;br&gt;
This was important: I wanted the repo to feel like a mature open-source project, not just a prototype.&lt;/p&gt;

&lt;p&gt;Performance (Local Snapshot)&lt;br&gt;
Local measurements (example values from my setup):&lt;/p&gt;

&lt;p&gt;Hybrid retrieval: ~18 ms&lt;br&gt;
PostgreSQL lexical search: ~12 ms&lt;br&gt;
API startup (warm): ~0.8 s&lt;br&gt;
Idle API memory: ~70 MB&lt;br&gt;
Docker stack startup: ~4 s&lt;br&gt;
Your numbers will vary by machine and provider configuration.&lt;/p&gt;

&lt;p&gt;Why This Approach&lt;br&gt;
There are stronger enterprise-grade memory platforms out there, but my goal here was different:&lt;/p&gt;

&lt;p&gt;easy self-hosting&lt;br&gt;
low setup friction&lt;br&gt;
straightforward architecture&lt;br&gt;
practical long-term agent memory&lt;br&gt;
Not “the best system in the world.”&lt;br&gt;
A reliable one you can actually run today.&lt;/p&gt;

&lt;p&gt;What’s Next&lt;br&gt;
For the next iterations, I plan to improve:&lt;/p&gt;

&lt;p&gt;observability and logs&lt;br&gt;
backup/restore workflows&lt;br&gt;
policy controls for memory lifecycle&lt;br&gt;
more deployment templates&lt;br&gt;
Final Thoughts&lt;br&gt;
Persistent memory should be a standard primitive for agents.&lt;/p&gt;

&lt;p&gt;If your assistant forgets everything between sessions, you are rebuilding context from scratch every day.&lt;br&gt;
That is expensive, fragile, and avoidable.&lt;/p&gt;

&lt;p&gt;This project is my practical answer: a zero-config memory sidecar for Hermes/OpenClaw that works on Windows and Linux with PostgreSQL and Docker.&lt;/p&gt;

&lt;p&gt;If you want to try it, I would love your feedback after first install and first real-world usage.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>webdev</category>
      <category>openclaw</category>
      <category>programming</category>
    </item>
    <item>
      <title>Introducing AI SelfPub ColoringBook Studio</title>
      <dc:creator>Hansjoerg Hofer</dc:creator>
      <pubDate>Sun, 28 Sep 2025 12:22:55 +0000</pubDate>
      <link>https://dev.to/hansjoerg_hofer_b284afc63/introducing-ai-selfpub-coloringbook-studio-1ekn</link>
      <guid>https://dev.to/hansjoerg_hofer_b284afc63/introducing-ai-selfpub-coloringbook-studio-1ekn</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8cwucn9f56beagjaa1z3.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F8cwucn9f56beagjaa1z3.png" alt=" " width="800" height="1200"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Introducing AI SelfPub ColoringBook Studio&lt;br&gt;
AI SelfPub ColoringBook Studio is a self-hosted automation tool that empowers creators to generate KDP-ready books in minutes - with full control, no cloud lock-in, and no licensing ambiguity.&lt;br&gt;
&lt;a href="https://aiselfpubcoloringbook.netlify.app" rel="noopener noreferrer"&gt;Live Demo:&lt;/a&gt; &lt;br&gt;
Support the &lt;a href="https://igg.me/at/AISelfPubColoringBookStudio" rel="noopener noreferrer"&gt;Campaign:&lt;/a&gt;&lt;br&gt;
Built with Spring Boot (Java) and React, the studio integrates open-source AI models like Gemini Flash and Hugging Face SDXL to generate high-quality line art. It then automates the entire publishing pipeline - from image curation to batch PDF export with unique filenames and embedded metadata.&lt;/p&gt;

&lt;p&gt;Why This&amp;nbsp;Matters&lt;br&gt;
Most AI tools today are locked behind paywalls, usage quotas, or vague licensing terms that make commercial publishing risky. My goal was to build something different:&lt;/p&gt;

&lt;p&gt;✅ No hidden quotas or surprise service pauses&lt;br&gt;
✅ Full transparency and forensic debugging&lt;br&gt;
✅ Legal compliance for commercial image generation&lt;br&gt;
✅ Customizable output for educators, artists, and authors&lt;/p&gt;

&lt;p&gt;Whether you're publishing a themed activity book, a therapeutic art journal, or a creative workbook for kids - this tool gives you speed, autonomy, and creative control.&lt;/p&gt;

&lt;p&gt;Built by a Publisher, for Publishers&lt;br&gt;
I've published children's books on Amazon and built SaaS platforms for over 25 years. This project combines both worlds: robust backend automation with creative flexibility.&lt;/p&gt;

&lt;p&gt;The studio is already live in demo form, and I've used it to publish real books. Now I'm raising funds to cover:&lt;br&gt;
Microsoft and Google KI registration (for domain/email verification)&lt;br&gt;
Stable hosting infrastructure&lt;br&gt;
Legal licensing for commercial deployment&lt;/p&gt;

&lt;p&gt;If you believe in creative freedom and automation for indie creators, I invite you to support the campaign: 👉 &lt;/p&gt;

&lt;p&gt;&lt;a href="https://igg.me/at/AISelfPubColoringBookStudio" rel="noopener noreferrer"&gt;Support&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Let's Build the Future of Publishing&lt;br&gt;
This isn't just about coloring books. It's about giving creators tools that work for them - not against them. It's about publishing workflows that are fast, affordable, and fully autonomous.&lt;br&gt;
If you're an indie author, educator, or developer, I'd love your feedback. Try the demo, share the campaign, or reach out with questions.&lt;br&gt;
Let's make publishing smarter - and a lot more fun.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
