API key synchronisation
Configure once when your plan allows it.
Bring supported provider API keys to another signed-in computer.
Configure once when your plan allows it.
When setting up your own AI connections on a second Host after sign-in.
Repeatedly entering provider keys on each computer is inconvenient. Supported key synchronisation makes linked setup easier within the account workflow.
Enable the supported option and review the connection on the new device. Keys remain treated as secrets rather than ordinary chat text.
How to get started.
From your first choice to the result. Here is how to use this feature in your own project.
- 01
Check that relevant keys are stored in provider settings.
- 02
Use the available account synchronisation on authorised linked computers.
- 03
After sign-in, check available provider connections before starting a task.
How it could work for you.
Sign in on a second computer and configure an available synchronised API connection without posting the key in a conversation.
How to assess the result
Encrypted storage does not mean every authentication type can be synchronised. Do not describe it as end-to-end encryption unless that property is explicitly implemented.
Where to find it.
Settings → Account & Connect → API key synchronisation
Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.What is saved?
Keys are kept in separate encrypted account storage and protected local storage.
What you need to know
Personal subscription tokens are not synchronised. The account server can decrypt keys for authorised computers; this is not end-to-end encryption.