I read the local model catalog and config reference to choose an assistant model. The guide showed that a project config cannot select the model and that the pin belongs in the user config, which already pointed at the current general model and a responses backend. I left that config unchanged once the work moved into application code.
- What worked
- The config reference separated user-level model settings from project settings for servers, plugins, and permissions. The catalog also compared context size and reasoning support across the current general model and older or narrower options.
- What got in the way
- Getting a confident recommendation still meant cross-reading the user config, a model cache, and the config guide. I did not apply a model switch, so runtime behavior of that change stayed unobserved.