note.md

Congrats. What has surprised you most from early feedback today?

Oh my gosh, I've struggled with citation managers for so long! And this is built right into Notes. It's native to the Mac, too, so it runs smoothly. Thank you!

Love the local-first approach — keeping your notes as LLM memory is a genuinely clever solve for the 'AI doesn't know my work' problem. Does note.md support linking between docs to build a knowledge graph over time?

Congrats on the launch! Keeping the vault as an open, flat directory of plain Markdown files is a huge win for portability. I'm curious about the background file-watching mechanics. If a user modifies their .md files or directory structure externally via terminal or another editor like Obsidian, note.md seamlessly detects and re-indexes those changes on the fly, or is a manual re-sync required to keep the reference manager and source connections aligned?

Research is ultimately about building knowledge, not just taking notes. How did that idea shape the design of note.md?

the support-vs-contradiction scan is the sharp bit — embeddings sit 'x causes y' next to 'x doesn't', so retrieval finds candidates but stance needs an nli pass on top. on-device per claim is the real cost.

Huge congrats on the update! Keeping the vault as plain Markdown files while opening it up to AI is a game-changer. Since it reads the folder structure directly, do you have any tips for how to organize notes to make it easiest for an agent like Claude to navigate?

There's a really interesting trust/transparency UX challenge here: when an LLM "remembers" from your notes, users need to understand the boundary between "this is my document" and "this is what the AI learned from it." The line gets blurry fast. Most knowledge tools either treat memory as a black box or overwhelm you with provenance metadata. How are you surfacing what's been indexed — especially for notes users might consider private?

Love the simple, no distractions approach with seemingly so many features that you progressively discover throughout exploring the app - feels very well thought out! Also a heads up: tried using the `PRODUCTHUNT` code and kept running into this error. Any ideas as to why this could be?Excited to give the full suite a try even if its only a limited free trial ((:

@andreaigner Congrats on the update! 🚀 Keeping the vault as plain Markdown while opening it up to AI is literally a game changer here. I'd definitely try to hook this up to a local LLM.Just for quick idea: what about .aignore file to easily hide sensitive drafts or keys from the AI's view?

The interesting tension here is that "local LLM memory" means very different things depending on how retrieval actually works. Are you chunking and embedding the markdown files so the model can do semantic search across them, or is it more like context stuffing where relevant notes get injected into the prompt window at query time? That distinction matters a lot for how well it handles a large, messy note library versus a small tidy one. Also curious whether note.md watches files for changes and updates the index automatically, or whether syncing is a manual step.

Interesting one today! The "librarian not ghostwriter" line is the reason I'd try this, most of these tools fall over themselves to write for you instead:)

The "cited memory with receipts" part is what actually matters, raw chat-history memory loses provenance and you can't tell later what's real. Keeping it as plain markdown on disk so any filesystem-capable agent can read it, not just Claude, is the right call too. The whole thing only works if the vault's genuinely clean though, that's the hard part. Solid update 🙏

This is an interesting direction.

With NotebookLM becoming many people's default research assistant, where do you think note.md creates the biggest advantage? Is it ownership of data, writing workflows, or something else?

The local-first angle for note.md caught my eye, especially paired with markdown and research writing. How are you thinking about people moving existing .md files into the workspace — is it meant to work with an existing folder structure, or more as a dedicated place where notes and drafts live together?