CC Safety Net
A coding agent CLI safety layer that blocks destructive git and filesystem commands and secret file access before execution.
Secretariat captures API keys from the clipboard or a screenshot, keeps them in your iCloud keychain, and lets your coding agents run your tools with them without ever reading them. Screenshots are re
SecuritySwift · HTMLGitHub @moinsen-devOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Your coding agents use your keys. They don't get to read them. Mac app + CLI for API keys, source-available (PolyForm Strict).
Loading the full README.
Read the full README ↗Your coding agents use your keys. They don't get to read them.
Secretariat is a native Mac app with a command line tool. API keys live in your iCloud keychain; Claude Code, Codex, OpenCode and other agents start your tools through secretariat run, so the program gets the values and the agent sees [masked]. It also captures keys from the clipboard or a screenshot, guards commits and agent commands, hands MCP tokens to Claude Code without plain text, logs who used which key, and backs up everything sealed to a recovery key only you hold.
Website, download and price: https://secretariat.moinsen.dev · What it protects and what it doesn't: threat model
So you can check what a tool that holds your keys actually does, instead of taking our word for it.
Sources/SecretariatCore (vault, keychain, CLI, masking, guard, history, backup) and Sources/Secretariat (the app).Tests/SecretariatCoreTests. Run them with xcrun swift test (Xcode's toolchain; a swift.org toolchain on the PATH lacks the macOS frameworks).PLAN.md lists requirements and acceptance criteria, TRACKER.md the evidence per task. The evidence reports (docs/t0xx-evidence.md) say what was run and observed, including what was not tested. New features are reviewed by a separate reviewer agent with a fresh context before release; its findings and our fixes are in docs/review-*.md. These are our own checks, not an outside audit.docs/release-*.md record build, notarization and distribution for each version.Source-available under the PolyForm Strict License 1.0.0: you may read and audit the code and use it for noncommercial purposes. You may not distribute it or make modified versions. Commercial use needs a Secretariat license, which also gets you the signed, notarized build and all 1.x updates.
Building from source as-is will not get you a working app: keychain access, iCloud sync and the CLI inside the bundle depend on the developer's signing identity and provisioning profile.
Ulrich Diedrichsen, Hamburg · [email protected] · https://www.moinsen.dev
Found a security problem? Please write to [email protected] before opening a public issue.