A provider profile is not a repository secret
A coding-agent provider profile needs an endpoint, account label, model selection, and credential reference. The raw secret should stay in client-managed secure storage or a controlled environment variable, not in source code, workspace configuration, screenshots, or copied prompts.
This lets teammates share a project workflow without sharing one person’s provider account. Each developer can connect an approved account locally and choose the profile that meets the project policy.
Test before you rely on a credential
A connection test should distinguish invalid credentials from a model permission problem, endpoint failure, account credit issue, or rate limit. Do not solve a 401 by repeatedly sending real workspace context to a different endpoint.
After setup, make a small read-only request and verify the selected provider and model are what you expected. Keep an alternate profile for legitimate service limits rather than weakening repository controls.
Rotate and contain the blast radius
Use keys with the narrowest practical scope, revoke exposed keys promptly, and rotate credentials when a device, environment file, or pasted transcript may have leaked them. Keep secrets out of Git history; deleting a file later does not remove a committed credential.
Truss stores provider credentials through the client credential integration and keeps them out of workspace configuration, while provider profiles and connection feedback remain visible to the developer.
Next steps
Put it to work in your own workspace.
Pick the surface that fits your day, then connect a model you control.
FAQ
Questions developers ask before switching.
Should I put an AI provider API key in my repository config?
No. Use secure client storage or an approved environment-secret mechanism, and ensure secret files are excluded from version control.
Can a coding agent read my API key?
A well-designed client should avoid exposing raw provider credentials to workspace context or normal agent tools. Verify the client’s credential model and keep secrets out of files the agent can read.