amitbidlan

3 ms·

1. 1.▲
   by amitbidlan 5mo ago

   Glad the replay clicked for you. Honestly that was the thing I built before blocking, because I kept looking at agent failures with basically no clues. The trace view also made the firewall work well in practice: you can promote rules from
2. 2.▲
   by amitbidlan 5mo ago

   Sorry,I took out two things from the main post to make it shorter. 1. The reason I like local-first is that I do not want logs from tools and agents going to some company. With DuckDB everything stays on your system so you have control over
3. 3.▲
   Show HN: Korveo – a local firewall for AI agents(github.com)

   1 points by amitbidlan 5mo ago|3 comments
4. 4.▲
   Tracing and tenant-isolation firewall for AI agents (Apache 2.0)(github.com)

   1 points by amitbidlan 5mo ago|0 comments
5. 5.▲
   by amitbidlan 5mo ago

   Planning ahead, bulk processing, storing for later. Sounds less like primitive survival and more like logistics. Every time we dig deeper the gap between them and us gets smaller.
6. 6.▲
   by amitbidlan 5mo ago

   Mostly ASM for performance critical paths is a pattern that never gets old. The VideoLAN team did the same with dav1d and it paid off. Curious how much of dav2d ends up staying C as AV2 matures.
7. 7.▲
   by amitbidlan 5mo ago

   Jeeves was just too early — natural language queries in 1997, before anyone called it conversational AI.