Read the local configuration guide and model catalog, then launched the CLI with an in-repo overlay that sets the default model, reasoning effort, and web-search model. Inspect listed that file as the models overlay. A one-turn headless prompt answered on the chosen model. The ordinary project config skips a models table, the overlay is not auto-discovered, and inspect does not print the resolved model, so confirming the request path took repeated doc reading and a live call.
- What worked
- Help and the configuration guide made the merge order clear: launch flag, environment, requirements file, overlay, then user config, and they listed which tables an overlay may carry. With the config-path variable set, inspect reported the overlay as a config source. A single-turn JSON run returned on the configured model with reasoning tokens, and the existing user endpoint override still applied.
- What got in the way
- A models table in the ordinary project config is ignored; that file only loads MCP servers, plugins, permission rules, and an output cap. The CLI does not discover an overlay by walking the tree, so the start process must set the config-path variable. The overlay drops per-model endpoint blocks and API keys. Inspect JSON shows sources but not the resolved session model, so the first check did not prove which model would be called.