🛠️ Hacker News Tools

[Other] Show HN: Building a web server in assembly to give my life (a lack of) meaning This is ymawky, a static file web server for MacOS written entirely in ARM64 assembly. It supports GET, PUT, DELETE, HEAD, and OPTIONS requests, and supports Range: bytes=X-Y headers (which allows scrubbing for video streaming). It decodes percent-encoded URLs, strictly enforces docroot, serves custom error pages for any HTTP error response, supports directory listing, and has (some) mitigations against slowloris-like attacks.<p>I’ve also written a more detailed writeup here: <a href="https:&#x2F;&#x2F;imtomt.github.io&#x2F;ymawky&#x2F;" rel="nofollow">https:&#x2F;&#x2F;imtomt.github.io&#x2F;ymawky&#x2F;</a>

[CLI Tool] Show HN: Remind – schedule Claude Code on your Mac Claude Code can&#x27;t schedule itself locally on your Mac, so I made Remind. Just add a reminder to the &quot;Remind&quot; list in Reminders with a due time and your prompt as the notes. Remind fires up your terminal at the due time and runs `claude` with the prompt. It writes the results right back into the Reminder.<p>Some cool things:<p>- The &quot;Remind&quot; list lives with your other Reminders, so adding from your phone or watch (or another Mac) just works.<p>- Frontmatter in the Reminder lets it continue an existing Claude session. A Stop hook captures the session id, so the next time it runs it can pick up where the last left off.<p>It&#x27;s free, updates itself with Sparkle, and requires that you have `claude` on your $PATH running on macOS 15+.<p>Remind has become sticky in my personal workflow so I thought I&#x27;d share it here. Let me know if you have any suggestions or questions.

[Other] Show HN: I made a Clojure-like language in Go, boots in 7ms Let-go is a Clojure-like language (~90% compatible with JVM Clojure) written in pure Go. It ships as a ~10MB static binary and cold boots in ~7ms - that&#x27;s about 50x faster than JVM and 3x faster than Babashka. It has decent throughput on algorithmic workloads - within ballpark of the GraalVM-backed sci.<p>I started this project in 2021 as an elaborate practical joke: I wanted to have an excuse for writing Clojure while pretending to write Go.<p>Jokes aside, it turned out to be pretty decent: it feels like real Clojure, it has an nREPL server (supported in Calva, CIDER, etc.), it&#x27;s easily embeddable in your Go programs (funcs, structs and channels cross the boundary without fuss). It&#x27;s good for writing CLIs, web servers, data processing scripts and even doing some systems programming - I used it to write a deamonless container runtime. Oh, and it runs on Plan9.<p>Under the hood there is a fairly simple compiler and a stack VM, both handcrafted specifically for running Clojure-like code. The compiler can work in AOT mode producing portable bytecode blobs and standalone binaries (runtime+bytecode).<p>This is not a drop-in replacement for Clojure in general - it does not load JARs, it does not have all Java APIs and it most probably won&#x27;t run your exiting Clojure projects without modifications. At least not at the moment.<p>Take it for a spin, tell me what you think. Issues and PRs are welcome!

[IDE/Editor] Zed Editor Theme-Builder

[Other] Docker images are hundreds of MB; a full game engine compiles to 35MB WASM

[Other] Show HN: JSLike, a CSP-Safe Interpreter for JS, TS, JSX, TSX in JS

[Other] Show HN: Chuchu, an Android SSH client built on libghostty

[Other] Rtwatch: Watch videos with friends using WebRTC

