AI tools ask
Codex, Claude, Cursor, Hermes, OpenWork, terminals, scripts, and deploy tools request access when real work needs real credentials.
SSH and Git approvals
Your keys. Your approval.
Reveiew sensitive requests on a trusted device. You decide what to authorize.
Starting with SSH and Git signing on iPhone.
9:41● ● ●
SSH SIGNING REQUEST
Sign this commit?
A paired Mac is asking to use your SSH signing key.
RequesterPaired Mac
Repositoryhito / holdkey
Actiongit commit -S
ExpiresIn 10 minutes
Example approval screen
One request. One decision
The goal is not to block agents. The goal is to let them keep working while sensitive authority stays visible, scoped, and approved somewhere more trustworthy than the ordinary coding environment.
HoldKey contains
Early access starts with a lite container on iPhone or Android, with dedicated Hito hardware planned for higher-value use.
You approve
You see the sensitive action on a trusted device and approve the scoped result, not a blanket credential handoff.
The careful version
HoldKey starts with developer access because that is testable: Git, SSH, deploys, API credentials, and agent workflows across tools like Codex, Claude, Cursor, Hermes, and OpenWork. Payment credentials, card data, crypto keys, passkeys, passwords, and documents belong to the broader authority-vault direction, but every class needs its own typed approval model.
Early access, not a full launch
Early access is for builders who want to help shape trusted-device approvals around their own workflows.
Phone first, hardware later
The lite container makes the workflow reachable. Dedicated Hito hardware is the advanced path for users who want a smaller attack surface and stronger ceremony.
No generic secret hose
Git signing, API-key use, card-use approval, crypto signing, passkeys, and passwords should be separate typed requests with clear scope, expiry, and audit behavior.
Ask for early access
If this is the exact discomfort you are feeling with AI coding tools, send a note. The best early feedback is specific: which tool you use, what credentials it can touch, and what would make you comfortable.
- Tell us your workflow. Codex, Claude, Cursor, terminal agents, deploy tools, and the keys they can currently touch.
- Pick the first boundary. GitHub SSH, Git commit signing, server SSH, API keys, payment credentials, crypto keys, passkeys, or something else.
- No secrets. Do not send private keys, tokens, card numbers, seed phrases, SSH configs, or sensitive logs.