Claude Code multi-model setup: Opus executes, Fable reviews, Jev decides
Opus 5.5 writes code while Fable 5.1 reviews via /advisor at plan, repeated-error and completion points, and Jev handles small calls like tool choice, retries and stopping.
Claude Code gets much better when Opus 5.5 stops working alone Keep Opus on the main session and add Fable 5.1 using /advisor fable. Opus writes the code while Fable reviews the full session, including tool calls Fable steps in at three moments: before a major plan, when an error keeps repeating, and before marking the task complete You can split the rest between specialized agents. Explorer reads the code, Worker edits and tests, while Researcher pulls documentation Jev handles smaller decisions like which tool to use, when to retry and when to stop. The bigger models focus on tasks that actually require deeper reasoning The result is a cleaner workflow where Opus handles execution, Fable provides oversight and smaller agents handle focused tasks Instead of forcing one model to do everything, each part of the system has a clear responsibility Full setup prompt below