The best Hacker News stories from Show from the past day
Latest posts:
Show HN: I built a tool to un-dumb Claude Code's CLI output (Local Log Viewer)
Hi HN,<p>I built this because I got tired of the Claude Code CLI hiding details from me.<p>Recent updates have replaced critical output with summaries like "Read 3 files" or "Edited 2 files". To see what actually happened, I was forced to use `--verbose`, which floods the terminal with unreadable JSON and system prompts.<p>I wanted a middle ground: *Full observability without the noise.*<p>`claude-devtools` is a local Electron app that tails the session logs in `~/.claude/` to reconstruct the execution trace in real-time.<p>*Unlike wrappers, it solves the visibility gap in your native terminal workflow:*
1. *Real Diffs:* It shows inline diffs (red/green) the moment files are edited, instead of just a checkmark.
2. *Context Forensics:* It breaks down token usage by File vs Tool Output vs Thinking (so you know exactly why your context window is full).
3. *Agent Trees:* It visualizes sub-agent execution paths which are usually interleaved and confusing in the CLI.<p>It’s 100% local, and works with the logs already on your machine. No API keys required.<p>Repo: <a href="https://github.com/matt1398/claude-devtools" rel="nofollow">https://github.com/matt1398/claude-devtools</a>
(Screenshots and diff viewer demo are in the README)
Show HN: Scanned 1927-1945 Daily USFS Work Diary
My great-grandfather Reuben P. Box was a US Forest Ranger in Northern California, and I've got his daily work diary from 1927-1945, through the depression, WWII, Conservation Corps, and lots of forest fires. I've scanned the entire thing, had Claude help with transcription, indexing, and web site building, and put the whole thing here:<p><a href="https://forestrydiary.com/" rel="nofollow">https://forestrydiary.com/</a><p>This is one of those projects I've sat on for years, but with Claude and Mistral helping with the handwriting recognition, and even helping me write a custom scanning app that would auto scan each page and put it into a database as I assembled everything.<p>As far as I know, this is the only US Forestry Diary that has been fully scanned in and published. I understand that there are other diaries in some collections, but none have been scanned in. I hope this helps somebody. Please let me know if it does.<p>This is the sort of project Claude and AI can help with - A personal project that sits on the shelf forever, but now a reasonable project that can be published in my spare time. I'm not trying to earn money on this, but just improving our knowledge and history just a little bit.
Show HN: Glitchy camera – a circuit-bent camera simulator in the browser
Fun little side project I built after learning about circuit bending in cameras for intentional glitch effect. It is browser based camera toy where you "rewire" CCD pin pairs, turn knobs to get different glitch artefacts in real time to capture as photos. I had fun learning to simulate different pin modes - channel split, hue/phase shifts, horizontal clock delays, colour kill etc.<p>Here are some photos taken: <a href="https://glitchycam.com/gallery" rel="nofollow">https://glitchycam.com/gallery</a><p>I intentionally leaned towards skeuomorphic design for nostalgia. I miss the days where I'd spend hours making a button to look like a physical button. Here I chose to make it look like a "good enough" Teenage Engineering device UI.<p>I tested/used GPT-5.3-Codex to build this from scratch, since there was a lot of hype around it on X. Maybe I wasn’t using it right, but I found it needed a lot of code cleanup at every step and a lot of hand holding along the way. It missed details/nuances and didn't land the skeuomorphic buttons or the interaction polish. It mostly helped with boilerplate where there wasn't much thinking/detailing. It did give a basic starting point for the effect calculations, but didn't really move the needle on the details.<p>Please give it a go and let me know what you think - your photos and video never leave your browser (you can download them if you choose to). Everything is processed locally in your browser (works offline), nothing is uploaded or seen by anyone.
Show HN: I taught LLMs to play Magic: The Gathering against each other
I've been teaching LLMs to play Magic: The Gathering recently, via MCP tools hooked up to the open-source XMage codebase. It's still pretty buggy and I think there's significant room for existing models to get better at it via tooling improvements, but it pretty much works today. The ratings for expensive frontier models are artificially low right now because I've been focusing on cheaper models until I work out the bugs, so they don't have a lot of games in the system.
Show HN: I wrote a technical history book on Lisp
The book page links to a blog post that explains how I got about it (and
has a link to sample content), but the TL&DR is that I could not find
a lot of books that were on "our" history _and_ were larded with technical
details. So I set about writing one, and some five years later I'm happy
to share the result. I think it's one of the few "computer history" books that has tons of code, but correct me if I'm wrong (I wrote this both to tell a story and to learn :-)).<p>My favorite languages are Smalltalk and Lisp, but as an Emacs user, I've been
using the latter for much longer and for my current projects, Common Lisp is a better fit, so I call myself "a Lisp-er" these days. If people like what I did,
I do have plans to write some more (but probably only after I retire, writing next to a full-time job is heard). Maybe on Smalltalk, maybe on computer networks - two topics close to my heart.<p>And a shout-out to Dick Gabriel, he contributed some great personal memories about the man who started it all, John McCarthy.
Show HN: AsteroidOS 2.0 – Nobody asked, we shipped anyway
Hi HN,
After roughly 8 years of silently rolling 1.1 nightlies, we finally tagged a proper stable 2.0 release.
We built this because wrist-sized Linux is genuinely fun to hack on, and because a handful of us think it's worth keeping capable hardware alive long after manufacturers move on. Smartwatches don't really get old — the silicon is basically the same as it was a decade ago. We just keep making it useful for us.<p>No usage stats, no tracking, no illusions of mass adoption. The only real signal we get is the occasional person who appears in our Matrix chat going "hey, it booted on my watch from 2014 and now it's usable again" — and that's plenty.<p>Privacy is non-negotiable: zero telemetry, no cloud, full local control. Longevity is the other half: we refuse to let good hardware become e-waste just because support ended.
On the learning side, it's been one of the best playgrounds: instant feedback on your wrist makes QML/Qt, JavaScript watchfaces and embedded Linux feel tangible. The community is small and kind — perfect for people who want to learn open-source dev without gatekeeping.<p>Technically we're still pragmatic: libhybris + older kernels on most devices since it just works, but we've already mainlined rinato (Samsung Gear 2) and sparrow (ASUS ZenWatch 2) — rinato even boots with a usable UI. That's the direction we're pushing toward.<p>Repo: <a href="https://github.com/AsteroidOS" rel="nofollow">https://github.com/AsteroidOS</a>
Install images & docs: <a href="https://asteroidos.org" rel="nofollow">https://asteroidos.org</a>
2.0 demo video : <a href="https://www.youtube.com/watch?v=U6FiQz0yACc" rel="nofollow">https://www.youtube.com/watch?v=U6FiQz0yACc</a>
Announcement post: <a href="https://asteroidos.org/news/2-0-release/" rel="nofollow">https://asteroidos.org/news/2-0-release/</a><p>Questions, port requests, mentoring offers, criticism, weird ideas — all welcome. We do this because shaping a tiny, open wearable UX and infrastructure is oddly satisfying, and because Linux on the wrist still feels like a playground worth playing in.<p>Cheers, the AsteroidOS Team
Show HN: Lightwave – Real-time notes app, 3.5 years of hand-rolled JavaScript
Hi HN!<p>I've been building this solo for about three and a half years. I kept trying every new project/notes tool (Notion, Asana, Trello, etc.) and always ended up back in a plain text file. I wanted something that felt like a text editor on first touch but could grow into real structure when you needed it.<p><a href="https://lightwave.so" rel="nofollow">https://lightwave.so</a> (desktop only)<p>The tech stack is Laravel, MySQL, Redis, and hand-rolled JavaScript on the client. No frameworks like React/Vue/etc. ~270 lines of jQuery (out of 80k+ total LOC) for a few legacy DOM utilities, plus IndexedDB for local persistence. Real-time collaboration uses a hybrid approach: HTTP/2 POST for resilient ops + WebSockets via Laravel Reverb for live cursors, presence, and edits.<p>This is a pre-release stress test, not a launch. Lightwave will be a paid product. Right now I'm opening it up because no amount of solo testing replicates getting punched in the mouth by real traffic.<p>The link above has a button to create a test account in 1 click.<p>Known rough edges: the cursor and selection system are built from scratch (like VS Code, not a contenteditable wrapper), so there's a lot of surface area. Some keyboard shortcuts may be missing. Desktop only, accessibility not yet implemented. I'm shipping fixes in real time.<p>There's a "Submit Bug or Feedback" button inside the app if something breaks. Happy to answer any questions about the architecture, or anything else.<p>Some highlights:<p>- Paste markdown in, get native blocks. Copy blocks out, get markdown back.<p>- Hierarchical document, structure. Hierarchichal file manager.<p>- Live collab with shared cursors, selection, and presence.<p>- Code blocks with syntax highlighting. LaTeX math blocks.<p>- Full data export: markdown, JSON, and attachments. No lock-in.<p>- Full undo/redo with cursor restoration.
Show HN: Maths, CS and AI Compendium
Hey HN, I don’t know who else has the same issue, but:<p>Textbooks often bury good ideas in dense notation, skip the intuition, assume you already know half the material, and get outdated in fast-moving fields like AI.<p>Over the past 7 years of my AI/ML experience, I filled notebooks with intuition-first, real-world context, no hand-waving explanations of maths, computing and AI concepts.<p>In 2024, a few friends used these notes to prep for interviews at DeepMind, OpenAI, Nvidia etc. They all got in and currently perform well in their roles. So I'm sharing.<p>This is an open & unconventional textbook covering maths, computing, and artificial intelligence from the ground up. For curious practitioners seeking deeper understanding, not just survive an exam/interview.<p>To ambitious students, an early careers or experts in adjacent fields looking to become cracked AI research engineers or progress to PhD, dig in and let me know your thoughts.
Show HN: Wildex – Pokémon Go for real wildlife
Dear HN,<p>My wife and I both love nature and have always wanted a Pokémon go style app, to collect and learn about different species we find.<p>All the usual species identifying apps were didn’t feel fun enough, so we designed and built one together!<p>Would love for you guys to give it a try and share any thoughts you have.
Show HN: Wildex – Pokémon Go for real wildlife
Dear HN,<p>My wife and I both love nature and have always wanted a Pokémon go style app, to collect and learn about different species we find.<p>All the usual species identifying apps were didn’t feel fun enough, so we designed and built one together!<p>Would love for you guys to give it a try and share any thoughts you have.
Show HN: Free alternative to Wispr Flow, Superwhisper, and Monologue
Show HN: Free alternative to Wispr Flow, Superwhisper, and Monologue
Show HN: Jemini – Gemini for the Epstein Files
Related: <i>Show HN: JeffTube</i> - <a href="https://news.ycombinator.com/item?id=47030797">https://news.ycombinator.com/item?id=47030797</a>
Show HN: Jemini – Gemini for the Epstein Files
Related: <i>Show HN: JeffTube</i> - <a href="https://news.ycombinator.com/item?id=47030797">https://news.ycombinator.com/item?id=47030797</a>
Show HN: Pangolin: Open-source identity-based VPN (Twingate/Zscaler alternative)
Pangolin (<a href="https://github.com/fosrl/pangolin" rel="nofollow">https://github.com/fosrl/pangolin</a>) is an open-source tool for identity-based remote access to internal resources - an alternative to Cloudflare ZTNA, Zscaler, and Twingate.<p>It’s different than existing approaches: mesh VPNs (Tailscale, ZeroTier, etc.) create flat overlay networks where ACL and IP space management becomes complex at scale and every device can talk to every other device, while corporate ZTNA solutions (Zscaler, Cato, Netskope etc.) are closed-source and add latency by forcing traffic through a central server.<p>Pangolin takes a resource-centric approach. You deploy lightweight connectors that bridge to specific resources (private web apps, SSH, databases, CIDR ranges). Admins delegate resource-access to specific users and roles. It uses WireGuard with NAT hole-punching for peer-to-peer connections and traffic goes directly between the user and connector instead of through a central server. It supports native clients (Mac/Windows/Linux/iOS/Android) plus identity-aware, browser-based access when a client isn’t required.<p>Pangolin has a cloud and is optionally self-hosted. The Community Edition is AGPLv3. The Enterprise Edition is also open-source under the commercial license which enables free personal/small business use.<p>Everything, from the server to the clients, is fully open-source and you can even self-host the whole stack. We’d love to hear what you think and I'm happy to answer any questions!
Show HN: Pangolin: Open-source identity-based VPN (Twingate/Zscaler alternative)
Pangolin (<a href="https://github.com/fosrl/pangolin" rel="nofollow">https://github.com/fosrl/pangolin</a>) is an open-source tool for identity-based remote access to internal resources - an alternative to Cloudflare ZTNA, Zscaler, and Twingate.<p>It’s different than existing approaches: mesh VPNs (Tailscale, ZeroTier, etc.) create flat overlay networks where ACL and IP space management becomes complex at scale and every device can talk to every other device, while corporate ZTNA solutions (Zscaler, Cato, Netskope etc.) are closed-source and add latency by forcing traffic through a central server.<p>Pangolin takes a resource-centric approach. You deploy lightweight connectors that bridge to specific resources (private web apps, SSH, databases, CIDR ranges). Admins delegate resource-access to specific users and roles. It uses WireGuard with NAT hole-punching for peer-to-peer connections and traffic goes directly between the user and connector instead of through a central server. It supports native clients (Mac/Windows/Linux/iOS/Android) plus identity-aware, browser-based access when a client isn’t required.<p>Pangolin has a cloud and is optionally self-hosted. The Community Edition is AGPLv3. The Enterprise Edition is also open-source under the commercial license which enables free personal/small business use.<p>Everything, from the server to the clients, is fully open-source and you can even self-host the whole stack. We’d love to hear what you think and I'm happy to answer any questions!
Show HN: Klaw.sh – Kubernetes for AI agents
Hi everyone,<p>I run a generative AI infra company, unified API for 600+ models. Our team started deploying AI agents for our marketing and lead gen ops: content, engagement, analytics across multiple X accounts.<p>OpenClaw worked fine for single agents. But at ~14 agents across 6 accounts, the problem shifted from "how do I build agents" to "how do I manage them."<p>Deployment, monitoring, team isolation, figuring out which agent broke what at 3am. Classic orchestration problem.<p>So I built klaw, modeled on Kubernetes:
Clusters — isolated environments per org/project
Namespaces — team-level isolation (marketing, sales, support)
Channels — connect agents to Slack, X, Discord
Skills — reusable agent capabilities via a marketplace<p>CLI works like kubectl:
klaw create cluster mycompany
klaw create namespace marketing
klaw deploy agent.yaml<p>I also rewrote from Node.js to Go — agents went from 800MB+ to under 10MB each.<p>Quick usage example: I run a "content cluster" where each X account is its own namespace. Agent misbehaving on one account can't affect others. Adding a new account is klaw create namespace [account] + deploy the same config. 30 seconds.<p>The key differentiator vs frameworks like CrewAI or LangGraph: those define how agents collaborate on tasks. klaw operates one layer above — managing fleets of agents across teams with isolation and operational tooling. You could run CrewAI agents inside klaw namespaces.<p>Happy to answer questions.
Show HN: Klaw.sh – Kubernetes for AI agents
Hi everyone,<p>I run a generative AI infra company, unified API for 600+ models. Our team started deploying AI agents for our marketing and lead gen ops: content, engagement, analytics across multiple X accounts.<p>OpenClaw worked fine for single agents. But at ~14 agents across 6 accounts, the problem shifted from "how do I build agents" to "how do I manage them."<p>Deployment, monitoring, team isolation, figuring out which agent broke what at 3am. Classic orchestration problem.<p>So I built klaw, modeled on Kubernetes:
Clusters — isolated environments per org/project
Namespaces — team-level isolation (marketing, sales, support)
Channels — connect agents to Slack, X, Discord
Skills — reusable agent capabilities via a marketplace<p>CLI works like kubectl:
klaw create cluster mycompany
klaw create namespace marketing
klaw deploy agent.yaml<p>I also rewrote from Node.js to Go — agents went from 800MB+ to under 10MB each.<p>Quick usage example: I run a "content cluster" where each X account is its own namespace. Agent misbehaving on one account can't affect others. Adding a new account is klaw create namespace [account] + deploy the same config. 30 seconds.<p>The key differentiator vs frameworks like CrewAI or LangGraph: those define how agents collaborate on tasks. klaw operates one layer above — managing fleets of agents across teams with isolation and operational tooling. You could run CrewAI agents inside klaw namespaces.<p>Happy to answer questions.
Show HN: Klaw.sh – Kubernetes for AI agents
Hi everyone,<p>I run a generative AI infra company, unified API for 600+ models. Our team started deploying AI agents for our marketing and lead gen ops: content, engagement, analytics across multiple X accounts.<p>OpenClaw worked fine for single agents. But at ~14 agents across 6 accounts, the problem shifted from "how do I build agents" to "how do I manage them."<p>Deployment, monitoring, team isolation, figuring out which agent broke what at 3am. Classic orchestration problem.<p>So I built klaw, modeled on Kubernetes:
Clusters — isolated environments per org/project
Namespaces — team-level isolation (marketing, sales, support)
Channels — connect agents to Slack, X, Discord
Skills — reusable agent capabilities via a marketplace<p>CLI works like kubectl:
klaw create cluster mycompany
klaw create namespace marketing
klaw deploy agent.yaml<p>I also rewrote from Node.js to Go — agents went from 800MB+ to under 10MB each.<p>Quick usage example: I run a "content cluster" where each X account is its own namespace. Agent misbehaving on one account can't affect others. Adding a new account is klaw create namespace [account] + deploy the same config. 30 seconds.<p>The key differentiator vs frameworks like CrewAI or LangGraph: those define how agents collaborate on tasks. klaw operates one layer above — managing fleets of agents across teams with isolation and operational tooling. You could run CrewAI agents inside klaw namespaces.<p>Happy to answer questions.
Show HN: VOOG – Moog-style polyphonic synthesizer in Python with tkinter GUI
Body:
I built a polyphonic synthesizer in Python with a tkinter GUI styled after the Moog Subsequent 37.<p><pre><code> Features: 3 oscillators, Moog ladder filter (24dB/oct), dual ADSR envelopes, LFO, glide, noise generator, 4 multitimbral channels, 19 presets, rotary
knob GUI, virtual keyboard with mouse + QWERTY input, and MIDI support.
No external GUI frameworks — just tkinter, numpy, and sounddevice.</code></pre>