Harness Profiles and budgets
Keep coding-tool keys, model permissions and cumulative budgets in one place.
On this page
Create a profile
- Open Harness Profiles and select a coding tool.
- Name the profile and select its virtual model.
- Choose a request or token cap and token saver setting.
- Copy the newly issued gateway key and generated configuration into the tool.
Each account can have one active profile per tool. Profiles own their key and model restriction. Existing usage stays cumulative when a cap changes; changing a cap does not reset consumption.
Read the budget bar
The profile shows used and remaining budget. Requests over the profile budget return HTTP 429. Ordinary API Key quotas retain HTTP 402. Expiry, revocation, allowlists and account disabling are still enforced.
Rotate a client key
Regenerate or revoke from API Keys and update the local tool environment. Secrets are shown at issuance only. Audit records capture management actions without retaining the secret. Keep provider keys in Conflux; coding tools use gateway keys.