Since when is JavaScript native? Tauri may be using the system's web view but it's still a web view. False advertising.

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.

Been also building this slowly, mostly assisting my kids.

What they built is Apple-only, since it's a native iOS/macOS app in Swift. It's been a very interesting experience for me, as even capable frontier LLMs still can't write Apple SwiftUI/AppKit properly. They constantly get the bridges wrong, and any feature prompt puts your previous architectural efforts at risk :)

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

I guess my key issue is, with files getting continuously modified by coding agents, I want really good integration with git and live update features. If the file just got edited, make it easy to see the new parts etc.

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!

https://github.com/robinduckett/hyprmark