🛠️ All DevTools

[Other] Show HN: MDV – a Markdown superset for docs, dashboards, and slides with data

[Other] Migrating from DigitalOcean to Hetzner

[Other] Show HN: I can't write Python. It works anyway Read an article about analyzing Garmin data with AI. Sounded great — except I didn&#x27;t want to send my health data to any cloud service.<p>So I asked Claude to write me 2-3 scripts and a dashboard. This escalated a bit. 30 days and 20$ later I have this:<p>A local-first Garmin archive with interactive HTML dashboards, Excel exports, weather and pollen context, AES-256 encrypted token storage, and a self-healing data pipeline with 515 automated tests. Windows desktop app, no terminal needed. Nothing leaves your machine.<p>I never wrote a line of Python. I understood the problems and made the architectural decisions. Claude wrote everything else.<p>GitHub: github.com&#x2F;Wewoc&#x2F;Garmin_Local_Archive

[CLI Tool] Show HN: Sfsym – Export Apple SF Symbols as Vector SVG/PDF/PNG I found myself reaching for SF Symbols&#x27; &#x27;Copy Image As…&#x27; quite often during agentic design sessions, so I made a command-line tool that the agent can use by itself. It exports Apple SF Symbols as SVG, PDF, or PNG.<p>The vector paths come directly from macOS&#x27;s symbol renderer. Internally it reaches a private ivar on NSSymbolImageRep to get the CUINamedVectorGlyph, draws into a CGPDFContext, then walks the PDF content stream back out as SVG `d` commands. The output matches what the system draws, rather than an approximation traced from rasters.<p>A few things about it:<p>- Every subcommand accepts `--json`, and `sfsym schema` returns a machine-readable description of the whole CLI. - Symbol enumeration reads the OS&#x27;s Assets.car BOM tree, so the list of 8,300+ names stays current with macOS updates without a version table in the binary. - Each SVG `&lt;path&gt;` carries a `data-layer` attribute, so you can retheme in CSS without touching geometry.<p>It&#x27;s been saving me a bunch of clicking. Please let me know if you have any other ideas for it.

[Other] Show HN: Pyra – a Python toolchain experiment inspired by uv and Bun I’ve been working on Pyra for the past few months and wanted to start sharing it in public.<p>Right now it’s focused on the core package&#x2F;project management workflow: Python installs, init, add&#x2F;remove, lockfiles, env sync, and running commands in the managed env.<p>The bigger thing I’m exploring is whether Python could eventually support a more cohesive toolchain story overall, more in the direction of Bun: not just packaging, but maybe over time testing, tasks, notebooks, and other common workflow tools feeling like one system instead of a bunch of separate pieces.<p>It’s still early, and I’m definitely not claiming it’s as mature as uv. I’m mostly sharing it now because I want honest feedback on whether the direction feels interesting or misguided.

[Other] Show HN: Waputer – The WebAssembly Computer Waputer is an operating system that runs entirely in the browser. When you visit the website at <a href="https:&#x2F;&#x2F;waputer.app" rel="nofollow">https:&#x2F;&#x2F;waputer.app</a>, a kernel written in JavaScript sets up a filesystem and launches a WebAssembly program, which in turn talks to the kernel to handle the display and input. A purely terminal-based version is at <a href="https:&#x2F;&#x2F;waputer.dev" rel="nofollow">https:&#x2F;&#x2F;waputer.dev</a>.<p>My original intention was to create programs that run in the browser that have a lot more in common with the desktop. The traditional &quot;hello world&quot; program is not really suited for the web. Waputer changes that. The GitHub repo at <a href="https:&#x2F;&#x2F;github.com&#x2F;waputer&#x2F;docs" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;waputer&#x2F;docs</a> gives a very brief overview of compiling a C program and running it on Waputer. There is a blog available from the main site that has a long-form explanation of Waputer and my motivations if you want some additional reading.

