v0.11.0
·
182 commits
to master
since this release
Remote Agent profiles now support Personal Credentials: account-owned credentials that remain private and are resolved only by Agent Proxy sessions.
Highlights
- Add
[personal_credentials.*]bindings for Remote Agent sessions. - Support profiles containing secrets, Personal Credentials, or both.
- Personal Credential-only profiles do not require a project, environment, or local file.
- Generate identical Agent Proxy placeholders and MCP authorization headers for secret and Personal Credential bindings.
- Improve binding validation, policy output, and profile summaries.
- Reject local runs that include Personal Credential bindings with a clear validation error.
Configuration update
Project and environment identifiers now belong under [secrets]:
[secrets]
project = "project"
environment = "environment"
[secrets.GITHUB_TOKEN]Use Personal Credentials for account-owned Remote Agent credentials:
[personal_credentials.LINEAR_API_KEY]
[[personal_credentials.LINEAR_API_KEY.rules]]
effect = "allow"
hosts = ["mcp.linear.app"]
methods = ["GET", "POST"]
paths = ["/mcp"]Personal Credentials work only with stashbase agent run --remote. The CLI never fetches, prints, exports, or stores their raw values.