The best Hacker News stories from Show from the past week
Latest posts:
Show HN: Whosthere: A LAN discovery tool with a modern TUI, written in Go
Show HN: Whosthere: A LAN discovery tool with a modern TUI, written in Go
Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete
Hey HN, we trained and open-sourced a 1.5B model that predicts your next edits, similar to Cursor. You can download the weights here (<a href="https://huggingface.co/sweepai/sweep-next-edit-1.5b" rel="nofollow">https://huggingface.co/sweepai/sweep-next-edit-1.5b</a>) or try it in our JetBrains plugin (<a href="https://plugins.jetbrains.com/plugin/26860-sweep-ai-autocomplete--coding-agent" rel="nofollow">https://plugins.jetbrains.com/plugin/26860-sweep-ai-autocomp...</a>).<p>Next-edit autocomplete differs from standard autocomplete by using your recent edits as context when predicting completions. The model is small enough to run locally while outperforming models 4x its size on both speed and accuracy.<p>We tested against Mercury (Inception), Zeta (Zed), and Instinct (Continue) across five benchmarks: next-edit above/below cursor, tab-to-jump for distant changes, standard FIM, and noisiness. We found exact-match accuracy correlates best with real usability because code is fairly precise and the solution space is small.<p>Prompt format turned out to matter more than we expected. We ran a genetic algorithm over 30+ diff formats and found simple `original`/`updated` blocks beat unified diffs. The verbose format is just easier for smaller models to understand.<p>Training was SFT on ~100k examples from permissively-licensed repos (4hrs on 8xH100), then RL for 2000 steps with tree-sitter parse checking and size regularization. The RL step fixes edge cases SFT can’t like, generating code that doesn’t parse or overly verbose outputs.<p>We're open-sourcing the weights so the community can build fast, privacy-preserving autocomplete for any editor. If you're building for VSCode, Neovim, or something else, we'd love to see what you make with it!
Show HN: isometric.nyc – giant isometric pixel art map of NYC
Hey HN! I wanted to share something I built over the last few weeks: isometric.nyc is a massive isometric pixel art map of NYC, built with nano banana and coding agents.<p>I didn't write a single line of code.<p>Of course no-code doesn't mean no-engineering. This project took a lot more manual labor than I'd hoped!<p>I wrote a deep dive on the workflow and some thoughts about the future of AI coding and creativity:<p><a href="http://cannoneyed.com/projects/isometric-nyc" rel="nofollow">http://cannoneyed.com/projects/isometric-nyc</a>
Show HN: Rails UI
Show HN: ChartGPU – WebGPU-powered charting library (1M points at 60fps)
Creator here. I built ChartGPU because I kept hitting the same wall: charting libraries that claim to be "fast" but choke past 100K data points.<p>The core insight: Canvas2D is fundamentally CPU-bound. Even WebGL chart libraries still do most computation on the CPU. So I moved everything to the GPU via WebGPU:<p>- LTTB downsampling runs as a compute shader
- Hit-testing for tooltips/hover is GPU-accelerated
- Rendering uses instanced draws (one draw call per series)<p>The result: 1M points at 60fps with smooth zoom/pan.<p>Live demo: <a href="https://chartgpu.github.io/ChartGPU/examples/million-points/" rel="nofollow">https://chartgpu.github.io/ChartGPU/examples/million-points/</a><p>Currently supports line, area, bar, scatter, pie, and candlestick charts. MIT licensed, available on npm: `npm install chartgpu`<p>Happy to answer questions about WebGPU internals or architecture decisions.
Show HN: Mastra 1.0, open-source JavaScript agent framework from the Gatsby devs
Hi HN, we're Sam, Shane, and Abhi.<p>Almost a year ago, we first shared Mastra here (<a href="https://news.ycombinator.com/item?id=43103073">https://news.ycombinator.com/item?id=43103073</a>). It’s kind of fun looking back since we were only a few months into building at the time. The HN community gave a lot of enthusiasm and some helpful feedback.<p>Today, we released Mastra 1.0 in stable, so we wanted to come back and talk about what’s changed.<p>If you’re new to Mastra, it's an open-source TypeScript agent framework that also lets you create multi-agent workflows, run evals, inspect in a local studio, and emit observability.<p>Since our last post, Mastra has grown to over 300k weekly npm downloads and 19.4k GitHub stars. It’s now Apache 2.0 licensed and runs in prod at companies like Replit, PayPal, and Sanity.<p>Agent development is changing quickly, so we’ve added a lot since February:<p>- Native model routing: You can access 600+ models from 40+ providers by specifying a model string (e.g., `openai/gpt-5.2-codex`) with TS autocomplete and fallbacks.<p>- Guardrails: Low-latency input and output processors for prompt injection detection, PII redaction, and content moderation. The tricky thing here was the low-latency part.<p>- Scorers: An async eval primitive for grading agent outputs. Users were asking how they should do evals. We wanted to make it easy to attach to Mastra agents, runnable in Mastra studio, and save results in Mastra storage.<p>- Plus a few other features like AI tracing (per-call costing for Langfuse, Braintrust, etc), memory processors, a `.network()` method that turns any agent into a routing agent, and server adapters to integrate Mastra within an existing Express/Hono server.<p>(That last one took a bit of time, we went down the ESM/CJS bundling rabbithole, ran into lots of monorepo issues, and ultimately opted for a more explicit approach.)<p>Anyway, we'd love for you to try Mastra out and let us know what you think. You can get started with `npm create mastra@latest`.<p>We'll be around and happy to answer any questions!
Show HN: Pdfwithlove – PDF tools that run 100% locally (no uploads, no back end)
Most PDF web tools make millions by uploading documents that never needed to leave your computer.<p>pdfwithlove does the opposite:<p>1. 100% local processing
2. No uploads, no backend, no tracking<p>Features include merge/split/edit/compress PDFs, watermarks & signatures, and image/HTML/Office → PDF conversion.
Show HN: Pdfwithlove – PDF tools that run 100% locally (no uploads, no back end)
Most PDF web tools make millions by uploading documents that never needed to leave your computer.<p>pdfwithlove does the opposite:<p>1. 100% local processing
2. No uploads, no backend, no tracking<p>Features include merge/split/edit/compress PDFs, watermarks & signatures, and image/HTML/Office → PDF conversion.
Show HN: I quit coding years ago. AI brought me back
Quick background: I used to code. Studied it in school, wrote some projects, but eventually convinced myself I wasn't cut out for it. Too slow, too many bugs, imposter syndrome — the usual story. So I pivoted, ended up as an investment associate at an early-stage angel fund, and haven't written real code in years.<p>Fast forward to now. I'm a Buffett nerd — big believer in compound interest as a mental model for life. I run compound interest calculations constantly. Not because I need to, but because watching numbers grow over 30-40 years keeps me patient when markets get wild. It's basically meditation for long-term investors.<p>The problem? Every compound interest calculator online is terrible. Ugly interfaces, ads covering half the screen, can't customize compounding frequency properly, no year-by-year breakdowns. I've tried so many. They all suck.<p>When vibe coding started blowing up, something clicked. Maybe I could actually build the calculators I wanted? I don't have to be a "real developer" anymore — I just need to describe what I want clearly.<p>So I tried it.<p>Two weeks and ~$100（Opus 4.5 thinking model） in API costs later: I somehow have 60+ calculators. Started with compound interest, naturally. Then thought "well, while I'm here..." and added mortgage, loan amortization, savings goals, retirement projections. Then it spiraled — BMI calculator, timezone converter, regex tester. Oops.<p>The AI (I'm using Claude via Windsurf) handled the grunt work beautifully. I'd describe exactly what I wanted — "compound interest calculator with monthly/quarterly/yearly options, year-by-year breakdown table, recurring contribution support" — and it delivered. With validation, nice components, even tests.<p>What I realized: my years away from coding weren't wasted. I still understood architecture, I still knew what good UX looked like, I still had domain expertise (financial math). I just couldn't type it all out efficiently. AI filled that gap perfectly.<p>Vibe coding didn't make me a 10x engineer. But it gave me permission to build again. Ideas I've had for years suddenly feel achievable. That's honestly the bigger win for me.<p>Stack: Next.js, React, TailwindCSS, shadcn/ui, four languages (EN/DE/FR/JA). The AI picked most of this when I said "modern and clean."<p>Site's live at <a href="https://calquio.com" rel="nofollow">https://calquio.com</a> . The compound interest calculator is still my favorite page — finally exactly what I wanted.<p>Curious if others have similar stories. Anyone else come back to building after stepping away?
Show HN: I quit coding years ago. AI brought me back
Quick background: I used to code. Studied it in school, wrote some projects, but eventually convinced myself I wasn't cut out for it. Too slow, too many bugs, imposter syndrome — the usual story. So I pivoted, ended up as an investment associate at an early-stage angel fund, and haven't written real code in years.<p>Fast forward to now. I'm a Buffett nerd — big believer in compound interest as a mental model for life. I run compound interest calculations constantly. Not because I need to, but because watching numbers grow over 30-40 years keeps me patient when markets get wild. It's basically meditation for long-term investors.<p>The problem? Every compound interest calculator online is terrible. Ugly interfaces, ads covering half the screen, can't customize compounding frequency properly, no year-by-year breakdowns. I've tried so many. They all suck.<p>When vibe coding started blowing up, something clicked. Maybe I could actually build the calculators I wanted? I don't have to be a "real developer" anymore — I just need to describe what I want clearly.<p>So I tried it.<p>Two weeks and ~$100（Opus 4.5 thinking model） in API costs later: I somehow have 60+ calculators. Started with compound interest, naturally. Then thought "well, while I'm here..." and added mortgage, loan amortization, savings goals, retirement projections. Then it spiraled — BMI calculator, timezone converter, regex tester. Oops.<p>The AI (I'm using Claude via Windsurf) handled the grunt work beautifully. I'd describe exactly what I wanted — "compound interest calculator with monthly/quarterly/yearly options, year-by-year breakdown table, recurring contribution support" — and it delivered. With validation, nice components, even tests.<p>What I realized: my years away from coding weren't wasted. I still understood architecture, I still knew what good UX looked like, I still had domain expertise (financial math). I just couldn't type it all out efficiently. AI filled that gap perfectly.<p>Vibe coding didn't make me a 10x engineer. But it gave me permission to build again. Ideas I've had for years suddenly feel achievable. That's honestly the bigger win for me.<p>Stack: Next.js, React, TailwindCSS, shadcn/ui, four languages (EN/DE/FR/JA). The AI picked most of this when I said "modern and clean."<p>Site's live at <a href="https://calquio.com" rel="nofollow">https://calquio.com</a> . The compound interest calculator is still my favorite page — finally exactly what I wanted.<p>Curious if others have similar stories. Anyone else come back to building after stepping away?
Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss
Hey HN – I built Dock after years of team chat frustrations as a founder.
Free forever for teams up to 5. Unlimited search, unlimited history. No "upgrade to see messages older than 90 days" nonsense.
Built for teams who work both async and sync/real-time when it matters. runs on SOC 2 infra, compliant, secure and in-transit and at-rest encryption, runs on Cloudflare.<p>Early stage – would love feedback from anyone who's felt the same pain.
Show HN: Dock – Slack minus the bloat, tax, and 90-day memory loss
Hey HN – I built Dock after years of team chat frustrations as a founder.
Free forever for teams up to 5. Unlimited search, unlimited history. No "upgrade to see messages older than 90 days" nonsense.
Built for teams who work both async and sync/real-time when it matters. runs on SOC 2 infra, compliant, secure and in-transit and at-rest encryption, runs on Cloudflare.<p>Early stage – would love feedback from anyone who's felt the same pain.
Show HN: OpenWork – An open-source alternative to Claude Cowork
hi hn,<p>i built openwork, an open-source, local-first system inspired by claude cowork.<p>it’s a native desktop app that runs on top of opencode (opencode.ai).
it’s basically an alternative gui for opencode, which (at least until now) has been more focused on technical folks.<p>the original seed for openwork was simple: i have a home server, and i wanted my wife and i to be able to run privileged workflows. things like controlling home assistant, or deploying custom web apps (e.g. our customs recipe app recipes.benjaminshafii.com), legal torrents, without living in a terminal.<p>our initial setup was running the opencode web server directly and sharing credentials to it. that worked, but i found the web ui unreliable and very unfriendly for non-technical users.<p>the goal with openwork is to bring the kind of workflows i’m used to running in the cli into a gui, while keeping a very deep extensibility mindset. ideally this grows into something closer to an obsidian-style ecosystem, but for agentic work.<p>some core principles i had in mind:<p>- open by design: no black boxes, no hosted lock-in. everything runs locally or on your own servers. (models don’t run locally yet, but both opencode and openwork are built with that future in mind.)
- hyper extensible: skills are installable modules via a skill/package manager, using the native opencode plugin ecosystem.
- non-technical by default: plans, progress, permissions, and artifacts are surfaced in the ui, not buried in logs.<p>you can already try it:
- there’s an unsigned dmg
- or you can clone the repo, install deps, and if you already have opencode running it should work right away<p>it’s very alpha, lots of rough edges. i’d love feedback on what feels the roughest or most confusing.<p>happy to answer questions.
Show HN: WebTiles – create a tiny 250x250 website with neighbors around you
There is a large grid of 250x250 tiles, on which you are be able to create a tiny website, contained into the tile.
You can basically consider the tile as a mini version of your website, showcasing what your full site has (but it can be anything). You are able to link to your full site, and use any HTML/CSS/JS inside. The purpose is to create beautiful and interesting tiles, that could be used for exploring the indie-web in an easy and interesting way.
Show HN: OSS AI agent that indexes and searches the Epstein files
Hi HN,<p>I built an open-source AI agent that has already indexed and can search the entire Epstein files, roughly 100M words of publicly released documents.<p>The goal was simple: make a large, messy corpus of PDFs and text files immediately searchable in a precise way, without relying on keyword search or bloated prompts.<p>What it does:<p>- The full dataset is already indexed
- You can ask natural language questions
- Answers are grounded and include direct references to source documents
- Supports both exact text lookup and semantic search<p>Discussion around these files is often fragmented. This makes it possible to explore the primary sources directly and verify claims without manually digging through thousands of pages.<p>Happy to answer questions or go into technical details.<p>Code: <a href="https://github.com/nozomio-labs/nia-epstein-ai" rel="nofollow">https://github.com/nozomio-labs/nia-epstein-ai</a>
Show HN: Self-host Reddit – 2.38B posts, works offline, yours forever
Reddit's API is effectively dead for archival. Third-party apps are gone. Reddit has threatened to cut off access to the Pushshift dataset multiple times. But 3.28TB of Reddit history exists as a torrent right now, and I built a tool to turn it into something you can browse on your own hardware.<p>The key point: This doesn't touch Reddit's servers. Ever. Download the Pushshift dataset, run my tool locally, get a fully browsable archive. Works on an air-gapped machine. Works on a Raspberry Pi serving your LAN. Works on a USB drive you hand to someone.<p>What it does: Takes compressed data dumps from Reddit (.zst), Voat (SQL), and Ruqqus (.7z) and generates static HTML. No JavaScript, no external requests, no tracking. Open index.html and browse. Want search? Run the optional Docker stack with PostgreSQL – still entirely on your machine.<p>API & AI Integration: Full REST API with 30+ endpoints – posts, comments, users, subreddits, full-text search, aggregations. Also ships with an MCP server (29 tools) so you can query your archive directly from AI tools.<p>Self-hosting options:
- USB drive / local folder (just open the HTML files)
- Home server on your LAN
- Tor hidden service (2 commands, no port forwarding needed)
- VPS with HTTPS
- GitHub Pages for small archives<p>Why this matters: Once you have the data, you own it. No API keys, no rate limits, no ToS changes can take it away.<p>Scale: Tens of millions of posts per instance. PostgreSQL backend keeps memory constant regardless of dataset size. For the full 2.38B post dataset, run multiple instances by topic.<p>How I built it: Python, PostgreSQL, Jinja2 templates, Docker. Used Claude Code throughout as an experiment in AI-assisted development. Learned that the workflow is "trust but verify" – it accelerates the boring parts but you still own the architecture.<p>Live demo: <a href="https://online-archives.github.io/redd-archiver-example/" rel="nofollow">https://online-archives.github.io/redd-archiver-example/</a><p>GitHub: <a href="https://github.com/19-84/redd-archiver" rel="nofollow">https://github.com/19-84/redd-archiver</a> (Public Domain)<p>Pushshift torrent: <a href="https://academictorrents.com/details/1614740ac8c94505e4ecb9d88be8bed7b6afddd4" rel="nofollow">https://academictorrents.com/details/1614740ac8c94505e4ecb9d...</a>
Show HN: AI in SolidWorks
Hey HN! We’re Will and Jorge, and we’ve built LAD (Language-Aided Design), a SolidWorks add-in that uses LLMs to create sketches, features, assemblies, and macros from conversational inputs (<a href="https://www.trylad.com/" rel="nofollow">https://www.trylad.com/</a>).<p>We come from software engineering backgrounds where tools like Claude Code and Cursor have come to dominate, but when poking around CAD systems a few months back we realized there's no way to go from a text prompt input to a modeling output in any of the major CAD systems. In our testing, the LLMs aren't as good at making 3D objects as they are are writing code, but we think they'll get a lot better in the upcoming months and years.<p>To bridge this gap, we've created LAD, an add-in in SolidWorks to turn conversational input and uploaded documents/images into parts, assemblies, and macros. It includes:<p>- Dozens of tools the LLM can call to create sketches, features, and other objects in parts.<p>- Assembly tools the LLM can call to turn parts into assemblies.<p>- File system tools the LLM can use to create, save, search, and read SolidWorks files and documentation.<p>- Macro writing/running tools plus a SolidWorks API documentation search so the LLM can use macros.<p>- Automatic screenshots and feature tree parsing to provide the LLM context on the current state.<p>- Checkpointing to roll back unwanted edits and permissioning to determine which commands wait for user permission.<p>You can try LAD at <a href="https://www.trylad.com/" rel="nofollow">https://www.trylad.com/</a> and let us know what features would make it more useful for your work. To be honest, the LLMs aren't great at CAD right now, but we're mostly curious to hear if people would want and use this if it worked well.
Show HN: Ferrite – Markdown editor in Rust with native Mermaid diagram rendering
Ferrite: Fast Markdown/Text/Code editor in Rust with native Mermaid diagrams<p>Built a Markdown editor using Rust + egui. v0.2.1 just dropped with major Mermaid improvements:<p>→ Native Mermaid diagrams - Flowcharts, sequence, state, ER, git graphs - pure Rust, no JS<p>→ Split view - Raw + rendered side-by-side with sync scrolling<p>→ Syntax highlighting - 40+ languages with large file optimization<p>→ JSON/YAML/TOML tree viewer - Structured editing with expand/collapse<p>→ Git integration - File tree shows modified/staged/untracked status<p>Also: minimap, zen mode, auto-save, session restore, code folding indicators.<p>~15MB binary, instant startup. Windows/Linux/macOS.<p>GitHub: <a href="https://github.com/OlaProeis/Ferrite" rel="nofollow">https://github.com/OlaProeis/Ferrite</a><p>v0.2.2 coming soon with performance improvements for large files. Looking for feedback!
Show HN: Ferrite – Markdown editor in Rust with native Mermaid diagram rendering
Ferrite: Fast Markdown/Text/Code editor in Rust with native Mermaid diagrams<p>Built a Markdown editor using Rust + egui. v0.2.1 just dropped with major Mermaid improvements:<p>→ Native Mermaid diagrams - Flowcharts, sequence, state, ER, git graphs - pure Rust, no JS<p>→ Split view - Raw + rendered side-by-side with sync scrolling<p>→ Syntax highlighting - 40+ languages with large file optimization<p>→ JSON/YAML/TOML tree viewer - Structured editing with expand/collapse<p>→ Git integration - File tree shows modified/staged/untracked status<p>Also: minimap, zen mode, auto-save, session restore, code folding indicators.<p>~15MB binary, instant startup. Windows/Linux/macOS.<p>GitHub: <a href="https://github.com/OlaProeis/Ferrite" rel="nofollow">https://github.com/OlaProeis/Ferrite</a><p>v0.2.2 coming soon with performance improvements for large files. Looking for feedback!