guyb3

4 ms·

1. 1.▲
   by guyb3 1mo ago

   fair question and there are lots of overlap, here some diffs we found important for us - 1) the agent never holds your keys and all its traffic goes to onecli gateway. which adds the secret at the moment of the request. 2) our approval mech
2. 2.▲
   by guyb3 2mo ago

   It’s definitely a crowded space, totally agree about it. honestly for us we didn't want to commit to a specific provider, whether that's grok or openai. So we decided to go with a harness that lets us switch models easily when one
3. 3.▲
   by guyb3 2mo ago

   Honestly, we're not sure yet how we win this space. We both come from security backgrounds, and that's probably what led us to where we are today. basically we built the gateway first because we were afraid of using openclaw the w
4. 4.▲
   Launch HN: OneCLI (YC S26) – OSS sandboxed agent harness for teams(github.com)

   88 points by guyb3 2mo ago|37 comments
5. 5.▲
   by guyb3 7mo ago

   It's a good point, I don't think the placeholders we use will trigger a secret scanner, but we can adjust if it's an issue. https://github.com/onecli/onecli/blob/942cfc6c6fd6e184504e01...
6. 6.▲
   Show HN: OneCLI – Vault for AI Agents in Rust(github.com)

   161 points by guyb3 7mo ago|52 comments
7. 7.▲
   Show HN: ChartDB Agent – Cursor for DB schema design(app.chartdb.io)

   130 points by guyb3 1y ago|36 comments