[Other] Show HN: PanicLock – Close your MacBook lid disable TouchID –> password unlock I wrote this after the case of a Washington Post reporter, Hannah Natanson, was compelled to unlock her computer with her fingerprint. This resulted in access to her Desktop Signal on her computer, revealing sources and their conversations.<p><a href="https:&#x2F;&#x2F;www.yahoo.com&#x2F;news&#x2F;articles&#x2F;washington-post-raid-proves-face-153402560.html" rel="nofollow">https:&#x2F;&#x2F;www.yahoo.com&#x2F;news&#x2F;articles&#x2F;washington-post-raid-pro...</a><p>Edit: I&#x27;ve a lot more details about the legality and precedence on the apps landing page <a href="https:&#x2F;&#x2F;paniclock.github.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;paniclock.github.io&#x2F;</a>

[Database] Show HN: XitDB – an immutable single-file database I couldn&#x27;t find a database that was immutable (like Datomic) and embedded (like SQLite), so I made one. The reference impl is in Zig and there are now ports for Java, Clojure, TypeScript, and Go.

[Other] Build your own AI SRE agents. The open source toolkit for the AI era ✨

[Other] Show HN: Spice simulation → oscilloscope → verification with Claude Code I built MCP servers for my oscilloscope and SPICE simulator so Claude Code can close the loop between simulation and real hardware.

[CLI Tool] Android CLI: Build Android apps 3x faster using any agent

[Code Quality] Show HN: Stage – Putting humans back in control of code review Hey HN! We&#x27;re Charles and Dean, and we&#x27;re building Stage: a code review tool that guides you through reading a PR step by step, instead of piecing together a giant diff.<p>Here&#x27;s a demo video: <a href="https:&#x2F;&#x2F;www.tella.tv&#x2F;video&#x2F;stage-demo-1pph" rel="nofollow">https:&#x2F;&#x2F;www.tella.tv&#x2F;video&#x2F;stage-demo-1pph</a>. You can play around with some example PRs here: <a href="https:&#x2F;&#x2F;stagereview.app&#x2F;explore">https:&#x2F;&#x2F;stagereview.app&#x2F;explore</a>.<p>Teams are moving faster than ever with AI these days, but more and more engineers are merging changes that they don&#x27;t really understand. The bottleneck isn&#x27;t writing code anymore, it&#x27;s reviewing it.<p>We&#x27;re two engineers who got frustrated with GitHub&#x27;s UI for code review. As coding agents took off, we saw our PR backlog pile up faster than we could handle. Not only that, the PRs themselves were getting larger and harder to understand, and we found ourselves spending most of our time trying to build a mental model of what a PR was actually doing.<p>We built Stage to make reviewing a PR feel more like reading chapters of a book, not an unorganized set of paragraphs. We use it every day now, not just to review each other&#x27;s code but also our own, and at this point we can&#x27;t really imagine going back to the old GitHub UI.<p>What Stage does: when a PR is opened, Stage groups the changes into small, logical &quot;chapters&quot;. These chapters get ordered in the way that makes most sense to read. For each chapter, Stage tells you what changed and specific things to double check. Once you review all the chapters, you&#x27;re done reviewing the PR.<p>You can sign in to Stage with your GitHub account and everything is synced seamlessly (commenting, approving etc.) so it fits into the workflows you&#x27;re already used to.<p>What we&#x27;re not building: a code review bot like CodeRabbit or Greptile. These tools are great for catching bugs (and we use them ourselves!) but at the end of the day humans are responsible for what gets shipped. It&#x27;s clear that reviewing code hasn&#x27;t scaled the same way that writing did, and they (we!) need better tooling to keep up with the onslaught of AI generated code, which is only going to grow.<p>We&#x27;ve had a lot of fun building this and are excited to take it further. If you&#x27;re like us and are also tired of using GitHub for reviewing PRs, we&#x27;d love for you to try it out and tell us what you think!

[Other] Codex for almost everything

