edf13

6 ms·

31.
Five AI Agent Failures in 36 Days. Zero Times the Agent Caught It(grith.ai)
3 points by edf13 5mo ago|1 comments
32.
by edf13 6mo ago
Manually review the package and override the setting
33.
by edf13 6mo ago
Anyone know of a similar tool to conductor for Linux?
34.
by edf13 6mo ago
Hand written I’m afraid… regular comments on this topic is true - it’s an area I’m very interested in.
35.
by edf13 6mo ago
Yes, true ;)
36.
by edf13 6mo ago
We are Open Source… code will be published soon (before launch)
37.
by edf13 6mo ago
Yes, fair point. Feedback accepted, thanks!
38.
The Vercel Breach Needed Malware. The Next One Needs a Bad Readme(grith.ai)
1 points by edf13 6mo ago|3 comments
39.
by edf13 6mo ago
Related: https://news.ycombinator.com/item?id=47803847
40.
Every Claude 4.7 Improvement Makes the Security Problem Worse(grith.ai)
5 points by edf13 6mo ago|1 comments
41.
They Hacked Claude, Gemini, and Copilot (and No One Told You)(grith.ai)
4 points by edf13 6mo ago|0 comments
42.
They Hacked Claude, Gemini, and Copilot (and No One Told You)(grith.ai)
3 points by edf13 6mo ago|0 comments
43.
by edf13 6mo ago
Seems to be a very regular occurrence starting around this time of day (14:30 UTC)... Claude Code returning: API Error: 500 {"type":"error","error":{"type":"api_error","message":&
44.
Prompt Injection Is Unfixable (So We Stopped Trying)(grith.ai)
4 points by edf13 6mo ago|1 comments
45.
by edf13 6mo ago
Building grith (grith.ai) - a security proxy for AI coding agents enforced at the OS syscall level. The problem: agents like Claude Code, Codex, and Aider execute file reads, shell commands, and network requests with your full system privil
46.
by edf13 6mo ago
> And really, for what? Readership, clicks and views
47.
If Your AI Agent Ran NPM Install During the Axios Attack, You're Compromised(grith.ai)
5 points by edf13 6mo ago|0 comments
48.
Zero Ambient Authority: The Principle That Should Govern Every AI Agent(grith.ai)
3 points by edf13 6mo ago|0 comments
49.
Alibaba's AI Agent Hijacked GPUs and Dug Reverse SSH Tunnels(grith.ai)
3 points by edf13 6mo ago|0 comments
50.
by edf13 6mo ago
I’m going to take a look today!
51.
by edf13 6mo ago
Or perhaps we end up where all software is self evolving via agents… adjusting dynamically to meet the users needs.
52.
by edf13 6mo ago
Nice - I do something similar in a semi manual way. I do find Codex very good at reviewing work marked as completed by Claude, especially when I get Claude to write up its work with a why,where & how doc. It’s very rare Claude has fully
53.
by edf13 6mo ago
Good write up… I’ve found Claude in particular to be very good at this sort of thing. As for whether it’s a good thing, I’d say it’s a net positive - your own reporting of this probably saved a bigger issue! We wrote up the why/what ha
54.
by edf13 6mo ago
Congrats on the film use! It’s really interesting to read how you’ve captured and created these images… will follow your work!
55.
Claude now decides what's safe to run – a UX improvement, not a security fix(twitter.com)
3 points by edf13 7mo ago|0 comments
56.
AI agents are now deciding what's safe to run (Claude Auto Mode)(grith.ai)
3 points by edf13 7mo ago|0 comments
57.
by edf13 7mo ago
Author here. The point of this post is not “LiteLLM was compromised” since that was already covered on HN, but the chain behind it. We tried to connect the February 27, 2026 Trivy CI compromise to the later Trivy release/tag issues, th
58.
The Trivy Supply Chain Attack Reached LiteLLM(grith.ai)
3 points by edf13 7mo ago|1 comments
59.
Meta's Rogue AI Agent Gave Engineers Access They Shouldn't Have Had(grith.ai)
1 points by edf13 7mo ago|0 comments
60.
Meta's Rogue AI Agent Gave Engineers Access They Shouldn't Have Had(grith.ai)
3 points by edf13 7mo ago|0 comments

More ›