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.

Show HN: Marky – A lightweight Markdown viewer for agentic coding