[Other] Show HN: Marky – A lightweight Markdown viewer for agentic coding Hey HN,<p>In this age of agentic coding I&#x27;ve found myself spending a lot of time reviewing markdown files. Whether it&#x27;s plans or documentation that I&#x27;ve asked my agent to generate for me, it seems that I spend more time reading markdown than code.<p>I&#x27;ve tried a few different solutions to make it easier to read such as Obsidian however I&#x27;ve found their Vault system to be quite limiting for this use case and I&#x27;ve found TUI solutions to not quite be as friendly to read as I&#x27;ve wanted so I made Marky.<p>Marky is a lightweight desktop application that makes it incredibly easy to read and track your markdown files. It also has a helpful cli so you can just run marky FILENAME and have the app open to the md file that you pointed it at. I&#x27;ve been using the daily over the past week and I really enjoy it so I figured I&#x27;d share it.<p>Here&#x27;s a video if you want to check out a demo: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=nGBxt8uOVjc" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=nGBxt8uOVjc</a>.<p>I have plans to add more features such as incorporating agentic tools such as claude code and codex into the UI as well as developing a local git diff reviewer to allow me to do local code review before pushing up to git.<p>I&#x27;d love to hear your thoughts and any feature suggestions you may have :)

[Other] Claude Code skill to support Android app's reverse engineering

[API/SDK] Launch HN: Kampala (YC W26) – Reverse-Engineer Apps into APIs Hey! I am Alex and together with my co-founder Tarun built Kampala (<a href="https:&#x2F;&#x2F;www.zatanna.ai&#x2F;kampala">https:&#x2F;&#x2F;www.zatanna.ai&#x2F;kampala</a>). It’s a man-in-the-middle (MITM) style proxy that allows you to agentically reverse engineer existing workflows without brittle browser automation or computer use agents. It works for websites, mobile apps, desktop apps.<p>Demo: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=z_PeostC-b4" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=z_PeostC-b4</a>. Many people spend hours per day in legacy dashboards and on-prem solutions reconciling data across platforms. Current attempts at automation use browser automations or computer use agents which are brittle, slow, and nondeterministic. I come from a web reverse engineering background and spent the last 7-8 years building integrations by hand for sneaker&#x2F;ticket releases, sportsbooks logins, and everything in\ between. During that time I consulted for several companies and brought them off of browser based infrastructure into the requests layer.<p>When we started Zatanna (that’s our company name) we worked in dental tech, which meant we had to deal with tons of insurance payer dashboards and legacy dental-practice solutions. Our superpower (as a fairly undifferentiated voice agent&#x2F;front desk assistant company) was that we could integrate with nearly any system requested. During this time we built extensive tooling (including what we’re now calling Kampala) to allow us to spin up these integrations quickly. Existing MITM proxies and tooling didn’t work for a few reasons: (1) They manipulated the TLS and HTTP2 fingerprint over the wire which was detected by strict anti-bots. (2) They had bad MCPs which did not adequately expose necessary features like scripts&#x2F;replay. (3) They did not allow for building workflows or actions given a sample or sequence of requests.<p>As the tools we built got more powerful, we began to use them internally to scrape conference attendees, connect to external PMS systems, and interact with slack apps. I even sent it to my property manager mom, who (with a lot of help from me lol), automated 2-3 hours of billing information entry in Yardi. At that point we realized that this wasn’t really about dentistry :)<p>Because Kampala is a MITM, it is able to leverage existing session tokens&#x2F;anti-bot cookies and automate things deterministically in seconds. You can either use our agent harness that directly creates scripts&#x2F;apis by prompting you with what actions to make, or our MCP by manually doing a workflow once, and asking your preferred coding agent to use Kampala to make a script&#x2F;API to replicate it. Once you have an API&#x2F;script, you can export, run, or even have us host it for you.<p>We think the future of automation does not consist of sending screenshots of webpages to LLMs, but instead using the layer below that computers actually understand. Excited to hear your thoughts&#x2F;questions&#x2F;feedback!

[Other] The Unix Executable as a Smalltalk Method [video]

[Other] Qwen3.6-35B-A3B: Agentic coding power, now open to all

[Other] Artifacts: Versioned storage that speaks Git

[Other] €54k spike in 13h from unrestricted Firebase browser key accessing Gemini APIs