I used to run my whole setup on markdown files and honestly it held up longer than I expected. One handoff file, one decisions file, a rules file that both my coding tools were supposed to read at the start. For a while that was enough.
Where it started to crack for me was not one big failure. It was smaller stuff piling up. I would open a fresh session and the agent would just... not read the handoff file, or read the old version of a decision and state it back to me with total confidence even though we had reversed it two days earlier. And once the folder got to a few hundred notes I could not find the right one fast either, so I get why the agent struggled.
I ended up building something to fix that for myself (not selling anything here, just trying to figure out if I hit the ceiling of the file setup or if I just had sloppy file discipline).
So for people whose agent setup is basically files: what was the first thing the files could not do for you? Was it finding the right note once there were too many, two tools writing at the same time and clobbering each other, a stale note sounding more confident than the actual code, something else? Did you fix it by getting stricter with the files, or did you move to something more structured?
Also curious what you are building with this setup. Own product, client work, day job stuff, just for fun?
One more thing I keep wondering about. Have you ever looked at a memory tool that keeps context across tools, or did that thought never really cross your mind? For me the worry was always that moving everything I already had in files into something new would feel like starting over.
What if something handled all of this for you, in the cloud over MCP, so every agent and tool got the same context: decisions, failed attempts, conversations, skills, procedures, tasks. You never touch a file again. Would you guys pay for something that fixes this? Have you ever thought about paying for a tool to manage all of this for you, or has the thought never crossed your mind?