The Plain-Text AI Interface
Why Obsidian vaults, AGENTS.md, and markdown files are becoming the default runtime for AI agents
Your vault isn’t a notebook anymore. It’s a runtime.
We previously published “Your Vault Is Your Moat” — the case that your personal knowledge base is the one asset AI can’t commoditize. That piece was about ownership. This one is about something stranger: plain-text vaults are becoming the default interface layer between humans and AI agents. Not by design. By convergence.
Six independent signals, none of them coordinated, all pointing the same direction.
60,000 repos have an AGENTS.md file
The AGENTS.md standard is a plain-text file that tells coding agents how to work on your project. Build steps, test commands, code style, conventions — all in markdown, sitting in your repo root. Google, GitHub Copilot, Windsurf, and OpenAI Codex have adopted it. Claude Code has its own variant (CLAUDE.md). Over 60,000 open-source projects now include one.
Nobody designed this as a standard. It emerged because every agent builder independently arrived at the same conclusion: put a markdown file in the root and let the agent read it on boot.
38,000 stars on a repo of plain-text config files
awesome-cursorrules is a community-curated collection of .cursorrules files — plain-text instructions that tell Cursor’s AI how to behave in your project. 38K stars. 3,200 forks. Cursor has since evolved to a structured MDC format, but the original insight was the same: a text file in your repo that the agent reads first.
The ecosystem around “how to configure AI agents with plain text” is now larger than most programming frameworks.
JARVIS runs on DataviewJS now
A developer built a full monitoring dashboard inside Obsidian — 13 DataviewJS widgets tracking active Claude Code sessions, token usage, project status. It trended on r/ClaudeAI. The name is JARVIS, because of course it is.
The Iron Man cosplay is inevitable. The architecture is the story. No web app. No dashboard service. Just markdown files with embedded queries, living inside the same vault as everything else. Monitoring layer and knowledge layer collapsed into one.
An agent named Lloyd boots from a Mac Mini
Dave Swift wrote up how he set up OpenClaw + Obsidian for persistent agent memory. His agent, “Lloyd,” runs on a headless Mac Mini. On every session start, Lloyd reads AGENTS.md for behavioral instructions, SOUL.md for identity, and daily memory files for recent context. Between sessions, the vault is Lloyd’s brain.
The pattern: AGENTS.md → SOUL.md → MEMORY.md. Session bootstrapping via plain text. No database. No embeddings store. No vector DB. Files all the way down.
Dave didn’t invent this. He stumbled into it — same as a dozen other builders right now, all arriving at the same architecture from different starting points.
llms.txt is robots.txt for AI agents
The llms.txt proposal puts a plain-text markdown file in your site’s root directory that tells AI agents what your site is about, what content matters, and how to navigate it. It’s robots.txt logic applied to LLMs — and it’s already mainstream enough that Bluehost is publishing setup guides for it.
The pattern is identical to AGENTS.md, just pointed outward. AGENTS.md tells an agent how to work on your project. llms.txt tells an agent how to understand about your project. Both are plain text. Both sit in the root. Both emerged independently.
Smart Connections goes paid
Smart Connections Pro launched its paid tier this week. Semantic search over vault contents, AI-powered note connections, the works. The free version already had serious traction. A paid tier means the market is real enough to charge for.
The business signal matters more than the feature list. Someone looked at “AI + Obsidian vault” and decided it was worth charging for. That’s a market now, not a hobby.
The pattern no one planned
Here’s what’s actually happening: people are independently converging on plain text as the substrate for AI agents. Nobody published a spec. Plain text just has properties nothing else can match:
Readable by everything. LLMs parse markdown natively. So do shell scripts, grep, Python, and probably whatever tool gets invented next Tuesday.
Diffable. Git-track your agent’s memory. See exactly what changed between sessions. Good luck doing that with SQLite.
Portable. When the next AI framework drops (give it six weeks), your vault still works. Files outlive frameworks.
Composable. AGENTS.md handles behavior. SOUL.md handles identity. MEMORY.md handles continuity. Daily notes handle episodic memory. Each file is a module. Swap any piece without touching the others.
The AGENTS.md → SOUL.md → MEMORY.md bootstrap pattern is becoming a de facto standard through pure convergent evolution. When your agent’s context window starts with read these files, this is the obvious architecture.
Your vault is an agent runtime
Reframe it: your Obsidian vault is where an AI agent boots, orients, acts, and persists state. Folder structure is the file system. Links are the graph database. Frontmatter is the schema. Daily notes are the event log. AGENTS.md is the boot sequence.
More people figure this out independently every week. The plain-text AI interface was always there. We’re just now noticing what we built.