🛠️ All DevTools

[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] 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] 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

[Monitoring/Observability] Moving a large-scale metrics pipeline from StatsD to OpenTelemetry / Prometheus Full disclosure - I formerly worked for Grafana Labs.<p>The size of this Grafana Mimir deployment would rank it in the top echelon of customers. The irony is that this may be a $0 revenue user for Grafana Labs.

[API/SDK] Tailscale-rs: Official Rust library for embedding Tailscale

[DevOps] Show HN: Hiraeth – AWS Emulator With the recent changes around Localstack pricing&#x2F;licensing I&#x27;ve been hunting for alternatives. I decided that it might be a fun experiment to try rolling my own. SQS is a service I use heavily so I chose that as the first service to implement. I have more services planned and in development.<p>A few things I think are cool:<p>4MB Docker Image Size<p>Instant Startup<p>AWS Sigv4 Authentication<p>A little admin UI that can be helpful for development&#x2F;troubleshooting<p>Most of the SQS API implemented, the rest will soon follow :)

[Other] Keycard – inject API keys into subprocesses, never touch shell env

[IDE/Editor] Agent - Native Mac OS X coding ide/harness

[CLI Tool] I made a terminal pager

[CLI Tool] Hacker News CLI

[Other] Show HN: Omi – watches your screen, hears conversations, tells you what to do Spent 4 months and built Omi for Desktop, your life architect: It sees your screen, hears your conversations and will advise you on what to do next<p>Basically Cluely + Rewind + Granola + Wisprflow + ChatGPT + Claude in one app<p>I talk to claude&#x2F;chatgpt 24&#x2F;7 but I find it frustrating that i have to capture&#x2F;send screenshots of my screen and that it doesn&#x27;t help proactively during my work<p>Whenever omi sees something wrong about my workflow, it will send me a proactive notification with advice. It will also point to something I&#x27;m missing.<p>The hardest part was to nail proactivity - after trying 20+ similar tools I didn&#x27;t find a single one with smart proactive notifications based on content on your screen. I made it look at your screen every second with 4 main prompts:<p>1. Is the user productive or distracted?<p>2. Is there anything useful to say right now?<p>3. is there any task to add to do later?<p>4. is there anything important to remember about the user?<p>Full stack: - Swift - Rust backend - Deepgram transcription - Claude code for messaging - GPT 5.4 summaries - Gemini for embeddings and translation<p>Open source, stores screenshots locally, uses Claude Code for chat. Has cloud to sync with hardware or mobile app but can be disabled in settings

[Package Manager] Show HN: Dependicus, a dashboard for your monorepo's dependencies Late last year, I was digging into some dependency-related tech debt, and struggling with how long it takes to run pnpm&#x27;s introspection commands like &#x27;pnpm why&#x27; in a medium-size monorepo. So I started working on a simple static site generator that would let me view the output of these expensive commands all at once, to make problems clearly visible instead of requiring deep exploration one at a time.<p>Once I had that working, I realized I had enough data to add ticket tracking. It uses the data it gathers from the package manager to keep Linear or GitHub issues updated. And by auto-assigning those issues to coding agents, I get a Dependabot-but-better experience: agents keep up with API updates in addition to just bumping versions, and group related updates automatically.<p>It&#x27;s still early days, but it&#x27;s working really well for us and I think people will find value in it, so I&#x27;m sharing here!

