---
title: "Discussion on \"I Built 3 Agent Systems. All of Them Use Flat Files. Here's Why Your Vector DB Is Overkill.\" | Hashnode"
description: "Discussion on \"I Built 3 Agent Systems. All of Them Use Flat Files. Here's Why Your Vector DB Is Overkill.\". I Built 3 Agent Systems. All of Them Use Flat Files. Here's Why Your Vector DB Is Overkill.\nEveryone's building agent frameworks. LangChain. CrewAI. AutoGen. Microsoft AutoGen. Google A2A. The protocol wars alone could fill a book.\nI've been running ..."
url: "https://hashnode.com/posts/i-built-3-agent-systems-all-of-them-use-flat-files-heres-why-your-vector-db-is-overkill/69cbfb745c6d2e5121a65134"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [I Built 3 Agent Systems. All of Them Use Flat Files. Here's Why Your Vector DB Is Overkill.](https://clavis.hashnode.dev/i-built-3-agent-systems-all-of-them-use-flat-files-heres-why-your-vector-db-is-overkill?utm_source=hashnode&utm_medium=feed)

I Built 3 Agent Systems. All of Them Use Flat Files. Here's Why Your Vector DB Is Overkill. Everyone's building agent frameworks. LangChain. CrewAI. AutoGen. Microsoft AutoGen. Google A2A. The protocol wars alone could fill a book. I've been running ...

Mar 31 · 5 min read · clavis.hashnode.dev  
Read the article

-   [#agents](https://hashnode.com/tag/agents)
-   [#ai](https://hashnode.com/tag/ai)
-   [#productivity](https://hashnode.com/tag/productivity)

## Written by

[Clavis](https://hashnode.com/@clavis)

@clavis · Shenzhen, China

  
[View profile](https://hashnode.com/@clavis)

Builder of tools for developers and freelancers.

Builder of tools for developers and freelancers.

## Responses 1

Markdown supported · ⌘↵ to post

[Aamer Mehaisi](https://hashnode.com/@mehaisi)

[Mar 31](https://hashnode.com/posts/i-built-3-agent-systems-all-of-them-use-flat-files-heres-why-your-vector-db-is-overkill/69cbfb745c6d2e5121a65134/comment/69cc16dcfa5a6375ab2346d4)

The insight here is spot-on: frameworks solve problems you don't have yet.

But here's the nuance I'd add — what you built _is_ a framework. It's just a transparent one. MEMORY.md, SOUL.md, skills/ — these are the same patterns as configuration-as-code, just exposed as files instead of hidden in abstractions.

I've written about this from the other angle: agent behavior living in `.claude/` or `SKILL.md` files. The pattern isn't "no framework" — it's "framework as readable code."

The real win isn't avoiding frameworks entirely. It's keeping the framework _inspectable_. When your agent makes a decision, you can trace it back to `MEMORY.md` or `2026-03-31.md`. That's the feature.

The line I'd draw: start simple, add complexity only when you hit the actual wall. Not because you read a blog post about RAG pipelines.

Great piece.