Alternatives
Products that do what CyberGym/BountyBench-AI agents find zero-days and solve bug bounties does
A turning point on AI agents in Cybersecurity, shown in two recent research papers from UC Berkeley and Stanford: CyberGym: AI agents discovered 15 zero-days in major open-source software BountyBench: AI agents solved real-world bug bounty tasks worth tens of thousands of dollars This represents a pivotal shift in cybersecurity — AI agents can now autonomously do what only elite human hackers could before. Check out their work: CyberGym: https://www.cybergym.io/ BountyBench: https://bountybench.github.io/
- 1
- 2
- 3
- 4IB
I built this because I wanted my own directory of public companies running bug bounty programs — where I could see their infrastructure in one place and have a real idea of where to start poking holes. Neobotnet collects intel data from companies on HackerOne and Bugcrowd — subdomains, DNS records, web servers with status codes, indexed/crawled URLs, JS files, and exposed secrets/paths (still building this last part). The data is already there when you need it. No scans to run. Currently tracking 41 companies, 63,878 web servers, and 1.8M+ URLs. Long term I want to expand this to…
Mar 2026 · neobotnet.com
- 5
- 6GF
hi guys. been working on something i think is fundamentally missing in today's workflow with ai agents. vcs. i find myself struggling with questions that agents can't answer like "why did you do it?", "when did u delete this folder? why?", etc. or trying to /rewind (after a /compact...) or basically `bisect` to find when and why something was done by the agent in the current / previous session. just like git did for code, i think we are the same core capabilities with ai agents so... i developed an open source solution for that (currently supporting claude code) would love to…
May 2026 · github.com
- 7WB
Hey HN, Automated research is the next big step in AI, with companies like OpenAI aiming to debut a fully automated researcher by 2028 (https://www.technologyreview.com/2026/03/20/1134438/openai-i...). However, there is a very real possibility that much of this corporate research will remain closed to the general public. To counter this, we spent the last month building Enlidea---a machine-to-machine ecosystem for open research. It's a decentralized research hub where autonomous agents propose hypotheses, stake bounties, execute code, and perform automated…
Mar 2026 · enlidea.com
- 8
- 9
- 10
- 11
13,000+ MCP servers, skills & plugins for AI coding agents
Jul 2026 · codexmarketplaces.com
- 122C
Single-agent LLMs suck at long-running complex tasks. We’ve open-sourced a multi-agent orchestrator that we’ve been using to handle long-running LLM tasks. We found that single LLM agents tend to stall, loop, or generate non-compiling code, so we built a harness for agents to coordinate over shared context while work is in progress. How it works: 1. Orchestrator agent that manages task decomposition 2. Sub-agents for parallel work 3. Subscriptions to task state and progress 4. Real-time sharing of intermediate discoveries between agents We tested this on a Putnam-level math problem, but the…
Feb 2026 · github.com
- 13
- 14
- 15AA
I'm a solo dev in Taiwan. I built 4 AI agents that handle content, sales leads, security scanning, and ops for my tech agency — all on Gemini 2.5 Flash free tier (1,500 req/day). I use ~105. Monthly LLM cost: $0. Architecture: 4 agents on OpenClaw (open source), running on WSL2 at home with 25 systemd timers. What they do every day: - Generate 8 social posts across platforms (quality-gated: generate → self-review → rewrite if score < 7/10) - Engage with community posts and auto-reply to comments (context-aware, max 2 rounds) - Research via RSS + HN API + Jina Reader → feed…
Mar 2026
- 16
- 17OS
We build runtime security for AI agents. The playground started as an internal tool that we used to test our own guardrails. But we kept finding the same types of vulnerabilities because we think about attacks a certain way. At some point you need people who don't think like you. So we open-sourced it. Each challenge is a live agent with real tools and a published system prompt. Whenever a challenge is over, the full winning conversation transcript and guardrail logs get documented publicly. Building the general-purpose agent itself was probably the most fun part. Getting it to reliably use…
Mar 2026 · github.com
- 18
- 19
- 20WB
At Metabase, we built an AI agent called Repro-Bot that reads our GitHub issues and attempts to reproduce reported bugs automatically. It started as a hackathon project and is now part of our daily workflow, so we wrote about it and open-sourced the code as an example for others. How have similar tools been working for you? What has worked well and what has not?
Apr 2026 · metabase.com
- 21SO
hello everyone, my first post! AA here, founder of ⌘ Langbase.com — we are a developer platform for building and scaling serverless AI memory agents. I know surveys can be boring, but this one’s different—it’s interactive! That's very much intentional. My team and I have been up for the last 21 hours putting together this report. This was a looot of work, so I hope y'all like it. Introducing … State of AI Agents 2024 report On Langbase, we processed 184 billion tokens and handled 786 million AI agent runs from 36K developers. From all that data plus insights from 3.4K builders who filled out…
2024 · langbase.com
- 22OA
Hi HN. I've been running AI coding agents (Claude Code, Codex, etc.) on real repos for a while now. The dirty secret of "autonomous coding" is that agents stop all the time — quota limits, test failures, policy violations, bad judgement calls. You end up babysitting them. So I asked a different question: what if the system was designed around the assumption that agents WILL fail, and the job of the infrastructure is to never let that failure become a dead end? openTiger is a "non-human-first" orchestration system that runs multiple AI agents in parallel — planner, workers, testers, judge —…
Feb 2026 · github.com
- 23
- 24RU
hey all, happy to share research i've been working on for islo.dev in recent months. ever since the cheating agents (https://debugml.github.io/cheating-agents/) paper came out, revealing reward hacking was 4x more prevalent than previously estimated, i've been looking into how we can deal with the issue the common approach (taken by the tbench team) is post hoc trajectory analysis. i've been interested in the idea of reframing the problem as an endpoint security problem and tackling it via sandbox i hope you find it interesting, and thanks to the islo.dev team for…
Jun 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →