Read the ingredient label
Identify the model version, who serves it, and which application sends the request. Confirm relevant provider policies and technical limits directly. A model described as permissive may still be served under provider rules, and an interface may add its own instructions. Keep verified facts separate from assumptions based on a name.
Try a representative task
Use a small code recipe with a known result, such as explaining the CSV converter or reviewing an HTTP failure check. Evaluate whether the assistant follows the requested scope, handles ambiguity, and admits missing evidence. One successful answer describes that example; it does not establish universal correctness or unrestricted future behavior.
Control the working area
Review file, shell, and connector access before allowing actions. Start with a sample project and avoid sending sensitive material until you understand its handling in the selected setup. The kitchen metaphor is about preparation and judgment. It is not a promise that any endpoint has no restrictions, unlimited capacity, or audited privacy.
Recipe 07 / Model choice
Know what goes into the model choice.
An unfiltered or uncensored coding assistant can support an exploratory working style. Those words do not establish identical behavior across models, providers, or execution environments.
The serving check
You can name the model, explain who operates it, and describe what the assistant is allowed to inspect or change.
A brief for your assistant
Explain the CSV converter using only the supplied code. Identify the parsing library, validation checks, memory assumption, and expected output. Separate facts from questions that require additional evidence.
Next at the counterGet the assistant