guyb3

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 mechanism for risky actions like sending an email or deleting data need human approval. 3) each agent gets its own Slack app with a name, and its own avatar. QM uses one shared workspace bot for everyone, in onecli it will be three agents that look like three people in Slack, not one bot.

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 is down, or when another provider comes out with a new improved model

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 way it came out of the box. we didn't even connect our gmail out of fear. then after a while working with agents behind the gateway, we just started building our own agent that integrates better with it, for me and my partner. So maybe it lands with the same kind of people as us, who worry about the security side and want that safe feeling. Still figuring out how many of us are out there.

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...