Topic
#credentials
Loot, blog posts and adjacent themes connected to this topic. Follow the tag to keep it in your orbit.
Loot
More from this topic
OneCLI is an open-source credential gateway that lets agents call services through placeholder keys while the gateway injects real secrets at request time. OneCLI is worth evaluating if your agents need API access but you do not want raw keys sitting in prompts, project files, shell history, or agent memory. What it is OneCLI is an open-source credential gateway with a built-in vault. You store real API credentials once, give an agent a placeholder key, and route outbound HTTP calls through OneCLI. The gateway matches the target host and path, decrypts the right secret, and injects it into the request so the agent never sees the real credential. The repository describes a Rust gateway, a Next.js dashboard, AES-256-GCM encrypted storage, host/path matching, per-agent access tokens, and optional Bitwarden-style vault integration. Who it helps Use it when you are experimenting with Codex-style agents, Claude Code, MCP tools, local automations, or internal agent workflows that need to touch multiple APIs. The cleanest fit is a local or small-team setup where credential exposure is the main risk and you want one place to rotate keys, scope agent access, and inspect what each agent is doing. How to evaluate it Start in a throwaway local workspace. Read the README, inspect the Docker compose setup, review how secrets are encrypted, and test with a non-critical API token first. Confirm whether the gateway behavior fits your agent stack before connecting production accounts. Limits and risks OneCLI reduces direct key exposure, but it does not make an unsafe agent safe. A compromised or prompt-injected agent may still call allowed services through the gateway. You still need scoped API keys, logging, rate limits, approval gates for destructive actions, and a clear rotation plan. The HTTPS interception model also deserves careful review before team or production use. Access and pricing The visible repository is open source under Apache-2.0. The project also links to a website and docs; check the current hosted or team offering separately if you need managed deployment. Sources OneCLI GitHub repository OneCLI website
Free
Review open
Vercel's Chat SDK now supports Vercel Connect, letting bot builders use connector-backed Slack, GitHub, and Linear credentials instead of storing long-lived tokens and signing secrets in their own app. Use Vercel Connect to stop storing bot tokens in Chat SDK projects Vercel Connect support in Chat SDK is worth bookmarking if you build bots that talk to Slack, GitHub, or Linear. The practical win is credential handling: @vercel/connect/chat returns adapter helpers that use connector UIDs, fresh short-lived tokens, and OIDC-verified inbound triggers instead of app-managed token storage. Best fit Use case Why it helps Caveat --- --- --- Slack bots on Vercel connectSlackAdapter() can feed credentials into the Slack adapter. Vercel Connect is still beta. GitHub or Linear workflow bots Connector-backed auth reduces manual token rotation work. Check connector availability for your account. Inbound bot events Vercel documents trigger forwarding with OIDC validation. Review event scope and permissions before production use. What to check first Confirm your project can use Vercel Connect and the needed connector. Review the @vercel/connect/chat adapter helper docs. Keep least-privilege scopes on Slack, GitHub, and Linear connectors. Test inbound trigger verification before trusting production events. Read the beta terms, because connector behavior can change before GA. Practical LinkLoot angle This is not broad platform news, but it is a useful security and maintenance shortcut for bot projects. If your Chat SDK bot currently stores tokens or webhook signing secrets, test Vercel Connect in a staging deployment and compare the operational surface: fewer secrets, shorter-lived outbound credentials, and a standard verification path for inbound events. Source check Vercel's July 8, 2026 changelog confirms Chat SDK support for Vercel Connect and the @vercel/connect/chat subpath. The Chat SDK documentation explains setup, connector UIDs, adapter helpers, outbound token handling, and inbound webhook verification.
Free
Review open
Blog