Skip to content
New in 0.13hush push sends a key to where your app runs

Secrets your AI agentcan use but never read.

Your keys live encrypted in the repo. hush npm run dev hands them to that one process — your coding agent can run it, and only ever sees [redacted:KEY]. No server, no account, no shared password.

Get started
$npm i -g @omarei/hush

macOS, Linux and Windows (beta) · zero dependencies · MIT · other ways to install

127.0.0.1:4455

That is the app itself — the page hush ui opens on your machine — running here on made-up keys. Suggestions, groups, the agent's activity: click around.

Works with the coding agents you already use, through MCP

How it works

Your agent asks. You approve. It never sees a value.

CC
Claude Code
Cx
Codex
Cu
Cursor
hush
asks you first, on your screen
npm run dev
api.stripe.com
Cloudflare
01

Keys live encrypted in your repo

.hush/vault.json holds ciphertext and public keys, so you commit it. Your own key never leaves your machine — on a Mac it is in the Keychain.

02

Your agent names a key

Through hush's MCP tools it runs a command with your keys, calls an API with one, or sends one to a host. No tool ever returns a value.

03

You approve, on your screen

A native dialog, or Touch ID — never a message in the chat. The process gets the value; the transcript gets [redacted:KEY].

In your terminal

Five commands. Then it gets out of the way.

  1. hush init acme

    A vault in .hush/vault.json: ciphertext and public keys, safe to commit.

  2. hush add .env --as Dev

    Your existing secrets, encrypted, as a set. Then delete the .env.

  3. hush npm run dev

    The keys go into that one process, never onto disk. Its output is masked.

  4. hush team add sam hush_pk_…

    Commit, and Sam can decrypt. No server, no invite email.

  5. hush team rm sam

    Re-keys the vault, re-seals every value, and lists what to rotate.

Or skip all five: hush start finds your keys, asks a few questions, and sets the project up — or let your coding agent do it.

~/code/acme — zsh
✓ vault acme created at .hush/vault.json
This file is safe to commit — it holds only ciphertext and public keys.
✓ stored 2 secret(s) as Dev (dev) in this project
hush: using default, dev
connecting with [redacted:OPENAI_API_KEY]
✓ sam can now decrypt this vault
commit .hush/vault.json and they are in — no server, no invite email
✓ removed sam
new key generation 2; re-sealed 2 value(s)

What you get

Everything a .env did, without the plaintext.

The vault is a file in your repo

Each value is sealed on its own, with age's construction rebuilt on node:crypto. Key names stay readable, so a diff shows which key changed — never what to. The header is signed, and only an admin's signature changes who can read it.

.hush/vault.jsoncommitted
"envs": { "dev": {  "OPENAI_API_KEY": { "ct": "k6egPny2o9uFHSkiJzcUOWUZ…" },  "STRIPE_SECRET_KEY": { "ct": "k6egPny2o9uFHSkiJzcUOWUZ…" },  "DATABASE_URL": { "ct": "k6egPny2o9uFHSkiJzcUOWUZ…" },} },"signature": { "by": "99b889e5…", "sig": "rzm9ulD4…" }

Asked first, with your finger

Anything that uses a key asks on your own screen — a native dialog, or Touch ID on a Mac. Text in a chat can't click it.

hush wants to run npm test

for Claude Code, in acme-api, with 9 keys. Touch ID to allow.

Tools your agent can use, not read

hush's MCP server gives Claude Code, Codex, Cursor and the rest tools that name a key. None of them returns its value.

hush_list_sets
6 sets · names, never values

A teammate is one command

Everyone has a key pair. Adding someone wraps the vault's key for them; removing them re-encrypts every value and lists what to rotate.

alalexadmin
sasammember
prpriyamember · just now
$ hush team add priya hush_pk_9vRw…

Nothing beside it

No server to run, no account to make, nothing in node_modules: one binary, or one npm package.

0
runtime dependencies
0+
tests, and counting
0
file to install

Send keys where your app runs

hush push sends a key to 14 hosts through their own CLIs — on stdin, never on a command line — and refuses a value a CLI would quietly change. When you replace a key, the app tells you where it still needs to go. How it works

Cloudflare WorkersCloudflare PagesVercelConvexFly.ioRailwayFirebase Functions
Cloudflare WorkersCloudflare PagesVercelConvexFly.ioRailwayFirebase Functions
Cloudflare WorkersCloudflare PagesVercelConvexFly.ioRailwayFirebase Functions
Cloudflare WorkersCloudflare PagesVercelConvexFly.ioRailwayFirebase Functions
GitHub ActionsGitLab CI/CDGoogle Cloud Secret ManagerKoyebFastly Secret StorePulumiSST
GitHub ActionsGitLab CI/CDGoogle Cloud Secret ManagerKoyebFastly Secret StorePulumiSST
GitHub ActionsGitLab CI/CDGoogle Cloud Secret ManagerKoyebFastly Secret StorePulumiSST
GitHub ActionsGitLab CI/CDGoogle Cloud Secret ManagerKoyebFastly Secret StorePulumiSST

Status: early

Heavily tested. Not yet reviewed. Honest about both.

hush is pre-1.0, it has one author, and it has not had an external security review. The crypto is a standard construction — age's — rather than anything invented here, with a differential test suite against an independent reimplementation. That is not the same as someone qualified having looked at it.

Install

One file. Then hush start.

$curl -fsSL https://raw.githubusercontent.com/omarei-omoto/hush/main/scripts/install.sh | sh

One file, no Node needed. Installs to ~/.local/bin without sudo.

The installer refuses a binary whose sha256 is not the release's, and checks its build provenance when the GitHub CLI is signed in. Then, in your project, hush start finds your keys, gets them in, and asks whether an AI assistant will be near them.

Give your agent the keys.
Not the secrets.