Roadmap

What’s available today, what’s coming, and what’s out of scope.

Available today

• One-command login — authenticate with any of 45+ providers in one step. Works in the browser, over SSH, and in CI.
• Headless credential access — agents get a valid token with a single CLI call. No browser, no prompt, no secrets in env vars.
• Automatic token refresh — tokens are silently refreshed before they expire. Agents never see an auth error.
• Zero-knowledge proxy — run any agent or script behind a local proxy that injects credentials at request time, without exposing them in environment variables or process args.
• Encrypted local vault — all credentials are encrypted at rest on your machine. No cloud account, no SaaS dependency.
• 45+ bundled providers — GitHub, Google, Linear, OpenAI, Slack, Notion, and more. Custom providers via a JSON file.
• Multi-tenant provider support — connect to GitHub Enterprise, self-managed GitLab, Okta, and other multi-tenant services with a custom --base-url at login time.
• Web dashboard — view and manage all your connections in a local browser UI.
• Audit log — a structured record of every credential access, login, and logout.
• Hosted daemon mode — deploy authsome on an internal server and point multiple machines at it.
• Agent integrations — drop-in setup guides for Claude Code, Codex, Cursor, LangChain, LlamaIndex, OpenAI Agents SDK, and Anthropic SDK.

Coming next

• Per-agent access control — decide which agents are allowed to use which credentials, without changing the agent itself.
• Proxy firewall rules — block or allow outbound requests at the proxy layer per agent and per service.
• Multi-user support — multiple users sharing a deployed daemon with proper credential isolation between them.
• Native MCP tool — use authsome as an MCP tool in any MCP-compatible agent, not just via the CLI.
• Homebrew — brew install authsome for macOS.

Considering

• GitHub Actions — inject credentials directly into CI workflows without running a daemon.
• Managed SaaS — hosted credential management for teams who don’t want to self-host. No timeline yet.
• Windows — first-class Windows support.

Deliberately out of scope

• A cloud secrets manager — Authsome is local-first by design.
• An enterprise identity platform — Authsome handles credentials, not employee directories or SSO.

Shape the roadmap

• Open an issue to report a bug or request a feature.
• Start a discussion to share an idea.
• Open a PR — adding a new provider is the most common contribution.

Changelog

Recent releases.

Compared to alternatives

Authsome vs hardcoded env tokens, SaaS secrets managers, and DIY.