1 points | by amitbidlan 6 hours ago ago
2 comments
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 it.
2. I want to be honest about something. Korveo is between the agent and the tools it uses.
If the agent itself is compromised it can still get around Korveo.
So Korveo is, like a guard that helps keep things safe. It also keeps a record of what happens.
It is not a solution but it helps.
I am happy to talk about how Korveo works with policies or how it supports certain frameworks if people want to know more about Korveo.
The replay thing is what got me. Most of these tools just block stuff and leave you guessing why an agent did what it did. You mentioned the rule language isn't great — what's tripping you up on it?
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 it.
2. I want to be honest about something. Korveo is between the agent and the tools it uses.
If the agent itself is compromised it can still get around Korveo.
So Korveo is, like a guard that helps keep things safe. It also keeps a record of what happens.
It is not a solution but it helps.
I am happy to talk about how Korveo works with policies or how it supports certain frameworks if people want to know more about Korveo.
The replay thing is what got me. Most of these tools just block stuff and leave you guessing why an agent did what it did. You mentioned the rule language isn't great — what's tripping you up on it?