Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
benban
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
1.
▲
Show HN: I pointed 11 cold AI agents at my own product. 3 finished
(pact0.com)
3 points
by
benban
15d ago
|
0 comments
2.
▲
by
benban
6mo ago
Fair, but the top ~20 repos in the sample have 25K+ stars each.
3.
▲
Scanned 500 AI agent repos for bugs, nobody thinks of infinite loops
(inkog.io)
3 points
by
benban
6mo ago
|
1 comments
4.
▲
by
benban
7mo ago
This makes sense for OpenAI, my experience with Promptfoo is great at testing model outputs. But I keep wondering who's looking at the other side: the actual agent code, and what happens now for other models such as Gemini/Claude
5.
▲
OpenAI Acquires Promptfoo
(openai.com)
3 points
by
benban
7mo ago
|
1 comments
6.
▲
by
benban
7mo ago
I would also recommend checking out https://inkog.io as well, looks at similar patterns and you can run it directly in the browser and get results in 60s, it also builds an agent topology and check for "human in the loop&qu
7.
▲
by
benban
7mo ago
Interesting that NIST is pushing for machine-readable behavioral declarations for agents. Basically an SBOM equivalent — agents declaring what tools they can access and what they can't do. RFI responses due March 9, concept papers Apri
8.
▲
NIST Launches Standards Initiative for AI Agents
(nist.gov)
1 points
by
benban
7mo ago
|
1 comments
9.
▲
by
benban
7mo ago
Honestly yeah – static catches structural stuff (missing exit conditions). But the trickier loops are when the model keeps deciding to retry. Like "let me try one more search" forever. That's prompt behavior, need runtime tra
10.
▲
Show HN: Inkog – Pre-flight check for AI agents (governance, loops, injection)
(inkog.io)
1 points
by
benban
7mo ago
|
2 comments
11.
▲
by
benban
8mo ago
the point about this being an os problem not an ai problem resonates. letting untrusted agents drive your browser smells like a problem to me. in practice we've had better luck running agents in lightweight sandboxes with explicit capa
12.
▲
by
benban
8mo ago
nice work. the idea of breaking agents into short-lived executors with explicit inputs/outputs makes a lot of sense - most failures i've seen come from agents staying alive too long and leaking assumptions across steps. curious ho