alt.hn

7/23/2026 at 3:42:40 PM

Show HN: OneCLI – OSS credential gateway that keeps secrets out of AI agents

 https://github.com/onecli/onecli

by Jonathanfishner

7/23/2026 at 5:55:18 PM

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

by sandeepkd

7/23/2026 at 6:09:46 PM

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?

by Jonathanfishner

7/23/2026 at 6:52:41 PM

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.

by sandeepkd

7/24/2026 at 2:15:44 AM

got it. we have not heard that need from users yet, but, can def see it being usefule as a fallback mechanism, since we are already sit at this network proxy layer.

what type of calls are you aiming to? can share example of that "call is billed.." is that specific apps you have in mind?

by Jonathanfishner

7/24/2026 at 2:49:00 AM

Also it would be nice to support browser cookies and flows too.

by Onavo

7/23/2026 at 7:37:30 PM

How does it compare to agent-vault and clawpatrol?

by emilsoman

7/23/2026 at 11:35:23 PM

MITM is a feature now.

by vayup

7/23/2026 at 5:12:12 PM

does the agent control the environment that onecli is running in? (yes)

by doctorpangloss

7/23/2026 at 5:59:07 PM

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.

by Jonathanfishner

7/23/2026 at 6:15:26 PM

Oo this is interesting, blocking it on the network level is nice

by redbridgerock

7/23/2026 at 8:04:27 PM

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.

by osinix

7/24/2026 at 6:08:12 PM

What happens if the "fake" key gets compromised?

by trallnag

7/25/2026 at 3:54:02 PM

love it

by chaandannn

7/23/2026 at 6:14:30 PM

It is hilarious to see most comments are people peddling their own products more or less directly.

by stephantul

7/23/2026 at 7:01:45 PM

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.

by rvz

7/23/2026 at 5:25:31 PM

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

by notaharvardmba

7/23/2026 at 5:30:57 PM

No they don't - you're still giving the agent a static token that can be exfiltrated and used elsewhere.

by mjg59

7/23/2026 at 7:16:51 PM

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

by hmokiguess

7/23/2026 at 8:54:06 PM

The refresh token is often going to be good for a week, even if the access token isn't.

by mjg59

7/23/2026 at 5:23:06 PM

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.

by adithyassekhar

7/23/2026 at 5:31:29 PM

> at some point credentials will pass to your llm of the week.

How?

by mjg59

7/23/2026 at 5:34:01 PM

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

by theapiartist

7/23/2026 at 10:08:19 PM

I know one, too.

by throw1234567891

7/24/2026 at 7:40:00 AM

Do tell

by theapiartist

7/26/2026 at 4:59:11 PM

[flagged]

by chandankarn

7/25/2026 at 9:31:31 AM

[dead]

by entity002

7/23/2026 at 4:58:56 PM

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

by winterrx

7/23/2026 at 5:01:37 PM

+1 on infisical. brilliant self-hosted offering, i love their CLI and it works well with CI pipelines

by bstsb

7/23/2026 at 8:04:59 PM

Curious how you justify their pricing? Last I checked the $/identity extended to machine accounts which absolutely blew my mind.

by aliasxneo

7/23/2026 at 10:35:49 PM

If you want fully free and open source enterprise features you're better off going to OpenBao

by aiman_alsari

7/26/2026 at 2:30:47 AM

[flagged]

by oyadoti

7/23/2026 at 8:04:38 PM

[flagged]

by frank-bee

7/24/2026 at 1:04:52 PM

[flagged]

by gdemartino

7/24/2026 at 7:25:56 PM

[flagged]

by wulfkaal

7/25/2026 at 6:23:27 AM

[flagged]

by tancoai_dev

7/23/2026 at 5:19:36 PM

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.

by theozero

7/24/2026 at 12:22:03 PM

[flagged]

by chris_fa__

7/24/2026 at 10:23:07 AM

[flagged]

by russelmelroy

7/24/2026 at 10:00:24 AM

[flagged]

by jules_sarah088

7/24/2026 at 12:32:08 PM

[dead]

by feiz45607

7/23/2026 at 5:17:52 PM

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

by denysvitali

7/24/2026 at 11:32:54 AM

[dead]

by felixlu2026

7/23/2026 at 7:58:42 PM

why not just use 1password

by oliver236

7/24/2026 at 3:27:53 AM

[dead]

by Jonathanfishner