Model Switching
Changing between Claude models (Haiku/Sonnet/Opus) mid-session to optimize cost, using cheaper models for routine work and expensive models for critical decisions.
Model switching is the primary cost optimization lever in Knowledge OS. Haiku handles batch operations (file renaming, frontmatter updates, data processing) at 60x less cost than Opus. Sonnet is the daily driver for standard work (content production, research, coding). Opus is reserved for critical planning, complex multi-phase design, and high-stakes deliverables. Switching happens via the /model command: "/model haiku" before a batch operation, "/model sonnet" after. A typical session might start on Sonnet for planning, switch to Haiku for file operations, and switch to Opus for final review. This pattern reduces monthly costs by 30-50% compared to running everything on Sonnet.
Where it shows up:
Related Terms
Architecture
Token Cost
The API usage cost measured in input/output tokens, the primary operational expense of running Knowl...
Architecture
Context Window
The token limit within which Claude operates per conversation, determining how much knowledge, histo...
Skills Layer
Skill
A reusable instruction set that encodes a repeatable process. Skills load context, apply methodology...