How it works
One tap in the morning. Keys only where they're used.
This page describes the phone version of sealctl (0.7), which is in development. Screens are rendered from the app and command line specs until real screenshots exist.
1. The approval
An agent runs a command that needs a key. The machine asks your phone. The phone shows who asks: the agent, the repository, the command, user@host and the key.
You tap Allow. The phone derives the key, seals it to that one request and sends it back. The key goes into the command's environment and stays in the machine's memory for the session. The agent's view of the output is masked: values print as ****.
An agent's first use of a key in a repository asks once, and the answer is remembered for that agent, key and repository. You at the keyboard are never asked inside an open session.
WAITING · 0:12
Allow OPENAI_API_KEY?
- For
- npm test
- In
- ~/dev/shop
- From
- dev@mbp.example.com · claude
First use of this key by claude in shop. Allow is remembered.
2. Your day
One tap in the morning covers a workday with three hours of meetings. Lunch outside costs one tap, or none when you return to the same desk with the phone unlocked.
| Time | What happens | Session |
|---|---|---|
| 09:00 | Unlock the phone, one tap | Open, allowance 30 minutes |
| 09:00 to 11:00 | Coding with agents | Allowance reaches 4 hours |
| 11:00 to 14:00 | Meetings in the building | Open |
| 14:00 | Lunch outside; the phone leaves the place | Locked, credit kept |
| 15:00 | Back at the desk | Reopens on its own, allowance 4 hours |
| 19:00 | Go home | Locked |
| 02:00 | Hard stop | Credit resets |
The idle allowance is 30 minutes plus 2 minutes per minute worked today, up to 4 hours at a trusted place and 10 minutes elsewhere. The hard stop is 02:00 or 14 hours after the first approval, whichever comes first. Screen lock and sleep keep the session; sealctl lock or Lock on the phone ends it at once.
3. States and asking
| State | Means | Where you see it |
|---|---|---|
| Locked | No keys in memory; volumes unmounted | Phone list, sealctl status |
| Open | Keys in memory; you and known agents use them without asking | Phone list with time left, sealctl status |
| Waiting | A request is on the phone | One terminal line, "Waiting for your phone", which the agent reads too; it gives up after 5 minutes |
| Level | When | You do |
|---|---|---|
| Automatic | Reopening at the place of today's first approval, with the phone on the same network as the machine and unlocked | Nothing |
| One tap | First approval of the day; reopening anywhere else; an agent's first use of a key in a repository; every use of an --own-approval secret | Tap the notification; a locked phone asks for its own unlock first |
| In the app | Showing the words, changing them, typing old words, pairing, handing objects back | Face ID or a fingerprint |
None of this is a setting. A file in the repository never grants anything, because a malicious repository would write one. Steps that remove sealctl's protection, such as sealctl unseal --all, also need the number shown on the terminal and, away from a trusted place, wait an hour: see confirmation levels.
4. Places
- Learned, not drawn. After first approvals on three different days at the same spot, the phone asks once: "Trust this place?" There is no map; you name the place.
- Locations never leave the phone. Places reach the relay only inside the phone's encrypted backup, which the relay cannot open.
- Leaving locks. The phone's region monitoring notices when you leave and locks the machines you opened there. The day's credit is kept.
- Near means the same network. The phone counts as near a machine when both reach the relay from the same network address and the phone is on Wi-Fi. On mobile data or a VPN it falls back to one tap.
- No permission, no places. Without location access, a session stays open up to 1 hour and reopening always takes a tap.
5. Setup
- Install the command line tool:
brew install sealctl/tap/sealctl, or a package for your Linux. - Install the app, write your 24 words on the card, then run
sealctl pairand scan the QR code. sealctl scanfinds keys in.envfiles, shell rc files, shell history and~/.aws, moves them into the store and leaves references behind.sealctl ai installsets up Claude Code, Codex, Gemini CLI, Qwen Code, Copilot and Cursor: skills, hooks, refusals and masking.
6. The 24 words
| Procedure | Card step |
|---|---|
| First start | Print a blank card, write the 24 words by hand, then pick 3 of them by number from 4 choices each |
| Restore from words | Type the words, completed after four letters; nothing new to write |
| Changing words | A new card, written and checked the same way; the old card is marked retired |
| Yearly check | The phone asks for 2 words by number; a wrong answer offers to show the words again |
When you change words, each machine moves its keys to the new words the next time it talks to the phone; sealctl migrate re-encrypts volumes and backups when you start it. The printable blank card (A4 and Letter) will be published here with the app.
7. What it is not
- Not a password manager. Website passwords stay in 1Password, Bitwarden or the browser.
- Not a team vault. There are no shared stores; teams keep shared keys where they keep them today.
- Not for regulated production work through bastion hosts or air-gapped sites.
- Volumes and backups keep your own folders under the same 24 words; they don't replace FileVault or a backup service.