Secrets for AI coding agents

Your agents run the code. Your phone holds the keys.

sealctl keeps API keys, SSH keys and backup passwords off your disk. When an agent needs one, your phone asks, you tap Allow, and the key goes into that one command. The agent never sees it, and it never lands in a transcript or a .env file.

Start in two minutes

  1. Install the command line tool.

    brew install sealctl/tap/sealctl

    Other systems

  2. Get the phone app, then run sealctl pair and scan the code.

    iPhone · coming soon Android · coming soon

Free, no account.

$ sealctl run -- npm test
sealctl: OPENAI_API_KEY ← shop/openai-api-key
Waiting for your phone

> shop@1.4.0 test
> vitest run

 ✓ test/api.test.ts (12 tests)
 ✓ test/checkout.test.ts (7 tests)

 Test Files  2 passed (2)
      Tests  19 passed (19)
An agent runs the tests. sealctl names the key the command gets, waits for your phone, then runs it. Illustration built from the command line and app specs; it is replaced with output from a real run when the phone version ships.

WAITING · 0:12

Allow OPENAI_API_KEY?

For
npm test
In
~/dev/shop
From
dev@mbp.example.com · claude
Allow for this session Allow once Deny
The approval card, rendered from the app spec's text. A screenshot of the app replaces it once the app exists.

What sealctl does

Agents never see the key

The key goes into the environment of the one command that asked. Output is masked to ****, and reading a secret directly is refused inside an agent.

One tap, or none at your desk

The first approval of the day takes one tap. Back at the same desk, with your phone unlocked and on the same network, the session reopens by itself.

Locked when you leave

Keys live in memory for the session only. Leaving a trusted place, idle time or the 02:00 hard stop locks the machine and unmounts its volumes.

24 words on paper

Every key comes from 24 words you write by hand on a printed card. With them, sealctl recover opens anything sealctl sealed, with no phone or server.

Volumes and backups too

Encrypted APFS or LUKS volumes and restic backups open with the same words, mount with the session and lock with it.

Nothing goes missing silently

Your phone lists every key it hands out and every use. When you change the words, it shows what moved and what it couldn't find.

If we disappear, your keys don't.

Everything sealctl protects opens from your 24 words with the open-source command line tool. And sealctl unseal --all hands it all back under passwords of your own whenever you want to leave. No server, account or subscription stands between you and your data.

  • Open sourceCommand line tool under MIT, phone app under AGPL-3.0, protocol public: github.com/sealctl.
  • The relay sees sealed dataIt carries messages it cannot open. What it keeps.
  • Security reportsPrivate GitHub advisories, first answer within three working days. How to report.
  • Payments by PaddlePaddle is the merchant of record. We never see your card.
The card is printed blank and the words are written by hand. The app never prints, copies or screenshots them.

Free to use. $5.99 once if it earns its place.

The app, the command line tool and the relay are free. After 30 days with use, your terminal asks once a week. Paying changes nothing in the app.

  • Your employer can pay, with a VAT invoice.
  • Teams buy seats and share one code.
  • No subscription, no ads, no trackers.
$ sealctl buy
Who pays?
  1  Me             card, opens checkout
  2  My company     invoice with VAT ID, opens checkout
  3  Someone else   copies a payment link to send
Choose 1, 2 or 3: 2
sealctl buy as specified for the phone version. Nothing can be bought yet.