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

121–130 of 165 posts

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

#121

Post by esskay »

StevenNunez wrote: post #103

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…

Agree on the observability. Every time I've seen that mentioned on the many, many discussions on Xitter theres one of the usual clickbait youtube 'bros' telling you to go watch their video on how to make your own ui for it. Really shouldn't need to for such a fundamentally basic and crucial part of it. It's a bit of a hot mess.

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

#122

Post by jbgt »

StevenNunez wrote: post #103

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…

https://github.com/z80dev/lemon

Sounds like exactly this, hot off the presses...

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

#123

Post by jakkos »

amoskvin wrote: post #114

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

- It is possible to write Rust in a pretty high level way that's much closer to a statically-typed Python than C++ and some people do use it as a Python replacement

- You can build it into a single binary with no external deps

- The Rust type system + ownership can help you a lot with correctness (e.g. encoding invariants, race conditions)

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

#124

Post by lxgr »

outofpaper wrote: post #113
backscratches wrote: post #105

Earlier quoted context omitted.

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.

To be fair, you do keep significantly more control of your own data from a data portability perspective! A MEMORY.md file presents almost zero lock-in compared to some SaaS offering.

Privacy-wise, of course, the inference provider sees everything.

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

#125

Post by ramon156 »

Szpadel wrote: post #23
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.

counterargument: I always hated writing docs and therefore most of thing that I done at my day job didn't had any and it made using it more difficult for others. I was also burnt many times where some software docs said one thing and after many hours of debugging I found out that code does something different. LLMs are so good at creating decent descriptions and keeping them up to date that I believe docs are the num…

> if they are correct I see no issue at all.

I guess the term "correct" is different for me. I shouldn't be able to nitpick comments out like that. Putting LLM's aside, they basically did not proof-read your own docs. Things like "No python required" are an obvious sign that you 1. Started talking about a project (you {found || built} in python), want to do it in Rust (because it's fast!) and then the LLM put that detail in the docs.

If they did not skim it out, then they did not read their own documentation. There was no love put into it.

Nonetheless, I totally get your point, and the docs are at least descriptive.

> LLMs are so good at creating decent descriptions and keeping them up to date

I totally agree! And now that CC auto-updates memories, it's much easier to keep track of changes. I'm also confident that you're the type of person to at least proof-read what it wrote, so I do not doubt your validity in your argument. It just sounds a lot different when you look at this project.

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

#126

Post by ctcq »

> I use it daily as a knowledge accumulator, research assistant, and autonomous task runner for my side projects. The memory compounds — every session makes the next one better.

Can you explain how that works? The `MEMORY.md` is able to persists session history. But it seems that it's necessary for the user to add to that file manually.

An automated way to achieve this would be awesome.

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

#127

Post by embedding-shape »

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

Earlier quoted context omitted.

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.

> but normies just want stuff to "work."

Where in the world are you getting that this project is for "normies"? Installation steps are terminal instructions and it's a CLI, clearly meant for technical people already.

If you think copying-pasting an API key is too much, don't you think cloning a git repository, installing the Rust compiler and compiling the project might be too much and hit those normies in the face sooner than the API key?

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

#128

Post by jagged-chisel »

lxgr wrote: post #124
outofpaper wrote: post #113

Earlier quoted context omitted.

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

To be fair, you do keep significantly more control of your own data from a data portability perspective! A MEMORY.md file presents almost zero lock-in compared to some SaaS offering. Privacy-wise, of course, the inference provider sees everything.

To be clear: keeping a local copy of some data provides not control over how the remote system treats that data once it’s sent.

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

#129

Post by the_harpia_io »

avoutic wrote: post #91
the_harpia_io wrote: post #81

[flagged]

Hitting production APIs (and email) is my main concern with all agents I run. To solve this I've built Wardgate [1], which removes the need for agents to see any credentials and has access control on a per API endpoints basis. So you can say: yes you can read all Todoist tasks but you can't delete tasks or see tasks with "secure" in them, or see emails outside Inbox or with OTP codes, or whatever. Interested in any c…

[flagged]

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

#130

Post by zipy124 »

jazzyjackson wrote: post #47
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…

IMHO it doesn't make sense, financially and resource wise to run local, given the 5 figure upfront costs to get an LLM running slower than I can get for 20 USD/m. If I'm running a business and have some number of employees to make use of it, and confidentiality is worth something, sure, but am I really going to rely on anything less then the frontier models for automating critical tasks? Or roll my own on prem IT to…

The usage limits on most 20 USD/month subs are becoming quite restrictive though. API pricing is more indicative of true cost.
Post reply on HN