The Developer pages

Two pages, two people

Keys are managed on two pages in the app's settings.

Both pages are closed to keys and to an AI signed in to the app. They answer as if they did not exist.

The company's Developer page

This is where the CEO decides whether keys exist at all.

Developer mode switches keys on and off for the whole company. Switching it off revokes every key at once. How long a key works sets the period, from 1 to 5 hours, and shortening it shortens every live key too. Saving either change asks for a recent sign-in when it widens what keys can do.

Let an AI sign in to the app is the door described on Letting an AI sign in to the app. It needs developer mode on and a typed confirmation, and it is drawn as a warning panel because it is the one way in without a passkey or a code.

Every key in the company lists every person's keys, live and recently ended, with who made each one. The CEO can revoke any of them from here.

Your Developer page

This is where a person makes and manages their own keys.

Make a key takes a label and makes the key. Your keys lists your keys with their label, when each was made, a live countdown to its end, and when it was last used, with Revoke beside each live one. Ended and revoked keys stay listed for a week. What a key can do lists, in the role editor's words, what a key you make may do today, and the endpoints that answer.

The new key dialog

Pressing Make a key opens the dialog that shows the key, once.

The agent prompt is the text to paste into an AI agent, with the key inside it. The key on its own is for a program. Each has its own copy key. The notice at the top says it plainly: this is the only time the key is shown. Pressing I have copied it closes the dialog, and the key cannot be shown again.