Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: LocalGPT – A local-first AI assistant in Rust with persistent memory

github.com

Post reply on HN
Print view View original

31–40 of 165 posts

Re: Show HN: LocalGPT – A local-first AI assistant in Rust with persistent memory

#31

Post by halfcat »

jack_pp wrote: post #26
DonaldPShimoda wrote: post #25

Earlier quoted context omitted.

> if they are correct I see no issue at all. Indeed. Are you verifying that they are correct, or are you glancing at the output and seeing something that seems plausible enough and then not really scrutinizing? Because the latter is how LLMs often propagate errors: through humans choosing to trust the fancy predictive text engine, abdicating their own responsibility in the process. As a consumer of an API, I would mu…

Can you provide examples in the wild of LLMs creating bad descriptions of code? Has it ever happened to you? Somehow I doubt at this point in time they can even fail at something so simple. Like at some point, for some stuff we have to trust LLMs to be correct 99% of the time. I believe summaries, translate, code docs are in that category

> Can you provide examples in the wild of LLMs creating bad descriptions of code? Has it ever happened to you?

Yes. Docs it produces are generally very generic, like it could be the docs for anything, with project-specifics sprinkled in, and pieces that are definitely incorrect about how the code works.

> for some stuff we have to trust LLMs to be correct 99% of the time

No. We don’t.

Re: Show HN: LocalGPT – A local-first AI assistant in Rust with persistent memory

#32

Post by SeanAnderson »

IhateAI_6 wrote: post #29
ramon156 wrote: post #2

Pro tip (sorry if these comments are overdone), write your posts and docs yourself (or at least edit them). Your docs and this post is all written by an LLM, which doesn't reflect much effort.

People have already fried that part of their brain, the idea of writing more than a couple sentences is out of the question to many now. These plagiarism laundering machines are giving people a brain disease that we haven't even named yet.

Oh cmon, at least try to signal like you're interested in a good-faith debate by posting with your main account. Intentionally ignoring the rules of HN only ensures nobody will get closer to your belief system.

Re: Show HN: LocalGPT – A local-first AI assistant in Rust with persistent memory

#35

Post by dvt »

embedding-shape wrote: post #17
dvt wrote: post #15

Earlier quoted context omitted.

Ah true, missed that! Still a bit cumbersome & lazy imo, I'm a fan of just shipping with that capability out-of-the-box (Huggingface's Candle is fantastic for downloading/syncing/running models locally).

Ah come on, lazy? As long as it works with the runtime you wanna use, instead of hardcoding their own solution, should work fine. If you want to use Candle and have to implement new architectures with it to be able to use it, you still can, just expose it over HTTP.

I think one of the major problems with the current incarnation of AI solutions is that they're extremely brittle and hacked-together. It's a fun exciting time, especially for us technical people, but normies just want stuff to "work."

Even copy-pasting an API key is probably too much of a hurdle for regular folks, let alone running a local ollama server in a Docker container.

Re: Show HN: LocalGPT – A local-first AI assistant in Rust with persistent memory

#36

Post by dbacar »

theParadox42 wrote: post #3

I am excited to see more competitors in this space. Openclaw feels like a hot mess with poor abstractions. I got bit by a race condition for the past 36 hours that skipped all of my cron jobs, as did many others before getting fixed. The CLI is also painfully slow for no reason other than it was vibe coded in typescript. And the errors messages are poor and hidden and the TUIs are broken… and the CLI has bad path con…

Given the fact that it is only a couple of months old, one can assume things would break over here and there for some time before investing heavily.

Re: Show HN: LocalGPT – A local-first AI assistant in Rust with persistent memory

#38

Post by fy20 »

dvt wrote: post #4

So weird/cool/interesting/cyberpunk that we have stuff like this in the year of our Lord 2026: ├── MEMORY.md # Long-term knowledge (auto-loaded each session) ├── HEARTBEAT.md # Autonomous task queue ├── SOUL.md # Personality and behavioral guidance Say what you will, but AI really does feel like living in the future. As far as the project is concerned, pretty neat, but I'm not really sure about calling it "local-firs…

> Say what you will, but AI really does feel like living in the future.

Love or hate it, the amount of money being put into AI really is our generation's equivalent of the Apollo program. Over the next few years there are over 100 gigawatt scale data centres planned to come online.

At least it's a better use than money going into the military industry.

Re: Show HN: LocalGPT – A local-first AI assistant in Rust with persistent memory

#40

Post by aforwardslash »

jack_pp wrote: post #26
DonaldPShimoda wrote: post #25

Earlier quoted context omitted.

> if they are correct I see no issue at all. Indeed. Are you verifying that they are correct, or are you glancing at the output and seeing something that seems plausible enough and then not really scrutinizing? Because the latter is how LLMs often propagate errors: through humans choosing to trust the fancy predictive text engine, abdicating their own responsibility in the process. As a consumer of an API, I would mu…

Can you provide examples in the wild of LLMs creating bad descriptions of code? Has it ever happened to you? Somehow I doubt at this point in time they can even fail at something so simple. Like at some point, for some stuff we have to trust LLMs to be correct 99% of the time. I believe summaries, translate, code docs are in that category

This happens to me all the time. I always ask claude to re-check the generated docs and test each example/snippet, sometimes more than once; more often than not, there are issues.
Post reply on HN