The Chat Window is a Dead End · markdown-den<br>The Chat Window is a Dead End

By Diego Guridi

TL;DR: The chat window is good at one thing: a question you will never ask again. Everything worth keeping drifts toward files. The file tree is not a replacement for the conversation, it is what the conversation should be pointed at, and almost nobody has designed a surface around that idea yet.

The problem you have already felt

You open a new chat with your AI and describe the project: what you are building, the constraints, the decisions you have already made. The model catches up, you get something useful, and by the end of the session some of that thinking has become code.

That is where the reasoning disappears. The code captures what you built, not why you built it that way or what you decided against. Come back three days later and you explain it all again, slightly differently, and get a slightly different answer. A week in you have six conversations in your history and no idea which one holds the decision that matters. The code keeps accumulating, and the gap between what is built and why grows with every session.

Coding harnesses keep memory files, and conventions like AGENTS.md carry context between sessions automatically. That genuinely helps. But those files are written for the agent to read, not for you to work in. You rarely see them, you rarely edit them, and when the context in them is wrong there is no obvious place to go and fix it.

This is not a failure of the model. It is a failure of the surface. You have been doing serious, cumulative work in a tool designed for questions you ask once and forget.

Everything worth keeping ends up in files. The file tree is not a replacement for the conversation. It is what the conversation should be pointed at, and it is the thing that keeps the reasoning from vanishing into the code.

The file tree is the answer

The file tree is not a new idea. It is one of the oldest interfaces in computing, and it has outlasted every generation of tooling built on top of it. Databases, applications, frameworks, paradigms: all of them have come and gone, and the file tree is still there underneath, organising everything. There is a reason for that. Files and folders are a primitive: they presuppose almost nothing about what you are doing, which means they bend to any kind of work rather than constraining it to a shape someone else decided in advance.

The answer to losing your reasoning into a chat window is not a smarter chat window. It is the oldest solution in computing: write it down, put it somewhere, give it a name. The file tree is that somewhere, and it turns out to be exactly the right shape for this problem.

You can see what you have built. In a chat window your context is invisible, somewhere above the input box. A file tree is a diagram of it: what exists, how it is grouped, what is missing. You cannot improve something you cannot see.

Text in a file is an artifact. Every good sentence you write in a chat window is gone the moment the session ends. A file survives the session, and it is better each time because you edit it rather than retype it.

A file has an address. You can point at it, hand it to someone else, tell an agent to go and read exactly that. A paragraph twenty turns up a conversation has no address at all.

You improve context by editing it, not re-explaining it. In a chat, every correction piles more text on top of the old text. In a file, you change the sentence and the wrong version is gone. Over weeks, that difference adds up.

Markdown is the right format for this

Markdown is what these files should be written in, and there are a few good reasons for that.

Plain text is what the model actually reads. Nothing is converted or extracted on the way in, so what you see is what the agent sees. Headings, lists and links mean the same thing to a person and to a model, in the same characters.

There are no fonts to pick and no layout to fiddle with. The only thing left to work on is what the words say.

And a decent renderer turns the same file into something genuinely pleasant to read, with proper headings, tables and diagrams, so you are not staring at markup unless you want to.

Underneath it is still just a text file, which means it outlives whatever tool you opened it in.

What a plain file system cannot do

The trouble is that a file system gives you files and folders and nothing else.

It does not know when something changed. It does not tell you that a collaborator, human or agent, just edited the file you are looking at. There is no way to leave a comment anchored to a specific sentence, no way to say "this paragraph needs rethinking" without either editing the file itself or sending a message somewhere else entirely. There is no presence: you cannot see who is in the document with you, or whether anyone is.

And an agent is not a first-class participant. It is a process that reads files and writes files, but it has no name in the...