🛠️ Hacker News Tools

[Other] Show HN: Turn Markdown into React/Svelte/Vue UI at runtime, zero build step

[Other] Gonzo: A Go-based TUI for log analysis (OpenTelemetry/OTLP support)

[Other] Google to require developer verification to install and sideload Android apps

[Other] Show HN: Stagewise – frontend coding agent for real codebases Hey HN, we&#x27;re Glenn and Julian, and we&#x27;re building stagewise (<a href="https:&#x2F;&#x2F;stagewise.io">https:&#x2F;&#x2F;stagewise.io</a>), a frontend coding agent that inside your app’s dev mode and that makes changes in your local codebase.<p>We’re compatible with any framework and any component library. Think of it like a v0 of Lovable that works locally and with any existing codebase.<p>You can spawn the agent into locally running web apps in dev mode with `npx stagewise` from the project root. The agent lets you then click on HTML Elements in your app, enter prompts like &#x27;increase the height here&#x27; and will implement the changes in your source code.<p>Before stagewise, we were building a vertical SaaS for logistics from scratch and loved using prototyping tools like v0 or lovable to get to the first version. But when switching from v0&#x2F; lovable to Cursor for local development, we felt like the frontend magic was gone. So, we decided to build stagewise to bring that same magic to local development.<p>The first version of stagewise just forwarded a prompt with browser context to existing IDEs and agents (Cursor, Cline, ..) and went viral on X after we open sourced it. However, the APIs of existing coding agents were very limiting, so we figured that building our own agent would unlock the full potential of stagewise.<p>Since our last Show HN (<a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=44798553">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=44798553</a>), we launched a few very important features and changes: You now have a proprietary chat history with the agent, an undo button to revert changes, and we increased the amount of free credits AND reduced the pricing by 50%. We made a video about all these changes, showing you how stagewise works: <a href="https:&#x2F;&#x2F;x.com&#x2F;goetzejulian&#x2F;status&#x2F;1959835222712955140&#x2F;video&#x2F;1" rel="nofollow">https:&#x2F;&#x2F;x.com&#x2F;goetzejulian&#x2F;status&#x2F;1959835222712955140&#x2F;video&#x2F;...</a>.<p>So far, we&#x27;ve seen great adoption from non-technical users who wanted to continue building their lovable prototype locally. We personally use the agent almost daily to make changes to our landing page and to build the UI of new features on our console (<a href="https:&#x2F;&#x2F;console.stagewise.io">https:&#x2F;&#x2F;console.stagewise.io</a>).<p>If you have an app running in dev mode, simply `cd` into the app directory and run `npx stagewise` - the agent should appear, ready to play with.<p>We&#x27;re very excited to hear your feedback!

