Show HN: Druids – Build your own software factory https://ift.tt/kBIqD6y

Show HN: Druids – Build your own software factory Hi HN! Druids ( https://ift.tt/YOyXn7r ) is an open-source library for structuring and running multi-agent coding workflows. Druids makes it easy to do this by abstracting away all the VM infrastructure, agent provisioning, and communication. You can watch our demo video here ( https://www.youtube.com/watch?v=EVJqW-tvSy4 ) to see what it looks like. At a high level: - Users can write Python programs that define what roles the agents take on and how they interact with each other. - A program is made of events - clear state transitions that the agents or clients can call to modify state. Each event gets exposed as an agent tool. - Druids provisions full VMs so that the agents can run continuously and communicate effectively. We made Druids because we were making lots of internal coding tools using agents and found it annoying to have to rearrange the wiring every time. As we were building Druids, we realized a lot of our internal tools were easier to express as an event-driven architecture – separating deterministic control flow from agent behavior – and this design also made it possible to have many agents work reliably. We had issues with scaling the number of concurrent agents within a run, so we decided to have each program run in an isolated sandbox program runtime, kind of the same way you run a Modal function. Each agent then calls the runtime with an agent token, which checks who can talk to who or send files across VMs, and then applies the tool call. Our early users have found the library useful for: - running many agents to do performance optimization - building custom automated software pipelines for eg code review, pentesting, large-scale migrations, etc... We've heard that the frontier labs have the infrastructure to quickly spin up 100 agents and have them coordinate with each other smoothly in various ways. We're hoping that Druids can be a starting point to make that infrastructure more accessible. https://ift.tt/YOyXn7r April 9, 2026 at 12:12AM

Show HN: Git-worm, the simple worktree manager https://ift.tt/SysONL1

Show HN: Git-worm, the simple worktree manager https://ift.tt/xmZEbQi April 9, 2026 at 09:45PM

Show HN: I built Dirac, Hash Anchored AST native coding agent, costs -64.8 pct https://ift.tt/ReTYNfg

Show HN: I built Dirac, Hash Anchored AST native coding agent, costs -64.8 pct Fully open source, a hard fork of cline. Full evals on the github page that compares 7 agents (Cline, Kilo, Ohmypi, Opencode, Pimono, Roo, Dirac) on 8 medium complexity tasks. Each task, each diff and correctness + cost info on the github Dirac is 64.8% cheaper than the average of the other 6. https://ift.tt/E7BIJ8R April 9, 2026 at 04:06PM

Show HN: Homebutler – I manage my homelab from chat. AI never gets raw shell https://ift.tt/FKD7ctr

Show HN: Homebutler – I manage my homelab from chat. AI never gets raw shell https://homebutler.dev April 9, 2026 at 04:09PM

Show HN: CSS Studio. Design by hand, code by agent https://ift.tt/XZGStqD

Show HN: CSS Studio. Design by hand, code by agent Hi HN! I've just released CSS Studio, a design tool that lives on your site, runs on your browser, sends updates to your existing AI agent, which edits any codebase. You can actually play around with the latest version directly on the site. Technically, the way this works is you view your site in dev mode and start editing it. In your agent, you can run /studio which then polls (or uses Claude Channels) an MCP server. Changes are streamed as JSON via the MCP, along with some viewport and URL information, and the skill has some instructions on how best to implement them. It contains a lot of the tools you'd expect from a visual editing tool, like text editing, styles and an animation timeline editor. https://cssstudio.ai April 9, 2026 at 03:23PM

Show HN: Moon simulator game, ray-casting https://ift.tt/4H0ZdlR

Show HN: Moon simulator game, ray-casting Did this a few years ago. Seems apropos. Sources and more here: https://ift.tt/s7jVo36 https://ift.tt/7v3Y9aK April 6, 2026 at 09:09PM

Show HN: A website to track live music attendance https://ift.tt/0br4M5h

Show HN: A website to track live music attendance TL;DR: I built a website that allows users to track the concerts they've been to. If you have strong opinions about engineering/design or how shows should be tracked (festivals, venues, etc...), I'd love to get your input! For the past ~5 years, I've been tracking the shows I attend on my personal website ( https://ift.tt/kWDU6fx ). It's fun to see things like distance traveled and how many times I've been to certain venues. I know many friends who also track their shows through notes, ticket stubs, Excel, etc... It always bummed me out that I couldn't pore through their concert data myself... showcount.com is my solution to that desire. It's essentially a public version of my old personal website, where anyone can make an account and manage a show list (mine is https://ift.tt/6S1fUND ). I'm currently on the lookout for other live music lovers and/or data nerds to try out the site and give opinions on various design choices. If any of the following topics are of interest to you, please reach out! - How should venue name/location changes be handled? - How should music festivals be handled? - I have an initial version of an AI parser for loading in existing show lists; how can this be made more robust? - What else should have first-class tracking support (e.g., friends in attendance)? As an aside, this project is also my first experiment with full-on vibe-coding / harness-engineering. I began the project with Cursor and then switched to Claude Code. I've been programming for the better part of a decade, mostly Python and Java. Full-stack development is relatively new to me. I include the tech stack below. Most decisions were made pragmatically based on what I thought would get me to a first version of the site as quickly as possible. - Next.js web app hosted on Vercel - Fast API backend service (for the AI parsing) hosted on Railway - Supabase - Observability through Axiom (logging), PostHog (analytics), and Sentry (monitoring) - Clerk for user authentication - Google Maps API for venue locations - Claude API for the AI parser - Terraform for infra-as-code https://ift.tt/whRByJj April 9, 2026 at 12:42AM