Show HN: LocalGPT – A local-first AI assistant in Rust with persistent memory
18 by yi_wang | 3 comments on Hacker News.
I built LocalGPT over 4 nights as a Rust reimagining of the OpenClaw assistant pattern (markdown-based persistent memory, autonomous heartbeat tasks, skills system). It compiles to a single ~27MB binary — no Node.js, Docker, or Python required. Key features: - Persistent memory via markdown files (MEMORY, HEARTBEAT, SOUL markdown files) — compatible with OpenClaw's format - Full-text search (SQLite FTS5) + semantic search (local embeddings, no API key needed) - Autonomous heartbeat runner that checks tasks on a configurable interval - CLI + web interface + desktop GUI - Multi-provider: Anthropic, OpenAI, Ollama etc - Apache 2.0 Install: `cargo install localgpt` 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. GitHub: https://ift.tt/tOfosGu Website: https://localgpt.app Would love feedback on the architecture or feature ideas.
Hack Nux
Watch the number of websites being hacked today, one by one on a page, increasing in real time.
New Show Hacker News story: Show HN: More beautiful and usable Hacker News
Show HN: More beautiful and usable Hacker News
3 by shivamhwp | 0 comments on Hacker News.
gives you keyboard navigation.. let me know what you think.
3 by shivamhwp | 0 comments on Hacker News.
gives you keyboard navigation.. let me know what you think.
New Show Hacker News story: Show HN: Slack CLI for Agents
Show HN: Slack CLI for Agents
7 by nwparker | 3 comments on Hacker News.
Our team lives in Slack, but we don’t have access to the Slack MCP and couldn’t find anything out there that worked for us, so we coded our own agent-slack CLI * Can paste in Slack URLs * Token efficient * Zero-config (auto auth if you use Slack Desktop) Auto downloads files/snippets. Also can read Slack canvases as markdown! MIT License
7 by nwparker | 3 comments on Hacker News.
Our team lives in Slack, but we don’t have access to the Slack MCP and couldn’t find anything out there that worked for us, so we coded our own agent-slack CLI * Can paste in Slack URLs * Token efficient * Zero-config (auto auth if you use Slack Desktop) Auto downloads files/snippets. Also can read Slack canvases as markdown! MIT License
New ask Hacker News story: Tell HN: I'm a PM at a big system of record SaaS. We're cooked
Tell HN: I'm a PM at a big system of record SaaS. We're cooked
23 by throwawaypm123 | 0 comments on Hacker News.
I found myself disagreeing with almost all of the comments on the “AI Is Killing B2B SaaS” thread [1], based on my perspective as a senior PM (~20 years in SaaS) at a massive system of record (SoR) company in California. We’re still cooked. Throwaway for obvious reasons. BigCo SoRs, differences aside, have historically been a good, low-drama way to make a living in tech. RSUs, ~40-hour weeks, generally smart colleagues, and real problems to solve for F100 customers. Our products work, but are not loved. Enterprise sales runs the show. I have no concerns about a scrappy AI startup or indie dev replacing us. The real threat is other SoR vendors, the cloud providers, and of course the AI labs themselves. All of them are coming for our SaaS margins, and as an industry we are woefully unprepared. Every major SoR has its core competency (HR, ERP, CRM, etc.), but also a long tail of lesser-known portfolio products that increasingly overlap with other SoRs and serve as growth vectors. The competition here is only going to accelerate. As a huge enterprise, you’re not going to rip out a component your SoR for a cool startup or a vibe-coded internal tool... but you would seriously consider doing so if the alternative comes from another SoR vendor you use and is cheaper. The public cloud providers are explicitly positioning themselves as the place where your business data, AI agents/LLMs, and critical applications live. This is on a direct collision course with SoRs’ own AI platform ambitions that they are banking on for growth. The AI labs themselves have the same ambition. Note where systems of record sit in OpenAI’s Frontier press release marketecture: a dotted, nearly invisible line at the bottom [2]. SoRs aren’t dead, and they’re not being disrupted by vibe coders. But the path forward is brutal. Which brings me to the hardest point that applies to me as well. SoR teams are not known for fast execution, cutting edge AI adoption, product taste, or engineering excellence. These are exactly the strengths of our new competitors. We also struggle to attract this kind of talent. People who fit that profile go to FAANG or the labs. We could try to compete with RSUs, but those are down ~50% over the past few months, and the industry is under increasing pressure from investors around stock-based comp and M&A in general. The goal here is an honest take from someone on the inside. There’s a difficult road ahead. I think SoRs will always continue to exist in some form but I don’t think the recent market corrections are overblown. [1] https://ift.tt/pjPrkCq [2] https://ift.tt/VFmSlus
23 by throwawaypm123 | 0 comments on Hacker News.
I found myself disagreeing with almost all of the comments on the “AI Is Killing B2B SaaS” thread [1], based on my perspective as a senior PM (~20 years in SaaS) at a massive system of record (SoR) company in California. We’re still cooked. Throwaway for obvious reasons. BigCo SoRs, differences aside, have historically been a good, low-drama way to make a living in tech. RSUs, ~40-hour weeks, generally smart colleagues, and real problems to solve for F100 customers. Our products work, but are not loved. Enterprise sales runs the show. I have no concerns about a scrappy AI startup or indie dev replacing us. The real threat is other SoR vendors, the cloud providers, and of course the AI labs themselves. All of them are coming for our SaaS margins, and as an industry we are woefully unprepared. Every major SoR has its core competency (HR, ERP, CRM, etc.), but also a long tail of lesser-known portfolio products that increasingly overlap with other SoRs and serve as growth vectors. The competition here is only going to accelerate. As a huge enterprise, you’re not going to rip out a component your SoR for a cool startup or a vibe-coded internal tool... but you would seriously consider doing so if the alternative comes from another SoR vendor you use and is cheaper. The public cloud providers are explicitly positioning themselves as the place where your business data, AI agents/LLMs, and critical applications live. This is on a direct collision course with SoRs’ own AI platform ambitions that they are banking on for growth. The AI labs themselves have the same ambition. Note where systems of record sit in OpenAI’s Frontier press release marketecture: a dotted, nearly invisible line at the bottom [2]. SoRs aren’t dead, and they’re not being disrupted by vibe coders. But the path forward is brutal. Which brings me to the hardest point that applies to me as well. SoR teams are not known for fast execution, cutting edge AI adoption, product taste, or engineering excellence. These are exactly the strengths of our new competitors. We also struggle to attract this kind of talent. People who fit that profile go to FAANG or the labs. We could try to compete with RSUs, but those are down ~50% over the past few months, and the industry is under increasing pressure from investors around stock-based comp and M&A in general. The goal here is an honest take from someone on the inside. There’s a difficult road ahead. I think SoRs will always continue to exist in some form but I don’t think the recent market corrections are overblown. [1] https://ift.tt/pjPrkCq [2] https://ift.tt/VFmSlus
New Show Hacker News story: Show HN: A state-based narrative engine for tabletop RPGs
Show HN: A state-based narrative engine for tabletop RPGs
2 by KoeppyLoco | 0 comments on Hacker News.
I’m experimenting with modeling tabletop RPG adventures as explicit narrative state rather than linear scripts. Everdice is a small web app that tracks conditional scenes and choice-driven state transitions to preserve continuity across long or asynchronous campaigns. The core contribution is explicit narrative state and causality, not automation. The real heavy lifting is happening in the DM Toolkit/Run Sessions area, and integrates CAML (Canonical Adventure Modeling Language) that I developed to transport narratives among any number of platforms. I also built the npm CAML-lint to check validity of narratives. I'm interested in your thoughts. https://ift.tt/GzhAtbg
2 by KoeppyLoco | 0 comments on Hacker News.
I’m experimenting with modeling tabletop RPG adventures as explicit narrative state rather than linear scripts. Everdice is a small web app that tracks conditional scenes and choice-driven state transitions to preserve continuity across long or asynchronous campaigns. The core contribution is explicit narrative state and causality, not automation. The real heavy lifting is happening in the DM Toolkit/Run Sessions area, and integrates CAML (Canonical Adventure Modeling Language) that I developed to transport narratives among any number of platforms. I also built the npm CAML-lint to check validity of narratives. I'm interested in your thoughts. https://ift.tt/GzhAtbg