The native trace-cli bundled with Trace has no BYOK configuration command
or provider-key flag in its documented command tree. Older setup guidance
does not apply to this executable. Do not guess a flag or put a provider key
in a chat message, design file or command argument.
Identify your client
Install the Trace app, launch it and sign in to the main app first for native CLI AI. The CLI reuses that session; an expired session needs desktop refresh/sign-in, not a separate token.
Use the native CLI guide and installed chat --help.
Regular CLI AI uses Trace-hosted models and the
account access and usage conditions.
--model chooses a supported hosted model; it does not configure BYOK.
Organization-specific arrangements
BYOK is disabled by default in the standard Trace service. If your organization needs a different arrangement, confirm native client and service support before sending any key.
Contact hello@buildwithtrace.com with:
- The client name and installed version.
- Whether you are using the standard Trace service or an organization-specific arrangement.
- The workflow and model you need.
Ask support to confirm compatibility, credential handling, and which account pays for requests. Do not send the credential itself.
A key reported as configured only describes local configuration. It does not prove that a request used that key, that the service accepted it, or that Trace usage was not charged.
Protect existing credentials
If you previously stored a provider key in another tool, review or revoke it through that tool's supported controls and the provider. Native CLI sign-in does not remove credentials stored elsewhere. Do not send a test design or key merely to discover whether a disabled feature works.
Keep keys out of logs, screenshots, chat messages and design files.
See BYOK availability, Billing, and Troubleshooting for the current supported path.