Alternatives
Products that do what Sealed evidence record of an AI agent run – broken twice, credited does
Contribute to cjchanh/aaap-challenge development by creating an account on GitHub.
- 1
- 2
- 3
- 4PG
I use AI agents to build UI features daily. The thing that kept annoying me: the agent writes code but never sees what it actually looks like in the browser. It can’t tell if the layout is broken or if the console is throwing errors. So I built a CLI that lets the agent open a browser, interact with the page, record what happens, and collect any errors. Then it bundles everything — video, screenshots, logs — into a self-contained HTML file I can review in seconds. proofshot start --run "npm run dev" --port 3000 # agent navigates, clicks, takes screenshots proofshot stop It works with…
Mar 2026 · github.com
- 5
- 6OS
Hi HN, I forked chromium and built agent-browser-protocol (ABP) after noticing that most browser-agent failures aren’t really about the model misunderstanding the page. Instead, the problem is that the model is reasoning from a stale state. ABP is designed to keep the acting agent synchronized with the browser at every step. After each action (click, type, etc), it freezes JavaScript execution and rendering, then captures the resulting state. It also compiles the notable events that occurred during that action loop, such as navigation, file pickers, permission prompts, alerts, and downloads,…
Mar 2026 · github.com
- 7
- 8
- 9
- 10OS
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
- 11
- 12WB
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
- 13TI
I'm an "ideas person" who messes around with AI on a low budget. I got tired of watching my tokens vanish and context windows filling up while agents fumbled around trying to find the right thing. Agents don't flail like they used to with shell tools, but there are still weak/blind spots and back-and-forth episodes — especially when using tools in combination/sequence. So I built "tilth" today. Or rather, AI built it — every line is Opus 4.6. I spent a lot of my precious tokens getting it to "not shit" (at least several of the different vendors' AI overlords assure me it's not…
Feb 2026 · github.com
- 14SR
Hello all, I'm a software developer. Over the last few months more and more of my work has turned into using coding agents instead of typing the whole code myself. Usually a few claude sessions at once, sometimes codex, one per feature or per revealed bug. I ran them in a split terminal for a few weeks, and quickly spotted two main problems. The first is that I couldn't easily tell which agent was stuck waiting on me and which was still working, so I'd cycle through sessions and checking on them. The second one: agents sharing a single branch step on each other. Two of them could be editing…
Jul 2026 · shikigami.dev
- 15
- 16
- 17
- 18
- 19
- 20
- 217D
hi all. i’ve been shipping a small open project that tries to answer that question with evidence, not vibes. in 70 days it reached \~800 stars. the core claim is simple: many AI failures are not noise. they repeat because the geometry and ordering underneath are stable. if so, we should be able to name each failure mode, set acceptance targets, and stop shipping the same bug twice. ### what it is * a compact Problem Map of 16 reproducible failure modes in RAG and agents. * each item has a minimal fix and measurable gates. examples: * Semantic ≠ Embedding: metric and normalization mismatch.…
2025 · github.com
- 22
- 23GB
Hey HN Community, I recently found myself knee-deep in a fascinating challenge that I think you'll find intriguing. I'm a backend developer with a penchant for Node.js and SQL, and I've been wrestling with a problem that's both technically intricate and surprisingly common in the world of open-source development. The issue at hand? Duplicate GitHub issues. They're like weeds in a garden – you turn your back for a second, and suddenly they're everywhere, choking out the valuable discussions and dragging down productivity. So, I set out to build a bot. Not just any bot, mind you, but a Probot…
2024 · github.com
- 24CA
I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!
Sep 2025 · infrastructureas.ai
Ranked by how close each launch is in meaning, then by votes. Refine with a description →