[Other] Show HN: Mochi.js: bun-native high-fidelity browser automation library Hi HN,<p>I’m sharing mochi.js (<a href="https:&#x2F;&#x2F;github.com&#x2F;0xchasercat&#x2F;mochi" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;0xchasercat&#x2F;mochi</a>), a Bun-native, raw-CDP browser automation framework. It&#x27;s designed to make programmatic browser use more effective by focusing on consistency and measured parity with regular traffic, purely from the JS layer, against stock Chromium.<p>The most common forms of browser automation focus heavily on client-side line by line probes, which are mostly cosmetic. This makes people feel better but it doesn&#x27;t have much relevance to actual WAF or anti-automation defences.<p>Mochi.js focuses on what actually matters, allowing you to get past captchas, WAF&#x27;s and most defence mechanisms. In fact, in some cases it actually outperforms chromium forks simply by virtue of not having to lie.<p>The foundation is built on a probe manifest based on analyzing several WAF&#x27;s and trying to cover most of the ground that matters, and from there building upwards while ensuring every decision is backed by data. Solves turnstile&#x2F;interstitial automatically, single digit fpjs suspect score, very good client-side results, though browserscan and a few others are known limitations that are fundamentally conflicting with what WAF&#x27;s probe for.<p>I&#x27;ll be here if anyone wants to discuss the details, check out the docs and github. It&#x27;s completely free and open source, MIT, strictly no relationship to any proprietary products whatsoever. No affiliation to patched chromium forks, or SaaS.<p>But I also want to talk about why I built this, because the current paradigm of &quot;bot detection&quot; is fundamentally broken.<p>Traditionally they would probably try to label my repository a malicious tool, or at best, a grey hat one.<p>Let&#x27;s take Turnstile for example, If you attach a debugger to see what data they are extracting from your hardware, their script intentionally self-destructs. When they try to extract your data—acting as a guest on your silicon, using your electricity, without asking, the industry calls it &quot;Security.&quot;<p>But if you write a script to control exactly what data your own hardware emits, refusing to provide the data they have no right to ask for, you are suddenly labeled a &quot;Malicious Actor&quot; engaged in &quot;Bot Evasion.&quot;<p>I find it absurd we let ourselves put up with this, and the stance of the bot-evasion community only makes them feel more able to take a higher moral ground.<p>I have built a library that respects my hardware&#x27;s reality. If that breaks your security model, that&#x27;s because your security model relies on trespassing and secrecy. I stopped apologizing. Who&#x27;s next?<p>Mochi is the exact opposite of WAF opacity. It is a glass box. It is MIT-licensed. The entire DAG, fingerprint manifest schema, harvesting process, is documented. We even commit our live benchmarks to the public record (mochi on a Linux datacenter IP scored a suspect_score: 8 and bot: not_detected against FingerprintJS Pro v4).<p>We don&#x27;t even lie unnecessarily. We default to host-OS matching. If you run mochi on a Linux server, it uses privacy-sensible fingerprints for Linux, not Windows, because Linux is a real-user signal. It proves that WAFs aren&#x27;t actually blocking what most people think they are, which begs the question of what they are really doing in that obfuscated payload.<p>The legitimacy argument is exactly how they captured the narrative. And nobody challenged it because the people on the other side were too busy acting like they were doing something wrong.<p>Is this a conspiracy theory? For sure, but only because they allow it to be. Try make a conspiracy theory about the sticky riceball.

[Other] A History of IDEs at Google

[Other] Bun's experimental Rust rewrite hits 99.8% test compatibility on Linux x64 glibc <a href="https:&#x2F;&#x2F;xunroll.com&#x2F;thread&#x2F;2053047748191232310" rel="nofollow">https:&#x2F;&#x2F;xunroll.com&#x2F;thread&#x2F;2053047748191232310</a><p>Recent and related: <i>Zig → Rust porting guide</i> - <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=48016880">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=48016880</a> - May 2026 (540 comments)

[Other] Killswitch: Per-function short-circuit mitigation primitive

[Other] All my clients wanted a carousel, now it's an AI chatbot

[Other] Using Claude Code: The unreasonable effectiveness of HTML Examples: <a href="https:&#x2F;&#x2F;thariqs.github.io&#x2F;html-effectiveness&#x2F;" rel="nofollow">https:&#x2F;&#x2F;thariqs.github.io&#x2F;html-effectiveness&#x2F;</a><p>Related: <a href="https:&#x2F;&#x2F;simonwillison.net&#x2F;2026&#x2F;May&#x2F;8&#x2F;unreasonable-effectiveness-of-html&#x2F;" rel="nofollow">https:&#x2F;&#x2F;simonwillison.net&#x2F;2026&#x2F;May&#x2F;8&#x2F;unreasonable-effectiven...</a>

[Other] Show HN: Ant – A from-scratch JavaScript runtime in 9 MB Hey HN! I have been working on Ant for a while now, would love to share around now.<p>What is Ant? It&#x27;s my JavaScript runtime, built from scratch over many hours of work. Much effort has gone into keeping the binary size small, around 9MB at the moment (6.5 MB with -Os). On my M4 Pro, the hono coldstart bench (examples&#x2F;npm&#x2F;hono&#x2F;bench-coldstart.js) lands around 5ms, about 2.4x faster than bun, and 5.8x faster than node.<p>To keep things small, the engine (&quot;Ant Silver&quot;) is hand-written, not a wrapper around V8&#x2F;JSC&#x2F;SpiderMonkey. The JIT is still a work in progress but it uses a fork of MIR as the backend.<p>Ant currently targets the WinterTC Minimum Common API, while also passing 100% the javascript-zoo compat-table tests, and is sitting around 64% on test262.<p>Why did I build Ant? Well, I wanted a runtime small enough to ship with CLI&#x27;s and small Docker containers without having to drag along 50 to 100mb of just runtime. Ant in its current state is performant enough in some cases to compete with v8, but mostly in specific shapes.<p>Background on how it got here: <a href="https:&#x2F;&#x2F;themackabu.dev&#x2F;blog&#x2F;ant-part-two" rel="nofollow">https:&#x2F;&#x2F;themackabu.dev&#x2F;blog&#x2F;ant-part-two</a><p>Online demo shell&#x2F;container: <a href="https:&#x2F;&#x2F;ant.ax" rel="nofollow">https:&#x2F;&#x2F;ant.ax</a><p>If anyone has questions about Ant, such as the engine, im happy to answer any of them! Feedback is also appreciated, if you run your own code and hit some edge case.

[Other] Remembering Planet Source Code: Sharing Code Before GitHub Made It Easy

[API/SDK] Show HN: GETadb.com – every GET request creates a DB Hey HN! We made GETadb.com, so it&#x27;s easier to get agents to build you full stack apps. You don&#x27;t need to give them any credentials. Just by loading a GET request, they get access to a database, a sync engine, and abstractions for auth, presence, and streams.<p>To see what the agent sees, you can load https:&#x2F;&#x2F;getadb.com&#x2F;new<p>There&#x27;s two fun things about how it&#x27;s implemented:<p>1. If you curl the home page, it the agent content rather than human content. We do this by detecting the &#x27;Sec-Fetch-Mode&#x27; header. It&#x27;s not perfect, but gets the job done for Claude Code et al.<p>2. For an agent to spin up an app, they make _two_ fethes. (1) getadb.com&#x2F;guide tells them to generate a uuid, and fetch (2) getadb.com&#x2F;provision&#x2F;&lt;uuid&gt;. We did this, because just about half of the popular web-based app builders cache URLs globally, even if you return no-store headers. To get around this we just instruct the agent to generate unique URLs<p>You may wonder: Why GET requests, rather than POST requests? It&#x27;s because then you can build in surprising places. For example, we get meta.ai to build an app inside the artifact preview: https:&#x2F;&#x2F;artifacts.meta.ai&#x2F;share&#x2F;a&#x2F;b80c7412-c3af-4088-b430-78efdfe8ea2d<p>Under the hood, this is possible because the whole infra is mult-tenant from ground up. We already announced how that works on HN, but if you&#x27;re curious here&#x27;s the essay for it: https:&#x2F;&#x2F;www.instantdb.com&#x2F;essays&#x2F;architecture

[Other] Show HN: Notion-to-site – sync any Notion database to local Markdown/MDX/JSON Built this while syncing my own blog from Notion. Good alternative to paid options like Super.so.<p>Supports incremental sync, all Notion block types including equations and synced blocks, image download + WebP conversion, and adapters for Markdown, MDX, and JSON.<p>Works with Next.js, Astro, SvelteKit, and anything that reads files.

[Other] Show HN: Git for AI Agents hi guys. been working on something i think is fundamentally missing in today&#x27;s workflow with ai agents.<p>vcs.<p>i find myself struggling with questions that agents can&#x27;t answer like &quot;why did you do it?&quot;, &quot;when did u delete this folder? why?&quot;, etc. or trying to &#x2F;rewind (after a &#x2F;compact...) or basically `bisect` to find when and why something was done by the agent in the current &#x2F; previous session.<p>just like git did for code, i think we are the same core capabilities with ai agents<p>so...<p>i developed an open source solution for that (currently supporting claude code)<p>would love to get feedback, contribution or maybe other ideas or solutions you find for those problems.

[Other] Building a web server in aarch64 assembly to give my life (a lack of) meaning