Model Selection by Workflow Type

The best model is workflow-dependent. A Rocky setup should match model capability, cost, context length, and tool use to the job.

Coding and repo work

Use a strong model with reliable tool use and enough context for files, tests, and error output. The model should be able to inspect before editing and verify after changes.

Web research

Use a model that follows source-first behavior: search, extract, cite, and separate current facts from assumptions. Research workflows benefit from careful summaries more than speed alone.

Writing and wiki pages

Use a model that produces structured, accurate, non-fluffy copy. For public pages, the model should preserve schema, metadata, headings, and search-friendly summaries.

Vision and screenshots

Use a vision-capable model when the workflow depends on UI state, diagrams, charts, screenshots, or visual QA.

Scheduled summaries

For low-risk daily summaries, a cheaper model may be enough if the workflow is read-only and easy to verify.

Decision rule

Pick the least expensive model that can complete the task with high reliability and real verification. If failures become expensive, upgrade the model before adding more automation.