Generally curious, how is this different from pointing Claude Cowork at an Obsidian Vault?

Biggest difference is Atomic leverages an LLM to auto-tag and a text embedding pipeline to drive semantic search - so the knowledge base is self-organizing. The bet here is that having an agent grep the filesystem is fine for a carefully curated, relatively small set of markdown files. It starts to degrade if you approach your knowledge base as a place to put everything: personal notes, articles you find interesting, entire textbooks if you want to. Having a vector database in this context is pretty much required past a certain scale; a filesystem-based approach is just an incredibly inefficient way to do retrieval in this context, and your agent is bound to miss important data points.

Does the LLM auto-tagging and embedding pipeline run on the device, or are they remote calls?

So an Obsidian plugin? Got it.

One can imagine an obsidian plugin of any arbitrary level of complexity, given it's written in a Turing-complete language.

I would love to be able to do the clustering from a CSV instead of a collection of Markdown files. I know I can easily generate the files, but I used to do this directly for very short text inputs (just titles or words) on nomic.ai (before they pivoted to 'Enterprise')

Killer feature: add audio transcription. Record that meeting; just tell the app what you want to remember. It gets transcribed and then processed like any other note.

Reviewed: https://zby.github.io/commonplace/agent-memory-systems/revie...

It is the second llm wiki on frontpage today!

I wish the scene was more collaborative - instead of everyone writing their own. But I guess this is the llm curse - too easy to start. I am afraid it will all go in the LangChain direction with VC funding designs that are not yet ready solidifying choices that would normally be superseded.

What's the other one? I cannot find it.

Probably this one (Tolaria) https://news.ycombinator.com/item?id=47882697

Lots of good ideas and divergent methods and sources here cheers for the link

This is .. honestly a great synopsis of Atomic and its design tradeoffs. Thanks! Giving commonplace a look.

Thanks!

The reviews are done automatically - here are the instructions: https://github.com/zby/commonplace/blob/main/kb/agent-memory...

I am open to changing these instructions - it cannot be about just making your system look better - but I'll try to incorporate genuine ideas how to improve these reviews.

I've been tinkering with my own version of this idea off and on for months, and it's great to see someone finally make the thing that I've been wanting since LLMs hit the scene. Congrats on everything you've shipped!

They keep adding this “cloud of dots” where each dot represents a concept or something you wrote, and they are linked to other dots… sure it’s pretty the first time you see it, but it’s not useful at all beyond that

but there are a lot of them

"Runs everywhere"

...except my Android phone LOL

working on it https://github.com/kenforthewin/atomic/tree/main/mobile/andr...

I feel like most of these applications all boil down to "Obsidian but with AI integration baked in up front". It'd be interesting to see approaches that actually rethink commonplaces of the experience (graph view etc) rather than just reproduce the same thing but "with ai"

> Not x — but y.

Am I the only one who feels a bit betrayed after reading LLM text? I am not even willing to try out the app after I notice… which is a shame.

At least polishing the obvious parts would help a lot and is not that much work.

As someone that makes regular use of the em-dash, comments like this are rather maddening.

I still refuse to self-censor to avoid having my actual writing get flagged by someone as LLM written.

I don't mind the em-dash, but that whole front page is very much "We prompted ourselves a web site"

Thanks for the feedback. Yeah, I admit copywriting is not my forte. i'm a solo dev, I'm focusing most of the time and energy on the product itself. There are always 100 things I could be polishing for Atomic - social media presence, website, docs, etc. even with AI there just aren't enough hours in the day - you have to triage somehow.

This was good feedback - Website has been updated!

Maybe I'm just spoiled with a large working memory, but I don't want an AI agent thinking or remembering of synthesizing for me. Seems like a great way to never have a new idea.

I sure love when the local-first software defaults to a non-local option for its main feature.

Somehow, in the AI world, "local-first" means a local harness talking to a remote model, almost never "local harness talking to local model". But then "open source model" apparently also means "you can download the weights if you agree to our license" and almost never "you can see, understand and iterate on what we did", so the definitions already drifted a lot between the two ecosystems.

Atomic supports any generic openAI compatible LLM provider, including ollama, LM studio, etc.

But local-first !== defaults to local inference, right?

I'm not sure I understand the question. Regardless of what provider you choose - be it cloud based or local - you have to provide setup information such as host, authentication, etc. So it "defaults" to nothing; you have to select something.

Maybe this will be a clearer question: What does "local-first" mean in the title that you typed in for this HN submission?

Local first means running Atomic with local models is not an afterthought. It’s a first class citizen that works just as seamlessly as running with a cloud provider - assuming you’ve done the work to provision the local models and their connections yourself.

I'm not sure what the dunk is supposed to be here .. Atomic supports the exact same feature set with local models as it does for OpenRouter. Is your gripe just that Openrouter is the first option in the dropdown?

Yes. Why even call it local-first when local isn't first? Not to mention, for some reason they decided to only support Ollama instead of giving you the option to connect to any OpenAI-compatible server, which would make this work with any other inference server such as llama.cpp and vLLM as well as Ollama. (and also most SaaS inference providers, including OpenRouter, so the custom integration would not be necessary either, https://schizo.cooking/schizo-takes/9.html)

Did you think local-first meant how a dropdown is sorted?

OpenAI-compatible is indeed one of the provider options for Atomic. Ollama and openRouter are separate options to allow for easier selection of models from these specific providers.

The online documentation does not suggest that using a generic OpenAI-compatible server is an option, and it once again lists the non-local option first.

https://atomicapp.ai/getting-started/ai-providers/

> OpenAI-compatible is indeed one of the provider options for Atomic. Ollama and openRouter are separate options to allow for easier selection of models from these specific providers.

Why is this necessary over just presenting the result of `/v1/models`?

You can say it's just the ordering of a dropdown, but to me it seems pretty clear that this thing is developed with the idea that you'll most likely use a SaaS provider.

It has supported local LLMs from the beginning, it was not something that was just tacked on. I don't know what else to tell you. Your assumptions are just wrong.

Yes, hah.

"Local-first, your data never leaves the computer! Except once to go to the biggest information hoarders on the Internet."

Atomic supports any generic openAI compatible LLM provider, including ollama, LM studio, etc.

Awesome! How did you find using Tauri? Were there any particular pain points?

Tauri is great! this is my first Rust-based project and it took some real getting used to. But i love that Tauri does not ship with an entire chromium browser, and i love its focus on security.

The app Atomic.app com.atomic.app (signer: Developer ID Application: Foldingspace Labs LLC (D3SX98L77N)) will not run without access to fonts.googleapis.com:53, fonts.gstatic.com:53, api.fontshare.com:53.

nice username :)

fair point, the app makes requests to load fonts. we'll fix that next release.