Live data from Hacker News

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

github.com

111–120 of 165 posts

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

#111
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…

Yes this is not local first, the name is bad.

Horrible. Just because you have code that runs not in a browser doesn't mean you have something that's local. This goes double when the code requires API calls. Your net goes down and this stuff does nothing.

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

#112
post #18
post #5

Earlier quoted context omitted.

> which doesn't reflect much effort. I wish this was an effective deterrent against posting low effort slop, but it isn't. Vibe coders are actively proud of the fact that they don't put any effort into the things they claim to have created.

Github repo that is nothing but forks of others projects and some 4chan utilities. Professional codependent leveraging anonymity to target others. The internet is a mediocrity factory.

Mediocrity is in charge of the largest military atm

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

#113
post #77

Earlier quoted context omitted.

To be precise, it’s exactly as local first as OpenClaw (i.e. probably not unless you have an unusually powerful GPU).

Yes but OpenClaw (which is a terrible name for other reasons) doesn't have "local" in the name and so is not misleading.

As misleading. Lots of their marketing push or at least thr ClawBros pitch it as running local on your MacMini.

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

#115

This looks very interesting and i personally like that it reflects a lot of things that i actually plan to implement in a similar research project(not the same tho). Big props for the creators ! :) Nice to see some others not just relying on condensing a single context and strive for more

[flagged]

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

#116

Slop. Ask and ye shall receive. In a reply to another comment you claim it's because you couldn't be bothered writing documentation. It seems you couldn't be bothered writing the article on the project "blog" either[0]. My question then - Why bother at all? [0]: https://www.pangram.com/history/dd0def3c-bcf9-4836-bfde-a9e9...

The clout, people love the clout.

Guys, this is the AI slop we are all being told is the future of AI genetation.

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

#117
post #58

Earlier quoted context omitted.

The lethal trifecta is the most important problem to be solved in this space right now. I can only think of two ways to address it: 1. Gate all sensitive operations (i.e. all external data flows) through a manual confirmation system, such as an OTP code that the human operator needs to manually approve every time, and also review the content being sent out. Cons: decision fatigue over time, can only feasibly be used…

You could have a multi agent harness that constraints each agent role with only the needed capabilities. If the agent reads untrusted input, it can only run read only tools and communicate to to use. Or maybe have all the code running goin on a sandbox, and then if needed, user can make the important decision of effecting the real world.

A system that tracks the integrity of each agent and knows as soon as it is tainted seems the right approach.

With forking of LLM state you can maintain multiple states with different levels of trust and you can choose which leg gets removed depending on what task needs to be accomplished. I see it like a tree - always maintaining an untainted "trunk" that shoots of branches to do operations. Tainted branches are constrained to strict schemas for outputs, focused actions and limited tool sets.

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

#118
post #36

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.

Given its AI slop, itll gain features and bugs and insecurity at equal rates.

The real trifect of the pseudo singularity.

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

#119

not sure what’s the point of using/highlighting rust here. low-level language for a high-level application with IO-bound latency.

Codex is also in rust, no other modern language can compete. Maybe another older low level language. It's perfect for this kind of application.

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

#120

I've been been using OpenClaw for a bit now and the thing I'm missing is observability. What's this thing thinking/doing right now? Where's my audit log? Every rewrite I see fails to address this. I feel Elixir and the BEAM would be a perfect language to write this in. Gateways hanging, context window failures exhaustion can be elegantly modeled and remedied with supervision trees. For tracking thoughts, I can dump a…

those are all great ideas -- you should build it :)
Post reply on HN