A provider runtime is the coding-agent application Clay Studio launches, such as Claude Code or Codex. The model is the AI you select inside that application. Installing a provider does not make every model available, and choosing a model does not change provider accounts.
#Choose a model
- Select New session in the intended folder.
- Choose an installed provider and select Create.
- Open the session's model control.
- Wait for the model catalog.
- Select an offered model and wait for confirmation.
- Choose reasoning effort if that model exposes it.
The provider picker reflects discovery in the server environment. If a runtime is installed but cannot authenticate, follow Provider authentication.
The model picker distinguishes Loading models…, Couldn’t load models, and No models available. Use Retry to request the catalog again. If selection fails, read the error and check which model remains selected before submitting a large task.
#Reasoning effort
Reasoning effort controls how much effort a supported model spends working through a request. Models may offer low, medium, high, or additional levels. Use the actual options for the selected model rather than copying another provider's setting. Higher effort can affect latency and usage; it does not guarantee correctness.
A runtime without an effort control can still perform work. Clay Studio does not invent an equivalent option. Scheduled Tasks require explicit model choices for both members of their execution pair.
#Continue with another provider
Changing a model and handing off to another provider are different operations. A handoff needs the goal, current changes, verification, unresolved questions, and next action. Hidden reasoning and every provider-native feature do not automatically transfer.
Example: “Review the current three-file diff for error handling. The relevant check passed. Do not edit or commit.”
#Resolve failures
An empty catalog can indicate startup or authentication problems. A catalog that loads followed by a failed request can indicate model entitlement, exhausted usage, or a runtime error. Read the actual failure before retrying. Repeated selection cannot fix expired authentication.
Permission mode is independent of model and effort. Check Permissions, Usage and context, and Provider capabilities before a long task.