The history of OBTF: from Danny O'Brien to AI

Updated: October 29, 2026

OBTF was not invented in a single day. The idea of keeping everything in one text file appeared independently to different people: in talks, blogs, discussions, and personal habits. The name came later. The practice is older than the name.

2004: Danny O'Brien's talk

One early reference point is Danny O'Brien's 2004 talk at the O'Reilly Emerging Technology Conference. It was called “Life Hacks: Tech Secrets of Overprolific Alpha Geeks.”

O'Brien surveyed productive programmers and found a shared habit: many kept notes, lists, and links in plain text rather than in complex apps. Cory Doctorow's notes from the talk are still online. It was not a finished method, but it was an important public moment for the idea.

2005–2006: blogs and early articles

In the mid-2000s the idea spread through blogs. In 2005, 43 Folders published “Life inside one big text file” about working with one file instead of a collection of notes and lists.

In 2006, William Hern wrote “Living in a Single Text File.” He kept a file for several years and grew it to tens of thousands of lines. For its time, it was a clear example that one file could handle daily work.

There were no convenient sync tools, mobile editors, or cloud drives as we know them. People used what they had: a text editor, a terminal, and backups.

The 2020s: Jeff Huang and a new wave

The modern wave of interest is often linked to Jeff Huang's article “My productivity app is a never-ending .txt file.” He described a file he had kept for years and grown to tens of thousands of lines.

The article made a simple point. Personal productivity does not require databases, tags, and dashboards. One file, dates, and search can be enough. After the discussion on Hacker News, new readers picked up the idea.

Communities and templates

Small communities formed around OBTF. On Reddit, r/OneBigTextFile is a place where people share structures, templates, and sync setups.

Templates appeared too. Christopher Sherrod published a minimalist OBTF template with documentation. MrDizzy wrote about a shell script for working with the file and compared the method to the Commonplace Book tradition. In 2025, Ellane W. published an introductory piece, “OBTF: start here.”

These projects do not form a single school. They share one thing: the file stays plain text, while the tools around it can change.

Obsidian and Markdown

As Obsidian became popular, the idea found a new environment. OBTF can live inside a Markdown vault with links, tags, and plugins, while the file itself remains text.

Hybrid setups appeared. One file works as an incoming journal, while individual topics grow in Obsidian notes. This works until the file turns into a pile of markup. If the text is readable only inside one app, the advantage of a simple format is gone.

The AI era

Interest in text archives grew again after 2022. Large language models learned to read and summarize long texts. A single file became a convenient source of context: it can be pasted into a prompt, split into chunks, or indexed for RAG.

Local models and tools such as Ollama appeared. A personal archive can now be processed without sending it to the cloud. This brought back the themes of privacy and data ownership that plain text had from the start.

The AI era has its risks. A model can invent a fact, confuse a date, or lose context. The file remains the source, and the model only helps read it. For more on this, see the guides on notebooks, OBTF, and LLMs and RAG over a personal text file.

A short timeline

What stayed the same

Editors, clouds, and models changed over twenty years. A few properties stayed the same: the file belongs to the user, opens without special software, and requires no subscription.

OBTF did not become a product. It has no company, pricing tiers, or mandatory ecosystem. It is closer to a habit and a set of conventions that each person adapts.

Bottom line

The history of OBTF shows that people return to plain text not out of nostalgia. They return to a format that outlives apps and remains useful for search, backups, and new tools.

To start at the origins, read the notes from the 2004 talk and Jeff Huang's article. For a modern practical start, go to the main OBTF guide.