Show HN: OneCLI – OSS credential gateway that keeps secrets out of AI agents(github.com)
54 pointsby Jonathanfishner5 hours ago14 comments
  • sandeepkd3 hours ago
    It works great for static credentials. As a product I think about adding couple more things that might be helpful here (Btw I am not the client for this, I just happen to know them as practical problems)

    1. Support for OAuth Client credentials - Gateway does the OAuth dance to get the access token, this is quite practical and even useful in case of regular services running across clusters and sharing the same clientId-secretId

    2. Support for request retries on certain failures and short circuiting in other cases

    • Jonathanfishner2 hours ago
      thanks, both are useful.

      1. we support OAuth apps today, and we're growing the catalog based on demand. we support rotating and refreshing tokens for those.

      2. I'd like to understand your case better. sitting in the request path means we could own retry mechanisms, but I'm curious what made you think of it, what kind of use cases did you have in mind?

      • sandeepkd2 hours ago
        Almost every API caller has to add the logic for retries based on the response codes, centralizing it with the gateway optimizes the repetitive code across the clients.

        Trip breaker patterns are good for resource usage on both sides (client and server) when you know things are not working. In addition to that it also saves on cost for the clients if every call is billed irrespective of success or failure.

  • osinix21 minutes ago
    This is the same old good way from database world. A db client never touches the disk, but sends requests to a server who owns it. Same in your product. Keys are separated from agents and if needed, agents must send request to a proxy who owns them. Old proven design. Good luck.
  • emilsomanan hour ago
    How does it compare to agent-vault and clawpatrol?
  • redbridgerock2 hours ago
    Oo this is interesting, blocking it on the network level is nice
  • oliver23627 minutes ago
    why not just use 1password
  • doctorpangloss3 hours ago
    does the agent control the environment that onecli is running in? (yes)
    • Jonathanfishner2 hours ago
      yes the agent controls its environment which is exactly why nothing sensitive should live there. The gateway and the real secrets sit outside the sandbox. that said, not holding the secrets doesn't make the agent harmless. It still acts autonomously, and it can use whatever access those credentials grant. do you see the second half as the bigger risk? curious how people are thinking about it.
  • stephantul2 hours ago
    It is hilarious to see most comments are people peddling their own products more or less directly.
    • rvzan hour ago
      This is what happens when building software goes to 0.

      "Build it and they will come" now works well for competition:

      - If you build it (and it is not useful) they won't come.

      - If you build it (and it is useful and successful) they will come and copy you to build their own.

  • notaharvardmba3 hours ago
    oauth, saml, oidc accomplish the same thing in a way more mature way, so if you’re already using SSO just do that instead of adding another point of failure..
    • mjg593 hours ago
      No they don't - you're still giving the agent a static token that can be exfiltrated and used elsewhere.
      • hmokiguessan hour ago
        doesn't the token has an expiry window though? if you're using oidc/sso with aws for example it is short lived and can be revoked
  • frank-bee21 minutes ago
    [flagged]
  • winterrx3 hours ago
    nice launch. i have started to use a secrets manager (infisical) recently for my different projects and it's been really helpful. are your customers solo hackers, small startups or large enterprises that are looking for this kind of solution? i like to see competition in the space
    • aliasxneo21 minutes ago
      Curious how you justify their pricing? Last I checked the $/identity extended to machine accounts which absolutely blew my mind.
    • bstsb3 hours ago
      +1 on infisical. brilliant self-hosted offering, i love their CLI and it works well with CI pipelines
  • denysvitali3 hours ago
    Nice! I've built something like this, although specific to GitHub: https://github.com/denysvitali/gh-proxy

    The idea being that if the fake token leaks from my sandbox - it would be completely useless for an attacker

  • rahulr06093 hours ago
    +1 to Infisical.

    We added Hashicorp Vault support here: https://github.com/Infisical/agent-vault/pull/256

  • theozero3 hours ago
    Looks great. The "credential broker" pattern (inject placeholders, replace in proxy) is something we just added to https://varlock.dev (totally free and open source).

    Rather than using a dashboard, ours is configured within a .env.schema file, and rather than our own vault, we can pull secrets using our plugins (16 and counting) including Infisical, 1Password, Bitwarden, AWS, GCP, Azure, more. Also very useful for coding tasks in general, as we have integrations for most frameworks, and add built in validation, type safety, leak detection, etc.

    Will definitely be keeping an eye on OneCLI to compare notes.

  • adithyassekhar3 hours ago
    Holy mother of whatever this is, everyone got the same idea again and there’s a bunch of implementations people are desperate to promote in the comments.

    You’re just trading one key for another, whatever abstraction you chose to trust, at some point credentials will pass to your llm of the week.

    • mjg593 hours ago
      > at some point credentials will pass to your llm of the week.

      How?

    • theapiartist3 hours ago
      I happen to know a solution where credentials wouldn't get to the agent. It's structurally impossible