Appearance
Secrets & credentials
Provider keys and saved credentials belong to the local service’s private secret store. Use the dedicated controls instead of adding a key to source, a notebook, or a normal chat message.
Provider accounts and API keys
Use Settings › Agent for Codex or Claude Code sign-in. Their CLIs manage their own credentials on the service machine.
Use Settings › LLM providers for OpenAI, Anthropic, or OpenRouter API keys. Managed provider keys are stored in the encrypted local vault; public workspace records hold descriptors rather than resolved values.
Removing a provider removes its saved vault credential. It does not silently choose a different billed provider.
Private request cards
When a project conversation presents a Secret request card, review its title, purpose, and any credential-page link. Enter the value in its masked Secret field and choose Save securely, or choose Decline.
Remember as saves a named local credential for later use. The field clears on submission, and the value is not added to the conversation text.
A card requesting file delivery explains that the agent’s commands can read a private file for about 24 hours. Choose whether that delivery is appropriate before you submit it.
Where the store lives
The vault is under the private service data directory. On desktop, the operating system’s protected storage wraps the master key. A local service without desktop protected storage can use an owner-only key file; access to that file and the encrypted vault is enough to decrypt it.
There is no automatic cloud synchronization of saved workspace credentials. Agent provider requests still go to the provider you select.
If the store is locked
Open klars desktop on the computer holding the vault. For a provisioned headless service, the operator can supply KLARS_SECRET_KEY at startup. It must be the correct canonical base64-encoded 32-byte key for that store.
Do not replace a vault key to clear a locked-store error. You need the key that encrypted the existing credentials. Keep launch keys out of workspace files and logs.
A 1Password picker is not supported in this build. See troubleshooting for recovery steps.