Live data from Hacker News

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

github.com

131–140 of 165 posts

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

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

> but AI really does feel like living in the future.

Got the same feeling when I put on the Hololens for the first time but look what we have now.

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

#133

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…

If it’s plugged into any of the mainstream models like GPT, GPT-OSS, Claude etc, they lie to you about what it’s thinking.

They deliberately only show you a fraction of the thoughts, but charge you for all the secret ones.

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

#134
post #99

Earlier quoted context omitted.

It absolutely can be pointed to any standard endpoint, either cloud or local. It’s far better for most users to be able to specify an inference server (even on localhost in some cases) because the ecosystem of specialized inference servers and models is a constantly evolving target. If you write this kind of software, you will not only be reinventing the wheel but also probably disadvantaging your users if you try to…

It is not local first. Local is not the primary use case. The name is misleading to the point I almost didn't click because I do not run local models.

I think the author is using local-first as in “your files stay local, and the framework is compatible with on-prem infra”. Aside from not storing your docs and data with a cloud service though, it’s very usable with cloud inference providers, so I can see your point.

Maybe the author should have specified that capability, even though it seems redundant, since local-first implies local capability but also cloud compatibility, or it would be local or local-only.

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

#135
post #126

> 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.

> An automated way to achieve this would be awesome.

The author can easily do this by creating a simple memory tool call, announcing it in the prompt to the LLM, and having it call the tool.

I wrote an agent harness for my own use that allows add/remove memories and the AI uses it as you would expect - to keep notes for itself between sessions.

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

#136
post #44

Genuine question: what does this offer that OpenClaw doesn't already do? You're using the same memory format (SOUL.md, MEMORY.md, HEARTBEAT.md), similar architecture... but OpenClaw already ships with multi-channel messaging (Telegram, Discord, WhatsApp), voice calls, cron scheduling, browser automation, sub-agents, and a skills ecosystem. Not trying to be harsh — the AI agent space just feels crowded with "me too" p…

It's the static site generator of vibe coded projects.

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

#137

Earlier quoted context omitted.

> but I'm not really sure about calling it "local-first" as it's still reliant on an `ANTHROPIC_API_KEY`. See here: https://github.com/localgpt-app/localgpt/blob/main/src%2Fage...

What reasonable comparable model can be run locally on say 16GB of video memory compared to Opus 4.6? As far as I know Kimi (while good) needs serious GPUs GTX 6000 Ada minimum. More likely H100 or H200.

Devstral¹ has very good models that can be run locally.

They are in the top of open models, and surpass some closed models.

I've been using devstral, codestral and Le Chat exclusively for three months now. All from misteals hosted versions. Agentic, as completion and for day-to-day stuff. It's not perfect, but neither is any other model or product, so good enough for me. Less anecdotal are the various benchmarks that put them surprisingly high in the rankings

¹https://mistral.ai/news/devstral

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

#138
post #86

Earlier quoted context omitted.

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…

That’s probably true only as long as subscription prices are kept artificially low. Once the $20 becomes $200 (or the fast-mode inference quotas for cheap subs become unusably small), the equation may change.

This field is highly competitive. Much more than I expected it to. I thought the barrier to entry was so high, only big tech could seriously join the race, because of costs, or training data etc.

But there's fierce competition by new or small players (deepseek, Mistral etc), many even open source. And Icm convinced they'll keep the prices low.

A company like openai can only increase subscriptions x10 when they've locked in enough clients, have a monopoly or oligopoly, or their switching costs are multitudes of that.

So currently the irony seems to be that the larger the AI company, the more loss they're running at. Size seems to have a negative impact on business. But the smaller operators also prevent companies from raising prices to levels at which they make money.

Post reply on HN