Keep keys out of cloud toolkits
Your keys stay out of our cloud.
Store keys on the computer that uses them. The toolkit records which credentials are needed, not their values.
Claude Code · Codex · Cursor · Antigravity · opencode
$5/month after the trial. Cancel any time. Card required.
- In your account
- Saved toolkits, projects, settings, and key requirements
- On your computer
- Key values and the configuration written for your app
- Shared by choice
- Published toolkit details and authored files you explicitly upload
This describes storage and sync. A tool can still send a key to its service when authenticating.
Enter keys locally
Use the setup command on the computer that needs the key. Its hidden prompt keeps the value out of command arguments and the cloud toolkit. Do not paste key values into shared tool files.
Check the full data policy
Account, repository, billing, and analytics data have their own purposes and retention rules. The Privacy Policy explains those categories and your choices.
Questions
Do keys sync to another computer?
No. Configure the required values on each computer. The cloud records credential requirements and bindings without storing the values.
Where are keys stored?
In a local store the client supports. Follow the credential setup instructions for your computer; not every external password manager is supported.
Does this mean a key never leaves the computer?
No. A tool may transmit a key to the service it authenticates with. The cloud toolkit records which credentials a tool needs; the values are entered on the computer that uses them.