Somewhat related. I've also been generating lots of markdown files, which I've occasionally wanted to print out (so I can rest my eyes, or just read them somewhere other than my desk.) First class (free) printing support for rendered markdown seems like a lacuna in the overall ecosystem. I'm currently using the "print" plugin for VS Code, which opens rendered markdown in a browser window, which I print from there. Curious if anyone knows of better options?
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.
Not only can you point it at an entire directory, you can point it at multiple projects, quick load a project with a keyboard shortcut, and also easily see recent file that changed to help you find the 75th file your agent just wrote for you.
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:
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.
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 `#`):
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.
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.
Not only can you point it at an entire directory, you can point it at multiple projects, quick load a project with a keyboard shortcut, and also easily see recent file that changed to help you find the 75th file your agent just wrote for you.
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/
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.
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!
Glad you used Tauri to make this. I will check it out.