Local-first credential broker and vault for AI Agents
Docs · Website · Discord · Issues
An open-source credential broker that sits between your agents and the services they call. Instead of sharing credentials with every agent, log in once via OAuth2 or API keys. Authsome stores credentials securely and injects them via an HTTP proxy. You get one place to manage access, rotate keys, and see what every agent is doing.
44 bundled providers out of the box: 13 OAuth2 and 31 API key. See the full list.
demo.mp4
Agents run beyond interactive sessions. They live in CI, over SSH, in cron jobs, in background workers, and in parallel pipelines. They need API access that survives without a human in the loop.
Hardcoded environment tokens leak or go stale, and building auth flow logic, token storage, refresh handling, and per-provider config into every project rebuilds the same plumbing every time.
Authsome is the local credential layer agents call at runtime.
- No credential sprawl. One encrypted store. Every provider, every agent, one place.
- No SaaS, no privacy trade-off. Credentials never leave your machine. Eliminates credential exfiltration risks as agents never see them.
- No browser required at runtime. Setup can use browser PKCE, device code, or a browser bridge for secure API key entry. After that, agents run headlessly.
The CLI is the agent's interface: setup once, then inject fresh credentials whenever a tool runs.
Authenticate once:
uvx authsome login githubThen agents get valid credentials on demand:
uvx authsome get github --field access_token --show-secret
# → ghu_...
export $(uvx authsome export github)
# → sets GITHUB_ACCESS_TOKEN in current shell
uvx authsome run python my_agent.py
# runs behind a local auth proxy that injects headers at request time
# without exposing secrets in the child process environment.
# matched automatically via provider api_url (e.g. api.openai.com)Credentials are stored locally, encrypted at rest, and refreshed before expiry. No server. No account. No cloud.
| authsome | Hardcoded env tokens | DIY | |
|---|---|---|---|
| Automatic token refresh | ✅ | ❌ | build it |
| OAuth2 + API keys | ✅ | ❌ | build it |
| Runtime headless use | ✅ | ✅ | varies |
| Local, no SaaS dependency | ✅ | ✅ | ✅ |
| Built-in providers, zero config | ✅ | ❌ | ❌ |
| Multi-account per provider | ✅ | ❌ | build it |
Authsome gives agents one command for a valid token, without scattering long-lived secrets across every project.
Requires Python 3.13+.
pip install authsomeOr run without installing:
uvx authsome@latest --helpuvx authsome login github # opens browser, completes PKCE flow
uvx authsome login github --flow device_code # headless: Device Code, works over SSH and CI
uvx authsome login openai # secure API key entry via browser bridge
uvx authsome list # all connections + token statusAuthsome ships with adapters for the most common agent frameworks and CLIs:
Full list at authsome.agentr.dev/docs/integrations.
Full documentation lives at authsome.agentr.dev/docs.
To preview the docs site locally:
cd docs/site
npm i -g mint # requires Node.js >= 20.17.0
mint dev- Discord for questions, help, and showing what you're building.
- GitHub Issues for bugs and feature requests.
Authsome is a credential tool. If you find a vulnerability, please do not open a public GitHub issue.
See the responsible disclosure policy for how to report it privately.
Contributions welcome. See CONTRIBUTING.md for development setup, testing, and the engineering principles we follow.
MIT. See LICENSE.