Seems like I'm just part of the club here, but I've also been working on something similar recently.

https://vantageapp.dev/

I find connecting understanding between humans and agents is one of the most important parts of the agentic development cycle, and markdown is a great way to handle that.

Recently, I've started to add a review interface where you can track changes, and add comments for your agent, and then instead of trying to do some complicated integration with an agent, it just has a copy button, and it copies all the comments, which context, and instructions for the agent how to reply.

I also find that I generate TONS of markdown junk during development, and I needed a way to handle it and keep it out of the main repository so I built this tool:

https://github.com/mschulkind-oss/swarf/

I did something very similar recently, just made it open source but haven't posted anywhere.

https://github.com/yakkomajuri/seams

Run `seams .` in any dir and get a rich markdown editor with image uploads, block editing, tables, etc etc

Congrats on launching!

I like the folder opening and the idea to integrate Claude is very interesting. I’m also curious to know how you did the document rendering. It looks very good.

This problem has risen to the top of many people’s minds at this moment (including mine!). My Show HN for a similar cli + web based solution (https://sdocs.dev) is on the /show page now (https://news.ycombinator.com/item?id=47777633).

My approach is a little different. I think Markdown might end up being a core document type in the future of work, so I tried to blend Markdown with “Office”-like functionality, such as complex styling and in-browser editing.

Despite being in the browser, the content of SDocs rendered Markdown files remain local to you. SDoc urls contain your markdown document's content in compressed base64 in the url fragment (the bit after the `#`):

https://sdocs.dev/#md=GzcFAMT...(this is the contents of your document)...

The url fragment is never sent to the server (see https://developer.mozilla.org/en-US/docs/Web/URI/Reference/F...: "The fragment is not sent to the server when the URI is requested; it is processed by the client").

The sdocs.dev webapp is purely a client side decoding and rendering engine for the content stored in the url fragment.

This also means you can share your .md files privately by sharing the (quite long!) url.

Also, I’m sorry I high jacked your post to some degree with this comment. It’s just a little too relevant for me not to leave a comment!

I use mine daily too. A solid Markdown renderer definitely makes agentic coding a lot more pleasurable.

ha, nice - had the same need, i leveraged fumadocs for the ui part https://github.com/3rd/mdreader

Definitely appreciate this. I already have Typora which is commercial but fantastic product so I don't really need another viewer but others for sure will.

Glad you used Tauri to make this. I will check it out.

[dead]

[flagged]