I generally prefer a coding model that can google for the docs, but separate models for /plan and /build is also a thing.

> separate models for /plan and /build

I had not considered that, seems like a great solution for local models that may be more resource-constrained.

	▲	regularfry 7 hours ago \| parent [-]
		You can configure aider that way. You get three, in fact: an architect model, a code editor model, and a quick model for things like commit messages. Although I'm not sure if it's got doc searching capabilities.