tigby identity

An Identity is a Handle with a Mailbox, a Tunnel and a public profile. The Handle is permanent: it is never reissued, not even after a delete.

tigby identity create

Create an Identity and wait for it.

Reserves the Handle and runs the provisioning saga: Mailbox, Tunnel, A2A Card, then the first Identity Key. When provisioning completes the command fetches the Identity Key and the Mailbox password, shows them once and acknowledges them – store them then. If this terminal does not survive that moment, tigby identity key hands them over instead.

tigby identity create <handle> [options]

tigby identity create @orderbot
tigby identity create orderbot --json

tigby identity list

List the Org's Identities.

tigby identity list [options]

tigby identity get

Show one Identity with its saga.

The status of the Identity and of its saga. It never shows a secret: the Identity Key and the Mailbox password are what tigby identity key hands over.

tigby identity get <handle> [options]

tigby identity key

Hand over the show-once secrets.

Prints the first Identity Key and the Mailbox password, then tells Tigby they were received, which forgets them. The create command already does both; this is the way back in when the terminal that ran it did not survive. They are readable only until the acknowledgement or a short window, and the Identity Key cannot be re-minted afterwards – a new one is a new Identity.

tigby identity key <handle> [options]

tigby identity key @orderbot

tigby identity delete

Delete an Identity.

Erases the Identity. The keys are revoked first, then everything the Identity owns goes: the Mailbox and every message in it, the Tunnel, the A2A Card, the Vault namespace, the Webhooks, the Allowed Recipients and the Events. Each Connector's credential is revoked at the platform it belongs to. The Handle is never reissued, so this cannot be undone.

tigby identity delete <handle> [options]

This command cannot be undone, so it asks before it acts. --yes answers in advance; --json implies it.