Show HN for April 30, 2026

In light of recent news about an agent deleting a production database, I thought now would be a good time to share this.

As the use of AI tools in production is becoming more common, sadly so will the high profile incidents like the one mentioned.

Fewshell is a terminal agent specifically designed to avoid this.

There is no setting to enable command auto-approval. This is by-design, so that the user never has to second-guess or worry about accidentally having it enabled.

Originally my intention was to build an AI mobile terminal to make typing shell commands easy. But with so many mobile-enabled 'claw' agents being available, I decided to make Fewshell the opposite of an autonomous agent.

Please star if you like, let me know what you think. Happy to answer questions.

About me: I'm an ex Amazon Sr. SDE for Alexa AI, and currently am working in AI safety research for agentic RLVR. I use this tool to run and check on my lab experiments.

Hi HN,

I built ukbinday to provide a nicer way to find your bin collection days and actually remember when to put them out.

It shows your upcoming collections and generates a calendar that updates automatically as the schedule comes out. Coverage is at about 85% of the UK so far and I'm working on getting that to 100%. There is also an API for the Home Automation community.

This was built on top of two amazing open-source projects without which this would not exist: https://github.com/robbrad/UKBinCollectionData & https://github.com/mampfes/hacs_waste_collection_schedule Thank you to all the contributors of those repositories!

AgentRQ is a (optionally) human-in-the-loop, self learning closed loop task manager for agents. Agents can create and schedule tasks for themself and work on them on their own schedule.

In high level it comes with one supervisor MCP that controls workspaces(worker agents) and unlimited number of isolated workspace MCPs (self learning agents).

Each workspace/agent has a mission/persona for the agent. And self-learning-loop note.

I am using it about 6 weeks in production, and completed more than 500 tasks. I just released the opensource version(as is in production) under Apache 2.0 license.

Currently it supports Gemini CLI and Claude code. I am going to extend support all major agents soon.

Happy to answer any questions.

A multiplayer hommage to Jean-Michel Sanejouand's Jeu de Topo (1963), a game with no winner or loser where partners arrange stones until both points of view are satisfied.

Here, stones become colored points in a game based on Voronoi diagrams. The original opposing points of view become each player's screen: everyone shares the same points, but phones, tablets, and browser windows frame the space differently, so each player is likely seeing a different Voronoi view.

Two years ago I sat down to build a chess engine for my kids' Christmas present. Wanted it to play badly enough to be beatable but not randomly bad: different styles so they could choose what to face.

While building those styles I noticed the choices started looking like actual historical players' tendencies. Went looking. Turns out: given enough games from one person, you can extract enough of their decision pattern to reproduce it.

Two years later, 41 players, ~3,000 games each. Tal sacrifices unsoundly. Morphy attacks like it's 1850. Capablanca grinds endgames. Same engine underneath, visibly different choices each time.

playchessgate.com: browser, no signup. The kids never got their Christmas present.

I've been building this solo for a while now. I usually prefer writing code, but Unity's shader graph pulled me in, I ended up building all the visuals with custom shaders, which gave the game its look.

The concept is a reverse city-builder: instead of expanding and consuming, you restore a wasteland back into a thriving ecosystem using robots.

Would love any feedback, both on the technical side and the game itself. Free demo just went live on Steam yesterday.