Show HN: Dari-docs – Optimize your docs using parallel coding agents https://ift.tt/gL5MlxE

Show HN: Dari-docs – Optimize your docs using parallel coding agents It’s well known at this point that documentation needs to be optimized for AI agents - we’re all pointing our Claude Code / Codex / Pi agents at documentation, and expecting the models to figure out how to implement a product. This, however, changes the entire optimization problem when writing documentation. Good documentation now becomes more objective - you are solving the very concrete problem: can a dumb harness running the dumbest model implement this reliably? Humans can typically compensate for inconsistent terminology or scattered context across pages, but for agents, this often will waste time (or even just completely confuse the agent). We’ve been building a small project around this called dari-docs: users can upload their documentation via website or CLI and run agents across different providers to see where they falter. You can upload your documentation, feed a list of tasks, and ask agents with varying intelligence / cost levels to complete those tasks in parallel. When a run is complete, you get back a list feedback markdown files from each agent run and can apply changes based on agent feedback. Managed service: https://ift.tt/kR0TtBv , repo link: https://ift.tt/ZqAk2fl The agents actually try to use the product end-to-end. They search through the docs, follow instructions, run commands, try examples, and attempt to debug failures. Importantly, this is not a static LLM review of the documentation. The agents are actually attempting the integration. You can also enable live verification with test credentials so the agents can actually verify workflows against real APIs: dari-docs check . --live-verify --secret-env DARI_TEST_API_KEY --task "Create a checkout session" If you’re building a CLI, API, MCP server, or SDK and actively maintaining docs for humans or agents, we’d love to work with you and test this on real workflows! https://ift.tt/ZqAk2fl May 20, 2026 at 08:53PM

Show HN: IgniteMS – batch text embeddings at 253K msg/s on 8x A100 https://ift.tt/y19PZVG

Show HN: IgniteMS – batch text embeddings at 253K msg/s on 8x A100 https://ift.tt/m2ykXgD May 20, 2026 at 09:07PM

Show HN: Logbox – let Claude monitor your dev logs https://ift.tt/Ayr8KUf

Show HN: Logbox – let Claude monitor your dev logs TL;DR: logbox is an open-source tool that pipes dev server logs to a local sqlite db with ` | logbox collect`. Give Claude Code access by running `claude mcp add logbox -- logbox serve`. I used to copy & paste logs into Claude Code when manually testing my server in dev. I wanted to give it its own verification loop. I initially tried having it boot the server itself and follow the logs. It was good at knowing if the server booted properly, but it capped out and missed details when the logs started flowing in. I also tried piping the logs to a local file and telling Claude to read them from there. It worked, but became annoying once we had multiple services or wanted to reference past dev server sessions. So I built logbox for ourselves at Struct and decided to open-source it. It’s a simple Rust CLI that pipes logs into a local SQLite db with an MCP server that gives coding agents the ability to search them. Once it could reliably monitor the dev server logs totally autonomously after testing its changes, I stopped needing to fish for log snippets and keep nudging it to get a manual test working end-to-end. Everything stays local. `logbox serve` is an stdio MCP server and it just works with the local SQLite db. https://ift.tt/F53Dhbr May 19, 2026 at 11:03PM

Show HN: Gaussian Splat of a Strawberry https://ift.tt/I3ZckaL

Show HN: Gaussian Splat of a Strawberry The Setup: https://ift.tt/PfqjgVb https://ift.tt/dVOTQ1a https://ift.tt/sbwJ9Ny https://ift.tt/Q8XUwgo https://ift.tt/FpiqQUx May 19, 2026 at 02:38PM

Show HN: Better.ftp – cycling app for FTP tests without subscription https://ift.tt/KXidwB1

Show HN: Better.ftp – cycling app for FTP tests without subscription I built a free iOS app so cyclists can stop paying $20/mo just to retest their FTP. The ramp test itself is a 25-minute Bluetooth interaction with a known protocol. It shouldn't require rent. This app is opensource, free, no ads, no tracking nor third party integrations because I just wanted to have a fun side project and have no interest in monetization. If you are a cyclist, I would kindly ask for feedback on the app especially on the ftp test protocol instructions, trainer-model compatibility, and bug reports App store link: https://ift.tt/SmyW8gn GitHub (opensource project): https://ift.tt/ENL2rmj Demo gif: https://betterftp.cc/promo.gif https://betterftp.cc/ May 19, 2026 at 01:33AM

Show HN: Cubic Doggo, a Open-Source 12-DOF 4-Legged Robot Based on ROS2 https://ift.tt/2tYl7kz

Show HN: Cubic Doggo, a Open-Source 12-DOF 4-Legged Robot Based on ROS2 This is a recipe for building intermediate-priced robot dog from scratch with all commercial/3D-printed parts, controlled by Rasp Pi 5 and ROS2 Jazzy. A manually coded walk gait is implemented so far, which can be controlled by a controller to move forward or change directions. It does not yet have an IMU required for RL training; however, I believe it's one of the simplest design out there available for multiple development paths. https://ift.tt/ELCmuhM May 18, 2026 at 09:20PM

Show HN: We missed Winamp, so we built an audio player for macOS https://ift.tt/B86bNKT

Show HN: We missed Winamp, so we built an audio player for macOS https://ift.tt/3DTJwK9 May 18, 2026 at 11:20PM