[CLI Tool] Show HN: Libretto – Making AI browser automations deterministic Libretto (<a href="https:&#x2F;&#x2F;libretto.sh" rel="nofollow">https:&#x2F;&#x2F;libretto.sh</a>) is a Skill+CLI that makes it easy for your coding agent to generate deterministic browser automations and debug existing ones. Key shift is going from “give an agent a prompt at runtime and hope it figures things out” to: “Use coding agents to generate real scripts you can inspect, run, and debug”.<p>Here’s a demo: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=0cDpIntmHAM" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=0cDpIntmHAM</a>. Docs start at <a href="https:&#x2F;&#x2F;libretto.sh&#x2F;docs&#x2F;get-started&#x2F;introduction" rel="nofollow">https:&#x2F;&#x2F;libretto.sh&#x2F;docs&#x2F;get-started&#x2F;introduction</a>.<p>We spent a year building and maintaining browser automations for EHR and payer portal integrations at our healthcare startup. Building these automations and debugging failed ones was incredibly time-consuming.<p>There’s lots of tools that use runtime AI like Browseruse and Stagehand which we tried, but (1) they’re reliant on custom DOM parsing that&#x27;s unreliable on older and complicated websites (including all of healthcare). Using a website’s internal network calls is faster and more reliable when possible. (2) They can be expensive since they rely on lots of AI calls and for workflows with complicated logic you can’t always rely on caching actions to make sure it will work. (3) They’re at runtime so it’s not interpretable what the agent is going to do. You kind of hope you prompted it correctly to do the right thing, but legacy workflows are often unintuitive and inconsistent across sites so you can’t trust an agent to just figure it out at runtime. (4) They don’t really help you generate new automations or help you debug automation failures.<p>We wanted a way to reliably generate and maintain browser automations in messy, high-stakes environments, without relying on fragile runtime agents.<p>Libretto is different because instead of runtime agents it uses “development-time AI”: scripts are generated ahead of time as actual code you can read and control, not opaque agent behavior at runtime. Instead of a black box, you own the code and can inspect, modify, version, and debug everything.<p>Rather than relying on runtime DOM parsing, Libretto takes a hybrid approach combining Playwright UI automation with direct network&#x2F;API requests within the browser session for better reliability and bot detection evasion.<p>It records manual user actions to help agents generate and update scripts, supports step-through debugging, has an optional read-only mode to prevent agents from accidentally submitting or modifying data, and generates code that follows all the abstractions and conventions you have already in your coding repo.<p>Would love to hear how others are building and maintaining browser automations in practice, and any feedback on the approach we’ve taken here.

[Other] Show HN: MCP server gives your agent a budget (save tokens, get smarter results) As a consultant I foot my own Cursor bills, and last month was $1,263. Opus is too good not to use, but there&#x27;s no way to cap spending per session. After blowing through my Ultra limit, I realized how token-hungry Cursor + Opus really is. It spins up sub-agents, balloons the context window, and suddenly, a task I expected to cost $2 comes back at $8. My bill kept going up, but was I really going to switch to a worse model?<p>No. So I built l6e: an MCP server that gives your agent the ability to budget. It works with Cursor, Claude Code, Windsurf, Openclaw, and every MCP-compatible application.<p>Saving money was why I built it, but what surprised me was that the process of budgeting changed the agent&#x27;s behavior. An agent that understands the limitations of the resources doesn&#x27;t try to speculatively increase the context window with extra files. It doesn&#x27;t try to reach every possible API. The agent plans ahead, sticks to it, and ends work when it should.<p>It works, and we&#x27;ve been dogfooding it hard. After v1 shipped, the rest of l6e was all built with it. We launched the entire docs site using frontier models for $0.99. The kicker was every time l6e broke in development, I could feel the pain. The agent got sloppy, burned through context, and output quality dropped right along with it.<p>Install: pip install l6e-mcp<p>Docs: <a href="https:&#x2F;&#x2F;docs.l6e.ai" rel="nofollow">https:&#x2F;&#x2F;docs.l6e.ai</a><p>GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;l6e-ai&#x2F;l6e-mcp" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;l6e-ai&#x2F;l6e-mcp</a><p>Website: <a href="https:&#x2F;&#x2F;l6e.ai" rel="nofollow">https:&#x2F;&#x2F;l6e.ai</a><p>Happy to answer questions about the system design, calibration models, or why I can&#x27;t go back to coding without it.