Manage team keys and short-lived access.
The team SSH keychain stores reusable public keys for server access. ServerChirp records the key type and fingerprint so you can distinguish keys without comparing their full contents.
Open Settings → SSH keys, choose Add key, and paste the public key line.
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAA... developer@example.comServerChirp accepts supported OpenSSH public-key formats. It does not ask for or store the private key.
When you create or edit a system user, attach one or more team keys. ServerChirp reconciles the user's authorized_keys file through the agent and records the mutation.
For temporary access, issue a key that expires after 12 hours. Expiring access is better suited to a short investigation than adding a permanent team key and remembering to remove it later.
Cloud providers may maintain their own SSH-key catalog. Provider keys are selected while creating a server and are separate from ServerChirp's team keychain. After the agent is connected, manage ongoing access through system users and team keys.
Add the replacement key before removing the old one. Confirm that the replacement works on every required server, then remove the old key from the affected users and from the team keychain.