Stashbase

Personal Credentials

Use account-owned credentials in remote Agent Proxy sessions

Personal Credentials are account-owned credentials resolved by Stashbase for the authenticated user. They are private to that account and are available only in remote Agent Proxy sessions.

Configure them under [personal_credentials.<binding>]. They use the same HTTP policy and injection fields as secret bindings:

.stashbase/agents/coding.toml
egress_hosts = ["api.openai.com"]

[personal_credentials.LINEAR_API_KEY]
env = "LINEAR_API_KEY"

[[personal_credentials.LINEAR_API_KEY.rules]]
effect = "allow"
hosts = ["mcp.linear.app"]
methods = ["GET", "POST"]
paths = ["/mcp"]

Start the profile remotely:

stashbase agent validate --remote --profile coding
stashbase agent run --remote --profile coding -- codex

Personal-Credential-only profiles do not need project, environment, or file. They can also be combined with shared [secrets.<binding>] bindings. A remote session must contain at least one Stashbase-managed secret or Personal Credential; policy-only profiles cannot be used with --remote.

Personal Credentials are never fetched, printed, exported, persisted, or logged by the CLI. The remote Agent Proxy resolves them only for approved requests. Service API keys cannot be used for sessions that contain Personal Credentials, and Personal Credential access must be enabled for the workspace.

See Credential rules for host, method, and path matching.