Live data from Hacker News

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

github.com

41–50 of 165 posts

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

#41
post #38
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.

LoL, don't worry they are getting their dose of the snakeoil too

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

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

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

#43
post #19

Earlier quoted context omitted.

[flagged]

EE with decades of experience here. You have valid points (SWE tedium, LLMs allowing adjacent technical fields to access SW/FW work without involving SWEs) that are completely lost because you're being an asshole for no good reason.

Awwww...

A look at OPs post-history, projecting back low-effort meta-analysis of their own uselessness seems apt.

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

#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" projects lately. What's the unique angle beyond "it's in Rust"?

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

#45
post #38
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.

What makes you think AI investment isn't a proxy for military advantage? Did you miss the saber rattling of anti-regulation lobbying, that we cannot pause or blink or apply rules to the AI industry because then China would overtake us?

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

#46
post #23
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…

engineer who was too lazy to write docs before now generates ai slop and continues not to write docs, news at 11

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

#47
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 support it when Amazon Bedrock will do it for me?

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

#48

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…

Hate to break it to you but most AI tools are vibe coded hot messes internally. Claude Code famously wears this as a badge of pride (https://newsletter.pragmaticengineer.com/p/how-claude-code-i...).

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

#49
post #15

Earlier quoted context omitted.

You absolutely do not have to use a third party llm. You can point it to any openai/anthropic compatible endpoint. It can even be on localhost.

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

In local setup you still usually want to split machine that runs inference from client that uses it, there are often non trivial resources used like chromium, compilation, databases etc involved that you don’t want to pollute inference machine with.

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

#50

Can someone explain to me why this needs to connect to LLM providers like OpenAI or Anthropic? I thought it was meant to be a local GPT. Sorry if i misunderstood what this project is trying to do. Does this mean the inference is remote and only context is local?

I applaud the effort of tinkering, re-creating and sharing, but I think the name is misleading - it is not at all a "local GPT". The contribution is not to do anything local and it is not a GPT model.

It is more like an OpenClaw rusty clone

Post reply on HN