Why I built it
Developer secrets need strong local protection, while agent workflows introduce authority and disclosure risks a normal password manager does not solve.
What exists
The arm64 SwiftUI and Rust application has a verified signed Personal Team build with no observed network or automation surface. Agent brokering is not implemented.
How it works
A sandboxed native interface uses a statically linked Rust core and Keychain/file entitlements without a current socket, API, or agent-control surface.
- Local secrets storage
- Native SwiftUI interface
- Statically linked Rust core
- Signed arm64 build
My role
Designed the native and Rust boundary and the threat-model direction for narrowly scoped future approvals; directed the signing workflow and security checks, and reviewed and tested the implementation.
What I checked
- signingSigned arm64 Personal Team build verified
- securityNo network or automation surface observed
What stays bounded
- No agent broker exists today
- Agents do not receive real vault secrets
- Personal Team signing is not durable distribution
What is missing
- External review, durable distribution, recovery policy, and manual validation gaps remain.
Next
Complete a public-safe threat model without enabling real-vault access.
Later ideas, not current features
- Explore human-approved, operation-scoped credential access for developer and agent workflows
- Design replay prevention and revocation
- Use durable signing before any real trial