Show HN: Unlegacy – document everything, from COBOL to AI generated code
5 by Absonsonson | 0 comments on Hacker News.
Hack Nux
Watch the number of websites being hacked today, one by one on a page, increasing in real time.
New Show Hacker News story: Show HN: Eve – Managed OpenClaw for work
Show HN: Eve – Managed OpenClaw for work
9 by zachdive | 4 comments on Hacker News.
Eve is an AI agent harness that runs in an isolated Linux sandbox (2 vCPUs, 4GB RAM, 10GB disk) with a real filesystem, headless Chromium, code execution, and connectors to 1000+ services. You give it a task and it works in the background until it's done. I built this because I wanted OpenClaw without the self-hosting, pointed at actual day-to-day work. I’m thinking less personal assistant and more helpful colleague. Here’s a short demo video: https://ift.tt/EFH4vYV The main interface is a web app where you can watch work happen in real time (agents spawning, files being written, use of the CLI). There's also an iMessage integration so you can fire a task asynchronously, put your phone down, and get a reply when it's finished. Under the hood, there's an orchestrator (Claude Opus 4.6) that routes to the right domain-specific model for each subtask: browsing, coding, research, and media generation. For complex tasks it spins up parallel sub-agents that coordinate through the shared filesystem. They have persistent memory across sessions so context compounds over time. I’ve packaged it with a bunch of pre-installed skills so it can execute in a variety of job roles (sales, marketing, finance) at runtime. Here are a few things Eve has helped me with in the last couple days: - Edit this demo video with a voice over of Garry: https://www.youtube.com/watch?v=S4oD7H3cAQ0 - Do my tax returns - To build HN as if it was the year 2030: https://ift.tt/wTSEGc7 AMA on the architecture and lmk your thoughts :) P.S. I've given every new user $100 worth of credits to try it.
9 by zachdive | 4 comments on Hacker News.
Eve is an AI agent harness that runs in an isolated Linux sandbox (2 vCPUs, 4GB RAM, 10GB disk) with a real filesystem, headless Chromium, code execution, and connectors to 1000+ services. You give it a task and it works in the background until it's done. I built this because I wanted OpenClaw without the self-hosting, pointed at actual day-to-day work. I’m thinking less personal assistant and more helpful colleague. Here’s a short demo video: https://ift.tt/EFH4vYV The main interface is a web app where you can watch work happen in real time (agents spawning, files being written, use of the CLI). There's also an iMessage integration so you can fire a task asynchronously, put your phone down, and get a reply when it's finished. Under the hood, there's an orchestrator (Claude Opus 4.6) that routes to the right domain-specific model for each subtask: browsing, coding, research, and media generation. For complex tasks it spins up parallel sub-agents that coordinate through the shared filesystem. They have persistent memory across sessions so context compounds over time. I’ve packaged it with a bunch of pre-installed skills so it can execute in a variety of job roles (sales, marketing, finance) at runtime. Here are a few things Eve has helped me with in the last couple days: - Edit this demo video with a voice over of Garry: https://www.youtube.com/watch?v=S4oD7H3cAQ0 - Do my tax returns - To build HN as if it was the year 2030: https://ift.tt/wTSEGc7 AMA on the architecture and lmk your thoughts :) P.S. I've given every new user $100 worth of credits to try it.
New ask Hacker News story: Open Source card game cuttle.cards has its world championship Saturday at 1pm ET
Open Source card game cuttle.cards has its world championship Saturday at 1pm ET
3 by aleph_one | 0 comments on Hacker News.
Cuttle is a combat card game of mysterious origins dating back to the 1970's. It feels like playing Magic or Yugioh!, but it's played with a standard 52-card deck. https://cuttle.cards is an open source (code: https://ift.tt/OIl8iGS) project that lets people play Cuttle online, for free. The project is under active development and has a competitive format with 4 seasonal championships each year, followed by a world championship tournament. The Cuttle World Championship is tomorrow, April 11th, at 1pm ET. You can watch it live on Twitch (https://ift.tt/LaCFjuV) or Youtube (https://www.youtube.com/live/mBj04alF1Z8?si=amIR5flmW7zewmL9) and chat with the players on the Cuttle discord (https://ift.tt/anRj2XE). *RULES* ### Goal The goal is to be the first player to have 21 or more points worth of point cards on your field. The first player to reach the goal wins immediately. One player (traditionally the dealer) is dealt 6 cards, and their opponent is dealt 5. The player with 5 cards goes first. ### Play On your turn you must perform exactly one of the following actions: - *Draw:* Take one card from the Deck. You may not draw past the 8-card hand limit - *Points:* Play a number card from your hand. Worth its rank in points, lasts until scrapped - *Scuttle:* Scrap an opponent’s point card with a bigger one from your hand - If two number cards have the same rank, the suit breaks the tie - Suit order is (high) Spades ♠ > Hearts ♥ > Diamonds ♦> Clubs ♣ (low) - *Royal:* Play a face card for a persistent benefit based on rank (lasts until scrapped) - *Glasses:* Play an Eight to reveal your opponent’s hand (lasts until scrapped) - *One-Off:* Scrap a number card for an effect based on the rank of the card. ## Royals Royals (Kings, Queens, and Jacks) may be played to the field for a persistent benefit that remains in effect until the card is scrapped. Each Royal gives a different effect. *King:* Reduce the number of points you need to win (21, 14, 10, 5, 0 points with 0, 1, 2, 3, 4 kings) *Queen:* Protects your other cards from being targeted by the effects of other cards. This protects your cards against 2’s (both effects), 9’s, and Jacks, but not scuttling. *Jack:* Play on an opponent’s point card to steal it. Point card returns to opponent if the jack is scrapped or if another jack is used to steal it back. ### One-Offs Number cards (except 8’s and 10’s) can be played for a One-Off effect, which scraps the card for an effect based on the rank of the card played. Whenever a one-off is played, the other player may counter it using a two to cancel the effect. - *Ace:* Scrap all point cards on the field - *Two:* Twos have two alternative one-off effects: - Counter target One-Off Effect (Played immediately in response to a one-off) - Scrap target Royal - *Three:* Choose a card in the scrap pile and put it in your hand - *Four:* Your opponent discards two cards of their choice - *Five:* Discard one card and then draw three cards - *Six:* Scrap all Royals and Glasses Eights on the field - *Seven:* Choose one of the top two cards from the deck and play it however you choose. - *Nine:* Return a card from your opponent’s field to their hand. They cannot play it next turn.
3 by aleph_one | 0 comments on Hacker News.
Cuttle is a combat card game of mysterious origins dating back to the 1970's. It feels like playing Magic or Yugioh!, but it's played with a standard 52-card deck. https://cuttle.cards is an open source (code: https://ift.tt/OIl8iGS) project that lets people play Cuttle online, for free. The project is under active development and has a competitive format with 4 seasonal championships each year, followed by a world championship tournament. The Cuttle World Championship is tomorrow, April 11th, at 1pm ET. You can watch it live on Twitch (https://ift.tt/LaCFjuV) or Youtube (https://www.youtube.com/live/mBj04alF1Z8?si=amIR5flmW7zewmL9) and chat with the players on the Cuttle discord (https://ift.tt/anRj2XE). *RULES* ### Goal The goal is to be the first player to have 21 or more points worth of point cards on your field. The first player to reach the goal wins immediately. One player (traditionally the dealer) is dealt 6 cards, and their opponent is dealt 5. The player with 5 cards goes first. ### Play On your turn you must perform exactly one of the following actions: - *Draw:* Take one card from the Deck. You may not draw past the 8-card hand limit - *Points:* Play a number card from your hand. Worth its rank in points, lasts until scrapped - *Scuttle:* Scrap an opponent’s point card with a bigger one from your hand - If two number cards have the same rank, the suit breaks the tie - Suit order is (high) Spades ♠ > Hearts ♥ > Diamonds ♦> Clubs ♣ (low) - *Royal:* Play a face card for a persistent benefit based on rank (lasts until scrapped) - *Glasses:* Play an Eight to reveal your opponent’s hand (lasts until scrapped) - *One-Off:* Scrap a number card for an effect based on the rank of the card. ## Royals Royals (Kings, Queens, and Jacks) may be played to the field for a persistent benefit that remains in effect until the card is scrapped. Each Royal gives a different effect. *King:* Reduce the number of points you need to win (21, 14, 10, 5, 0 points with 0, 1, 2, 3, 4 kings) *Queen:* Protects your other cards from being targeted by the effects of other cards. This protects your cards against 2’s (both effects), 9’s, and Jacks, but not scuttling. *Jack:* Play on an opponent’s point card to steal it. Point card returns to opponent if the jack is scrapped or if another jack is used to steal it back. ### One-Offs Number cards (except 8’s and 10’s) can be played for a One-Off effect, which scraps the card for an effect based on the rank of the card played. Whenever a one-off is played, the other player may counter it using a two to cancel the effect. - *Ace:* Scrap all point cards on the field - *Two:* Twos have two alternative one-off effects: - Counter target One-Off Effect (Played immediately in response to a one-off) - Scrap target Royal - *Three:* Choose a card in the scrap pile and put it in your hand - *Four:* Your opponent discards two cards of their choice - *Five:* Discard one card and then draw three cards - *Six:* Scrap all Royals and Glasses Eights on the field - *Seven:* Choose one of the top two cards from the deck and play it however you choose. - *Nine:* Return a card from your opponent’s field to their hand. They cannot play it next turn.
New Show Hacker News story: Show HN: Coderegon Trail – A retro game to help you explore open-source repos
Show HN: Coderegon Trail – A retro game to help you explore open-source repos
3 by dtran | 3 comments on Hacker News.
After seeing yesterday's insightful post on using git heuristics as the first step for exploring a codebase [1], I messaged a couple of friends to ask how they explore codebases today. All of us just point Claude or Codex at the repo and start asking questions. I realized I barely read docs, browse files on GitHub, or explore repos locally anymore without Claude Code. But using LLMs to help us learn and understand code rather than just write code still seems to be under-explored. A couple months ago, I tried building a Claude code command to help me "fly through" a repo using an LLM to guide me to interesting parts of the codebase and narrate explainers for them as it navigated the files. That didn't really work, partially because my attention span for reading docs and code is at an all-time low. I saw that Devin released Deepwiki and tried to use that, but usually didn't get very far. More recently, I tried to make it fun: generate a game that tricks me into actually getting started with the codebase. I landed on an Oregon Trail inspired game where I read code snippets and answer questions generated by Claude. You can try it out here: https://ift.tt/ZS7dzRa I've been having fun pointing it at various repos, especially ones getting a lot of hype and stars but not necessarily real usage or contributions. I pointed it at a few projects that my friends and I starred but never explored as well as some of the top Show HN projects from 2026 so far that linked to open-source repos. I wanted to see if this might be interesting to anyone else who is struggling to read code. It sort of works for PRs, but that feels like a pretty different problem, so open to any ideas. As I was typing up this Show HN, I realized that it would be ironic if this wasn't also open source, so I frantically tried to clean up the repo a bit, and pointed the command at its own source code. You can play the Recursive Trail here: https://ift.tt/ZS7dzRa or see the Github repo here: Let me know if there are any inaccuracies, bugs, or if you'd like me to add a repo without setting it up yourself! [1] https://ift.tt/B9gltOS
3 by dtran | 3 comments on Hacker News.
After seeing yesterday's insightful post on using git heuristics as the first step for exploring a codebase [1], I messaged a couple of friends to ask how they explore codebases today. All of us just point Claude or Codex at the repo and start asking questions. I realized I barely read docs, browse files on GitHub, or explore repos locally anymore without Claude Code. But using LLMs to help us learn and understand code rather than just write code still seems to be under-explored. A couple months ago, I tried building a Claude code command to help me "fly through" a repo using an LLM to guide me to interesting parts of the codebase and narrate explainers for them as it navigated the files. That didn't really work, partially because my attention span for reading docs and code is at an all-time low. I saw that Devin released Deepwiki and tried to use that, but usually didn't get very far. More recently, I tried to make it fun: generate a game that tricks me into actually getting started with the codebase. I landed on an Oregon Trail inspired game where I read code snippets and answer questions generated by Claude. You can try it out here: https://ift.tt/ZS7dzRa I've been having fun pointing it at various repos, especially ones getting a lot of hype and stars but not necessarily real usage or contributions. I pointed it at a few projects that my friends and I starred but never explored as well as some of the top Show HN projects from 2026 so far that linked to open-source repos. I wanted to see if this might be interesting to anyone else who is struggling to read code. It sort of works for PRs, but that feels like a pretty different problem, so open to any ideas. As I was typing up this Show HN, I realized that it would be ironic if this wasn't also open source, so I frantically tried to clean up the repo a bit, and pointed the command at its own source code. You can play the Recursive Trail here: https://ift.tt/ZS7dzRa or see the Github repo here: Let me know if there are any inaccuracies, bugs, or if you'd like me to add a repo without setting it up yourself! [1] https://ift.tt/B9gltOS
New Show Hacker News story: Show HN: Druids – Build your own software factory
Show HN: Druids – Build your own software factory
8 by etherio | 1 comments on Hacker News.
Hi HN! Druids ( https://ift.tt/mr8p4iR ) 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.
8 by etherio | 1 comments on Hacker News.
Hi HN! Druids ( https://ift.tt/mr8p4iR ) 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.
New Show Hacker News story: Show HN: I built Dirac, Hash Anchored AST native coding agent, costs -64.8 pct
Show HN: I built Dirac, Hash Anchored AST native coding agent, costs -64.8 pct
2 by GodelNumbering | 1 comments on Hacker News.
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.
2 by GodelNumbering | 1 comments on Hacker News.
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.