Wirbelwind

5 ms·

1.
by Wirbelwind 1mo ago
That's a fair point. There were two main prompts that were controversial; cat .zshrc being benign for those who use separate env files, and npm run that's mostly benign. For npm run I added the evil payload in the history log shor
2.
by Wirbelwind 1mo ago
I think there are too many problems with HITL that even a simple experiment like this game shows. The fatigue causes people to jump to complete bypasses instead, and we need to work more on raising the general awareness of the new types of
3.
by Wirbelwind 1mo ago
A couple of months ago I shared the AI agent permission game here on HN. After adding in stats it got a little over 40k plays and 409k decisions since then. It's just a game, but I found the stats still interesting that I wanted to sha
4.
Humans missed 1 in 3 threats approving AI agent commands across 40k game runs(scalex.dev)
340 points by Wirbelwind 1mo ago|245 comments
5.
by Wirbelwind 4mo ago
that's a good callout. .internal is a reserved TLD so it shouldn't resolve publicly, but that's a good point about being wary of changing this while letting claude refactor a project for something that's best configured
6.
by Wirbelwind 4mo ago
thanks for the pointer! renamed it to npm ci so it's still 'safe'
7.
by Wirbelwind 4mo ago
that's a great point, and also the problem with relying on a human-in-the-loop to catch these kind of issues when it can be circumvented even if they were perfect
8.
by Wirbelwind 4mo ago
Good catch, this has now been nerfed and this approach has gotten its own title
9.
by Wirbelwind 4mo ago
and added! Made one for each stat separately
10.
by Wirbelwind 4mo ago
Thanks all for checking it out and your suggestions! If anyone is curious about the actual underlying risks and problems with some mitigations (like the 17% false-negative rates of Auto Mode), I wrote up a quick summary of some of the appro
11.
by Wirbelwind 4mo ago
That's a great idea, stay tuned
12.
Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue(llmgame.scalex.dev)
386 points by Wirbelwind 4mo ago|162 comments
13.
2 years with Shape-Up, and why we switched back(scalex.dev)
1 points by Wirbelwind 9mo ago|0 comments
14.
Simplifying Code: Migrating from Reactive to Virtual Threads(scalex.dev)
1 points by Wirbelwind 1y ago|0 comments
15.
Beyond the beep and saving sleep: optimizing the On-Call experience(scalex.dev)
1 points by Wirbelwind 3y ago|0 comments
16.
How to make software architecture trade-off decisions(medium.com)
1 points by Wirbelwind 5y ago|0 comments