Embed Notice

@kerravonsen@mastodon.au @maxleibman@beige.party I suppose I should add, this is only useful to me because I journal a whole lot, and it's in this specific format which lends itself to this use-case.

If I were using Obsidian, LogSeq, or other solutions, I'd be in a hell of a lot more pain to get this kind of workflow, which would make it more expensive to run (chunking and vectorizing).

For work applications, I use the same general workflow. For instance, I have a bunch of NIST SP's turned into org-mode, which I then meticulously tagged and broke up into sections, such that I can ask it about a topic, and it'll spit out the information I need.

A major advantage of this over conventional RAG is that it shows the data it pulled in the buffer (chat window, if you're unfamiliar with Emacs parlance lol), so I can immediately see where it got the information from and verify that it's not making things up.

Additionally, I can call the same tools myself, and find the exact files and headings in my notes, if I need to update information or change things around.

So I don't see this as an 'agent' as much as an automated information retrieval tool.

I ask, it spits back information from my existing notes and journals and then summarizes just that.

And if it's inaccurate? I have a damn good chance to notice, since *I wrote the material it's using.* (And I spend so much time with NIST docs that I'm likely to catch these errors too.)

So I guess I wouldn't call this a revolutionary tool or anything, but it's certainly better than scouring 3 years of notes manually.