[Other] Show HN: SecretMemoryLocker – File Encryption Without Static Passwords I built SecretMemoryLocker (<a href="https:&#x2F;&#x2F;secretmemorylocker.com" rel="nofollow">https:&#x2F;&#x2F;secretmemorylocker.com</a>), a file encryption tool that generates keys dynamically from your answers to personal questions instead of using a static master password. This makes offline brute-force attacks much more difficult. Think of it as a password manager that meets mnemonic seed recovery, but without storing any sensitive keys on disk.<p>Why? I kept losing master passwords and wanted a solution that wasn&#x27;t tied to a single point of failure. I also wanted to create a &quot;digital legacy&quot; that my family could access only under specific conditions. The core principle is knowledge-based encryption: the key only exists in memory when you provide the correct answers.<p>Status: * MVP is ready for Windows (.exe). * Linux and macOS support is planned. * UI is available in English, Spanish, and Ukrainian.<p>Key Features:<p>* No Static Secrets: No master password or seed phrase is ever stored. The key is reconstructed on the fly.<p>* Knowledge-Based Key Generation: The final encryption key is derived from a combination of your personal answers and file metadata.<p>* Offline Brute-Force Resistance: Uses MirageLoop, a decoy system that activates when incorrect answers are entered. Instead of decrypting real data, it generates an endless sequence of AI-created questions from a secure local database, creating an illusion of progress while keeping your real data untouched.<p>* Offline AI Generation Mode: Optional offline Q&amp;A generator (prototype).<p>How It Works (Simplified):<p>1) Files are packed into an AES-256 encrypted ZIP archive.<p>2) A JSON key file stores the questions in an encrypted chain. Each subsequent question is encrypted with a key derived from the previous correct answer and the file&#x27;s hash. This forces you to answer them sequentially.<p>3) The final encryption key for the ZIP file is derived by combining the hashes of all your correct answers. The key derivation formula looks like this:<p><pre><code> K_final = SHA256(H(answer1+file_hash) + H(answer2+file_hash) + ...) </code></pre> (Note: We are aware that a fast hash like SHA256 is not ideal for a KDF. We plan to migrate to Argon2 in a future release to further strengthen resistance against brute-force attacks.)<p>To encrypt, you provide a file. This creates two outputs: your_file.txt → your_file_SMLkey.json + your_file_SecretML.zip<p>To decrypt, you need both files and the correct answers.<p>Install &amp; Quick Start: Download the EXE from GitHub Releases (no dependencies needed):<p><a href="https:&#x2F;&#x2F;github.com&#x2F;SecretML&#x2F;SecretMemoryLocker&#x2F;releases" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;SecretML&#x2F;SecretMemoryLocker&#x2F;releases</a><p>Encrypt:<p><pre><code> SecretMemoryLocker.exe --encrypt &quot;C:\docs\important.pdf&quot; </code></pre> Decrypt:<p><pre><code> SecretMemoryLocker.exe --decrypt &quot;C:\docs\important_SMLkey.json&quot; </code></pre> I would love to get your feedback on the concept, the user experience, and any security assumptions I&#x27;ve made. Thanks!

[Database] Show HN: Base, an SQLite database editor for macOS I recently released v3 of Base, my SQLite editor for macOS.<p>The goal of this app is to provide a comfortable native GUI for SQLite, without it turning into a massive IDE-style app.<p>The coolest features are<p>- That it can handle full altering of tables, which is quite finicky to do manually with SQLite.<p>- It has a more detailed display of column constraints than most editors. Each constraint is shown as an icon if active, with full details available on clicking the icon.<p>This update also adds support for attaching databases, which is a bit fiddly with macOS sandboxing.<p>I&#x27;d love to hear any feedback or answer any questions.

[Other] Show HN: Async – Claude Code and Linear and GitHub PRs in One Opinionated Tool Hi, I’m Mikkel and I’m building Async, an open-sourced developer tool that combines AI coding with task management and code review.<p>What Async does:<p><pre><code> - Automatically researches coding tasks, asks clarifying questions, then executes code changes in the cloud - Breaks work into reviewable subtasks with stack diffs for easier code review - Handles the full workflow from issue to merged PR without leaving the app </code></pre> Demo here: <a href="https:&#x2F;&#x2F;youtu.be&#x2F;98k42b8GF4s?si=Azf3FIWAbpsXxk3_" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;98k42b8GF4s?si=Azf3FIWAbpsXxk3_</a><p>I’ve been working as a developer for over a decade now. I’ve tried all sorts of AI tools out there including Cline, Cursor, Claude Code, Kiro and more. All are pretty amazing for bootstrapping new projects. But most of my work is iterating on existing codebases where I can&#x27;t break things, and that&#x27;s where the magic breaks down. None of these tools work well on mature codebases.<p>The problems I kept running into:<p><pre><code> - I&#x27;m lazy. My Claude Code workflow became: throw a vague prompt like &quot;turn issues into tasks in Github webhook,&quot; let it run something wrong, then iterate until I realize I could&#x27;ve just coded it myself. Claude Code&#x27;s docs say to plan first, but it&#x27;s not enforced and I can&#x27;t force myself to do it. - Context switching hell. I started using Claude Code asynchronously - give it edit permissions, let it run, alt-tab to work on something else, then come back later to review. But when I return, I need to reconcile what the task was about, context switch back, and iterate. The mental overhead kills any productivity gains. - Tracking sucks. I use Apple Notes with bullet points to track tasks, but it&#x27;s messy. Just like many other developers, I hate PM tools but need some way to stay organized without the bloat. - Review bottleneck. I&#x27;ve never shipped Claude Code output without fixes, at minimum stylistic changes (why does it always add comments even when I tell it not to?). The review&#x2F;test cycle caps me at maybe 3 concurrent tasks. </code></pre> So I built Async:<p><pre><code> - Forces upfront planning, always asks clarifying questions and requires confirmation before executing - Simple task tracking that imports Github issues automatically (other integration coming soon!) - Executes in the cloud, breaks work into subtasks, creates commits, opens PRs - Built-in code review with stacked diffs - comment and iterate without leaving the app - Works on desktop and mobile </code></pre> It works by using a lightweight research agent to scope out tasks and come up with requirements and clarifying questions as needed (e.g., &quot;fix the truncation issue&quot; - &quot;Would you like a tooltip on hover?&quot;). After you confirm requirements, it executes the task by breaking it down into subtasks and then working commit by commit. It uses a mix of Gemini and Claude Code internally and runs all changes in the background in the cloud.<p>You&#x27;ve probably seen tools that do pieces of this, but I think it makes sense as one integrated workflow.<p>This isn&#x27;t for vibe coders. I&#x27;m building a tool that I can use in my day-to-day work. Async is for experienced developers who know their codebases and products deeply. The goal is to make Async the last tool developers need to build something great. Still early and I&#x27;m iterating quickly. Would love to know what you think.<p>P.S. My cofounder loves light mode, I only use dark mode. I won the argument so our tool only supports dark mode. Thumbs up if you agree with me.

[Other] Show HN: Diggit.dev – Git history for architecture archaeologists Hello friends,<p>Today I&#x27;m sharing a little tool to help you explore GitHub repositories:<p>• <a href="https:&#x2F;&#x2F;diggit.dev" rel="nofollow">https:&#x2F;&#x2F;diggit.dev</a><p>This project was admittedly a big dumb excuse to play with Elm and Claude Code. I published my design notes and all the chat transcripts here:<p>• <a href="https:&#x2F;&#x2F;taylor.town&#x2F;diggit-000" rel="nofollow">https:&#x2F;&#x2F;taylor.town&#x2F;diggit-000</a><p>Please add bug reports and feature requests to the repo:<p>• <a href="https:&#x2F;&#x2F;github.com&#x2F;surprisetalk&#x2F;diggit" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;surprisetalk&#x2F;diggit</a><p>Enjoy!

[Other] Make any site multiplayer in a few lines. Serverless WebRTC matchmaking

[Other] About Containers and VMs

[Other] Git-Annex

[Other] Show HN: Sping – An HTTP/TCP latency tool that's easy on the eye I&#x27;ve frequently found myself using [nvitop](<a href="https:&#x2F;&#x2F;github.com&#x2F;XuehaiPan&#x2F;nvitop" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;XuehaiPan&#x2F;nvitop</a>) to diagnose GPU&#x2F;CPU contention issues.<p>The two best things about it are:<p>- It&#x27;s easy to install if I can access pip in the container<p>- It makes a compelling screenshot (which helps me communicate with coworkers.)<p>With those two lessons in mind: Here is Sping!<p>Purpose: Help observe and diagnose latency issues at layer 4+ (TCP&#x2F;HTTP&#x2F;HTTPS)<p>Two good things about it:<p>- It&#x27;s easy to install if you have pip. (Available at [service-ping-sping](<a href="https:&#x2F;&#x2F;pypi.org&#x2F;project&#x2F;service-ping-sping&#x2F;" rel="nofollow">https:&#x2F;&#x2F;pypi.org&#x2F;project&#x2F;service-ping-sping&#x2F;</a>) on PyPi)<p>- It makes a compelling screenshot.<p>Not sure if this is the kind of thing that anyone else would be interested in. But I&#x27;ve enjoyed making it and intend to keep using it.

[API/SDK] Show HN: FilterQL – A tiny query language for filtering structured data Hey all, I just released v2.0.0 of FilterQL, a query language and TypeScript library. This version adds support for Operations, which allow you to transform the data after filtering.<p>If you think this would be useful in a project you&#x27;re working on, give it a try and let me know what you think!

[Other] Show HN: I Built a XSLT Blog Framework A few weeks ago a friend sent me grug-brain XSLT (1) which inspired me to redo my personal blog in XSLT.<p>Rather than just build my own blog on it, I wrote it up for others to use and I&#x27;ve published it on GitHub <a href="https:&#x2F;&#x2F;github.com&#x2F;vgr-land&#x2F;vgr-xslt-blog-framework" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;vgr-land&#x2F;vgr-xslt-blog-framework</a> (2)<p>Since others have XSLT on the mind, now seems just as good of a time as any to share it with the world. Evidlo@ did a fine job explaining the &quot;how&quot; xslt works (3)<p>The short version on how to publish using this framework is:<p>1. Create a new post in HTML wrapped in the XML headers and footers the framework expects.<p>2. Tag the post so that its unique and the framework can find it on build<p>3. Add the post to the posts.xml file<p>And that&#x27;s it. No build system to update menus, no RSS file to update (posts.xml is the rss file). As a reusable framework, there are likely bugs lurking in CSS, but otherwise I&#x27;m finding it perfectly usable for my needs.<p>Finally, it&#x27;d be a shame if XSLT is removed from the HTML spec (4), I&#x27;ve found it quite eloquent in its simplicity.<p>(1) <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=44393817">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=44393817</a><p>(2) <a href="https:&#x2F;&#x2F;github.com&#x2F;vgr-land&#x2F;vgr-xslt-blog-framework" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;vgr-land&#x2F;vgr-xslt-blog-framework</a><p>(3) <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=44988271">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=44988271</a><p>(4) <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=44952185">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=44952185</a><p>(Aside - First time caller long time listener to hn, thanks!)

[Other] Dynamically patch a Python function's source code at runtime

[Other] Show HN: Clearcam – Add AI object detection to your IP CCTV cameras This runs YOLOv8 + bytetrack with Tinygrad detections (depending on user config) are saved and can be sent to the companion iOS app along with a notification, all video processing is done locally, all footage is encrypted before leaving your computer, and the sending notifications + videos part is optional. This uses tinygrad, so it runs well on my apple silicon macs and should be able to run on a lot of hardware (or will be able to when I remove other deps).

[Other] Show HN: Publish Markdown – A tool to publish Markdown file in one click Hi everyone!<p>I built this tool because I couldn&#x27;t find a simpler solution to my problem (publish a markdown file and make it available online so other people can see). I hope you&#x27;ll find it useful too!<p>Currently, what it does is only publish a markdown file, but I&#x27;m thinking of adding features like styling, custom URL, password-protected link, etc.<p>But I don&#x27;t know whether people would find it useful.<p>Let me know what you think!

[CLI Tool] Show HN: brew-cleaner – CLI to bulk uninstall Homebrew formulae and free space

[Other] Bypass PostgreSQL catalog overhead with direct partition hash calculations

[Other] Show HN: AgentState – Lightweight state manager for multi-agent AI workflows AgentState to solve a problem I kept running into: managing state for multi-agent AI systems is surprisingly hard. When you have multiple AI agents that need to coordinate, persist their state, and query each other&#x27;s status, you typically end up with a mess of Redis&#x2F;Postgres setups, custom queuing, and manual synchronization code.<p>The whole thing is ~3MB, written in Rust for performance and safety, runs in Docker, and handles 1000+ ops&#x2F;sec. I&#x27;ve been running it in production for AI workflows and it&#x27;s been rock solid.