Original Reddit post

I’ve been working on an open-source document format and viewer idea I’m calling Adaptive Markdown. The basic idea is that a document should not have to stay static. It should be something a coding agent can extend, reshape, and turn into an interactive workspace. This is not just a canvas you edit with a chatbot. The bigger idea is: the document becomes a programmable interface. A living app. So the document is the starting point. You do not need to be a programmer. You write the document, keep the notes, and then tell a coding agent what you want it to do to it. This can range from simple edits to adding widgets, tables whatever. File can contain the text, data, styling, interactivity, history, and agent instructions in one self-contained .md file. The agent can then edit the doc: add charts, restyle sections, create calculators, build filters, generate summaries, export different views, or turn static notes into an interactive tool. So instead of having a document, a spreadsheet, a dashboard, an app, a changelog, and a separate AI chat about all of it, you can have one living document that contains those layers together. A simple example is a fitness log. At first it is just a text journal. Then the agent adds charts. Then it pulls in device data. Then it adds weekly summaries, rolling averages, goal tracking, export options, and a dashboard view. The document did not move into an app. The document became the app. That same pattern applies everywhere: A billable time log can compute subtotals live and rewrite rough notes into polished narratives. A research notebook can keep experiment parameters, runnable code, outputs, and methodology notes together. A recipe book can scale servings, adjust units, and generate shopping lists. A math textbook can rewrite a theorem for a beginner, a graduate student, or a specialist. A lab protocol can include persistent checklists and validation steps. An architecture doc can contain live Mermaid diagrams and executable API examples. A legal matter note can maintain timelines, fact matrices, and issue summaries. A small data report can include CSV data, live charts, filters, and exportable views. A music workbook can include playable notation and transposition tools. A project README can explain the system, demonstrate the system, and let the agent modify the system from inside the document. The core shift is that the document is no longer a passive artifact. It is a surface the agent can operate on. Traditional Markdown is great for writing static text. Apps are great for interaction. Dashboards are great for visualization. Spreadsheets are great for tabular manipulation. But a lot of real work sits awkwardly between those categories. Adaptive markdown is trying to make that middle space first-class: readable like a document, portable like a file, interactive like an app, and editable by an agent in real time. The thing I’m most interested in is not “Can Markdown support more widgets?” It is: What happens when the document itself becomes the programmable, agent-editable interface? I made some short video demos: https://youtu.be/l-I2UiZd-Jw

Originally posted by u/IDefendWaffles on r/ClaudeCode