Get started · The family

Why the Lock Family

Why the Lock Family #

The agent never holds a credential. Passwords, keys and tokens stay in a Lock's console, in an account and container the agent cannot reach.
Personal data stays masked. Values come back masked before they reach the model; a clear value needs your approval.
An agent cannot approve itself. Every approval is answered in lox run, outside the harness, and the hub signs it, bound to the exact plan.
One place for every source. One hub, one terminal and one audit log for all your Locks.

🔑 Credentials stay in the Lock Each Lock's console holds the password, key or token, in its own account and container. The agent talks to a socket, never to the database.	🎭 Masked by default Every value the agent sees is masked first: emails, IPs, cards, secrets. The hub only ever sees masked screens.
✍️ You sign, outside the harness `lox run` approves reads by rule and asks you for connections, writes and DDL. Shift+Tab switches to manual; quitting fails closed.	📜 Every decision audited `lox audit` lists each exchange: the masked request, the rule or human who decided, the outcome. Each decision is signed.