we’re open-sourcing our internal markdown editing + collaboration tool. built with @demegire1 and @emresarbak our team is spending more time planning on markdown files than coding. you probably are too. why is it so hard to collaborate on markdown files? i don't know. we just couldn't find anything that made it easy to share and work on the same file. sooo we created a new markdown file to plan a markdown editing + collaboration tool and vibe-coded with.md with.md lets you: - drag-and-drop your internal .md docs (no sign-in required) or sign in with github and access all the md files in your repo to organize, edit, and share repo-scoped markdown - share them with teammates to edit together (or get sign-off) - then, feed them back into your claude code / opencode / etc. - we also made shares easily parseable by agents. we’re planning to add more workflows like real-time editing + attribution for claude code agents, arxiv/docling integration, turning urls into markdown, etc. but that’s down the line. we weren’t avid markdown users, we mostly used google docs for company-wide stuff. but as we started using more and more terminal agents to edit, improve, and then straight-up copy-paste, we ended up sharing more and more markdown. and for whatever goddam reason, rendering markdown in cursor/vscode is a pretty clunky experience. then, if you share a markdown on slack, the other person has to download it, open it in their own vscode/cursor/sublime, and get the same shitty md viewing experience. we didn’t like that, so we built something that works for us. realtime cursors, anchored comments, diff view (thanks @pierrecomputer) -> the stuff you’d expect, but somehow doesn’t exist in one place for .md files. make no mistake: our understanding of wysiwyg editors and how crdts work is still pretty limited. but after reading the crdt docs on @ekzhang1’s reading group site, @geoffreylitt and the ink & switch crew’s peritext post, and talking through a primitive v1 design, the rest was straightforward: write a thorough plan in md, turn key resources and docs into md, feed it into codex 5.3, and get a working demo. after that, we polished the rough edges, iterated on the md rendering design system, fixed bugs, and tried to make the whole thing reasonably secure with a few extra human/agent passes. you’d think doc editors are “gg ez” they’re not. still, it was encouraging that the tool we built for ourselves (humans) was necessary to get to something that feels worth sharing on twitter. there are still a lot of bugs, we’ll try to squash them as we keep updating the tool. this is not a replacement for your @obsdmd , gdocs, or @NotionHQ . for our specific use case, we couldn’t bootstrap something more practical with existing tools. but yeah, if you have other ideas & tools, please share. again: this is 100% vibe-coded, but it works. we’re open-sourcing it to make it better. the github issues section is waiting for your snarky feedback.
