🛠️ All DevTools

[Other] Building a coding agent in Swift from scratch

[Other] TurboQuant: Redefining AI efficiency with extreme compression

[Database] Show HN: DuckDB community extension for prefiltered HNSW using ACORN-1 Hey folks! As someone doing hybrid search daily and wishing I could have a pgvector-like experience but with actual prefiltered approximate nearest neighbours, I decided to just take a punt on implementing ACORN on a fork of the DuckDB VSS extension. I had to make some changes to (vendored) usearch that I&#x27;m thinking of submitting upstream. But this does the business. Approximate nearest neighbours with WHERE prefiltering.<p>Edit: Just to clarify, this has been accepted into the community extensions repo. So you can use it like:<p>```<p>INSTALL hnsw_acorn FROM community;<p>LOAD hnsw_acorn;<p>```

[Other] Zero-Cost POSIX Compliance: Encoding the Socket State Machine in Lean's Types

[Other] Show HN: AI Roundtable – Let 200 models debate your question Hey HN! After the Car Wash Test post got quite a big discussion going (400+ comments, <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=47128138">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=47128138</a>), I spent the past few weeks building a tool so anyone can run these kinds of questions and get structured results. No signup and free to use.<p>You type a question, define answer options, pick up to 50 models at a time from a pool of 200+, and they all answer independently under identical conditions. No system prompt, structured output, same setup for every model.<p>You can also run a debate round where models see each other&#x27;s reasoning and get a chance to change their minds. A reviewer model then summarizes the full transcript. All models are routed via my startup Opper. Any feedback is welcome!<p>Hope you enjoy it, and would love to hear what you think!

[Other] Show HN: Skub – a sliding puzzle browser game Hi HN,<p>I&#x27;ve built Skub, a sliding puzzle game for the browser, based on a classic boardgame: Ricochet Robots.<p>It started as a challenge of trying to simplify the boardgame mechanics to fit on a mobile browser, which led to an 8x8 grid.<p>Since, it has evolved to a bit more of an experimentation with Deno, and a way for me to truly try out AI-assisted development. Claude Code has been especially helpful in building the BFS solver and setting up CI, less so in UI and logic.<p>I hope you enjoy it, all questions &#x2F; feedback welcome.

[Other] Show HN: I took back Video.js after 16 years and we rewrote it to be 88% smaller What do you do when private equity buys your old company and fires the maintainers of the popular open source project you started over a decade ago? You reboot it, and bring along some new friends to do it.<p>Video.js is used by billions of people every month, on sites like Amazon.com, Linkedin, and Dropbox, and yet it wasn’t in great shape. A skeleton crew of maintainers were doing their best with a dated architecture, but it needed more. So Sam from Plyr, Rahim from Vidstack, and Wes and Christain from Media Chrome jumped in to help me rebuild it better, faster, and smaller.<p>It’s in beta now. Please give it a try and tell us what breaks.

[Other] Show HN: Gridland: make terminal apps that also run in the browser Hi everyone,<p>Gridland is a runtime + ShadCN UI registry that makes it possible to build terminal apps that run in the browser as well as the native terminal. This is useful for demoing TUIs so that users know what they&#x27;re getting before they are invested enough to install them. And, tbh, it&#x27;s also just super fun!<p>Gridland is the successor to Ink Web (ink-web.dev) which is the same concept, but using Ink + xterm.js. After building Ink Web, we continued experimenting and found that using OpenTUI and a canvas renderer performed better with less flickering and nearly instant load times.<p>We&#x27;re excited to continue iterating on this. I expect a lot of criticism from the &quot;why does this need to exist&quot; angle, and tbh, it probably doesn&#x27;t - it&#x27;s really mostly just for fun, but we still think the demo use case mentioned previously has potential.<p>- Chris + Jess

[CLI Tool] Show HN: Gemini can now natively embed video, so I built sub-second video search Gemini Embedding 2 can project raw video directly into a 768-dimensional vector space alongside text. No transcription, no frame captioning, no intermediate text. A query like &quot;green car cutting me off&quot; is directly comparable to a 30-second video clip at the vector level.<p>I used this to build a CLI that indexes hours of footage into ChromaDB, then searches it with natural language and auto-trims the matching clip. Demo video on the GitHub README. Indexing costs ~$2.50&#x2F;hr of footage. Still-frame detection skips idle chunks, so security camera &#x2F; sentry mode footage is much cheaper.

[Other] Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromised About an hour ago new versions have been deployed to PyPI.<p>I was just setting up a new project, and things behaved weirdly. My laptop ran out of RAM, it looked like a forkbomb was running.<p>I&#x27;ve investigated, and found that a base64 encoded blob has been added to proxy_server.py.<p>It writes and decodes another file which it then runs.<p>I&#x27;m in the process of reporting this upstream, but wanted to give everyone here a headsup.<p>It is also reported in this issue: <a href="https:&#x2F;&#x2F;github.com&#x2F;BerriAI&#x2F;litellm&#x2F;issues&#x2F;24512" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;BerriAI&#x2F;litellm&#x2F;issues&#x2F;24512</a>

[Other] Show HN: Running AI agents across environments needs a proper solution Hi HN folks,<p>I have been building AI agents for quite some time now. The shift has gone from LLM + Tools → LLM Workflows → Agent + Tools + Memory, and now we are finally seeing true agency emerge: agents as systems composed of tools, command-line access, fine-grained system capabilities, and memory.<p>This way of building agents is powerful, and I believe it is here to stay. But the real question is: are the systems powering these agents ready for that future?<p>I do not think so.<p>Using Docker for a single agent is not going to scale well, because agents need to be lightweight and fast. LLMs already add significant latency, so adding heavy runtime overhead on top only makes things worse. Existing solutions start to fall apart here.<p>Agents built in Python also tend to have a large memory footprint, which becomes a serious problem when you want to scale to thousands of agents.<p>And open-source for agents is still not where it should be. Right now, I cannot easily reuse agents built by domain experts the same way I reuse open-source software.<p>These issues bothered me, and I realized that if agents are ever going to be democratized, they need to be open and easy to use. Just like Docker solved system dependencies, we need something similar for agents.<p>That is why I started building an agent framework in Rust. It is modular and follows the principle of true agency: an agent is an entity with tools, memory, and an executor. In AutoAgents, users can independently create and modify tools, executors, and memory.<p>With AutoAgents, I saw that powerful agents could be built without compromising on performance or memory the way many other frameworks do.<p>But the other problems still remained: re-sharing agents, sandboxing, and scaling to thousands of agents.<p>So I created Odyssey — a bundle-first agent runtime written in Rust on top of AutoAgents, the Rust agent framework. It lets you define an agent once, package it as a portable artifact, and run it through the same execution model across local development, embedded SDK usage, shared runtime servers, and terminal workflows.<p>Both AutoAgents and Odyssey are fully open source and built in Rust, and I am planning to build an Odyssey Agent Hub soon, with additional features like WASM tools, custom memory layers, and more.<p>My vision is to democratize agents so they are available to everyone — securely and performantly. Being open is not enough; agents also need to be secure.<p>The project is still in alpha, but it is in a working state.<p>AutoAgents Repo -&gt; <a href="https:&#x2F;&#x2F;github.com&#x2F;liquidos-ai&#x2F;AutoAgents" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;liquidos-ai&#x2F;AutoAgents</a><p>Odyssey Repo -&gt; <a href="https:&#x2F;&#x2F;github.com&#x2F;liquidos-ai&#x2F;Odyssey" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;liquidos-ai&#x2F;Odyssey</a><p>I would really appreciate feedback — especially from anyone who has dealt with similar problems. Your feedback help me shape the product.<p>Thanks for your time in advance!

[Package Manager] Nanobrew: The fastest macOS package manager compatible with brew

[CLI Tool] Show HN: ProofShot – Give AI coding agents eyes to verify the UI they build I use AI agents to build UI features daily. The thing that kept annoying me: the agent writes code but never sees what it actually looks like in the browser. It can’t tell if the layout is broken or if the console is throwing errors.<p>So I built a CLI that lets the agent open a browser, interact with the page, record what happens, and collect any errors. Then it bundles everything — video, screenshots, logs — into a self-contained HTML file I can review in seconds.<p>proofshot start --run &quot;npm run dev&quot; --port 3000 # agent navigates, clicks, takes screenshots proofshot stop<p>It works with whatever agent you use (Claude Code, Cursor, Codex, etc.) — it’s just shell commands. It&#x27;s packaged as a skill so your AI coding agent knows exactly how it works. It&#x27;s built on agent-browser from Vercel Labs which is far better and faster than Playwright MCP.<p>It’s not a testing framework. The agent doesn’t decide pass&#x2F;fail. It just gives me the evidence so I don’t have to open the browser myself every time.<p>Open source and completely free.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;AmElmo&#x2F;proofshot" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;AmElmo&#x2F;proofshot</a>

[Other] Ripgrep is faster than grep, ag, git grep, ucg, pt, sift (2016)

[Other] Log File Viewer for the Terminal

[Other] Sunsetting the Techempower Framework Benchmarks

[Other] Claude Code Cheat Sheet

[Other] How I'm Productive with Claude Code

[Other] Show HN: Burn Room – ephemeral SSH chat, messages burn after 1 hour I built Burn Room — a self-hosted SSH chat server where messages burn after 1 hour and rooms auto-destruct after 24 hours. Nothing is written to disk. No account, no email, no browser required.<p><pre><code> ssh guest@burnroom.chat -p 2323 password: burnroom </code></pre> Or connect from a browser (xterm.js web terminal): <a href="https:&#x2F;&#x2F;burnroom.chat" rel="nofollow">https:&#x2F;&#x2F;burnroom.chat</a>

[Other] Show HN: Shrouded, secure memory management in Rust Hi HN!<p>I&#x27;ve been building a project that handles high-value credentials in-process, and I wanted something more robust than just zeroing memory on drop. A comment on a recent Show HN[0] made me realize that awareness of lower-level memory protection techniques might not be as widespread as I thought.<p>The idea here is to pull out all the tools in one crate, with a relatively simple API. * mlock&#x2F;VirtualLock to prevent sensitive memory from being swapped (eg the KeePass dump) * Core dump exclusion using MADV_DONTDUMP on Linux &amp; Android * mprotect to minimize exposure over time * Guard pages to mitigate under&#x2F;overflows<p>After some battle testing, the goal here is to provide a more secure memory foundation for things like password managers and cryptocurrency wallets.<p>This was a fun project, and I learned a lot - would love any feedback!<p>[0] - <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=47073430">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=47073430</a>