Guides

Choose your model and tool stack

Fable 5 is unavailable for now, so the practical question is what to run instead. This is the written companion to our picker: what to choose, in what combination, for what you actually do — with the real tools and links.

Quick summary

  • Most people want a small stack, not one tool — one model to think, an agent to build, a second model to review, and cheap models for the bulk.
  • The everyday default: build in Claude Code on Opus 4.8, and have Codex (a different model lineage) review the work — that catches what a self-review misses.
  • For judgment, planning, and writing you don't need a coding agent — a strong chat model like GPT-5.5 Pro or Opus 4.8 is enough.
  • Push routine, high-volume work to cheaper open models (GLM-5.2, DeepSeek via OpenRouter) so your frontier spend stays focused.
  • Prefer not to read it all? The picker turns a few answers into a concrete setup.
BuildClaude Code · Opus 4.8
JudgeGPT-5.5 Pro
Cheap / bulkGLM-5.2 · DeepSeek

Start with two questions

Your best stack depends on two things more than anything else.

  • Are you coding?Building software needs a coding agent and a review step. Writing, research, and decisions do not — a strong chat model is enough.
  • How high is the bar, how often?Daily, high-stakes work justifies paying for a frontier model and a separate reviewer. Occasional or low-stakes work can lean on cheap or open models.

Answer those two and the rest falls into place. Below is the default most people should copy, then how to vary it by job, by budget, and by how often you work.

The default stack

If you don't want to think about it, copy this. It mirrors how careful teams are working in mid-2026.

  • Think / planGPT-5.5 Pro (ChatGPT) or Opus 4.8 — reason it through before you build.
  • BuildClaude Code on Opus 4.8 (1M context), effort high to max for the hard parts.
  • ReviewCodex (GPT-5.5) as an independent gate — a different model lineage catches what a self-review misses.
  • Cheap / bulkGLM-5.2 and DeepSeek via OpenRouter for routine, high-volume, or experimental work.
  • One client (optional)OpenCode or Hermes if you'd rather drive several models from one place.

If you mostly write, research, or decide

Non-coding work doesn't need a coding agent. Use a frontier chat model and a simple pattern.

The pattern that works: analyze with a strong model, have it produce a clean Markdown brief, then act on that brief. Ask for the reasoning, not just the conclusion.

For the hardest calls, run the same question through two different models; where they disagree, dig in before you commit — that gap is usually where the real risk is hiding.

If you build software

Pair a strong builder with a different-lineage reviewer — that combination is the daily driver.

  • BuildClaude Code on Opus 4.8 (1M context). Effort high for normal work, xhigh or max for the hardest 20%.
  • ReviewCodex (GPT-5.5), maxed, as a gate on every non-trivial change. It's also a capable second builder for the hardest module — build it twice and diff.
  • Front-endDesign in Claude, then hand the spec to Claude Code to build.
  • Bulk / scaffoldingSend boilerplate to GLM-5.2 + DeepSeek so you don't spend frontier tokens on plumbing.

By budget

Same roles, scaled to what you can spend. Prices move — check the live catalogs.

  • TightStart on open models: GLM-5.2 (1M context, MIT-licensed, ~$10/mo) and DeepSeek via OpenRouter. Step up to a Claude plan or about $5 of Anthropic API for Opus 4.8 only when an open model genuinely can't finish a task.
  • SomeOne paid frontier seat — Opus 4.8 in Claude Code at effort high or xhigh — plus open models for everything else. Add Codex as a review gate once your workflow is steady.
  • Whatever it takesThe full stack: Opus 4.8 (max) to build, GPT-5.5 Pro for judgment, Codex maxed as a mandatory review gate and parallel second builder. Even here, send scaffolding to cheap models.

By how often you use it

Frequency decides whether a subscription or pay-as-you-go is cheaper.

  • Heavy, dailyA subscription usually wins. Note: the June-15 change that would have metered automated runs separately is currently paused — interactive Claude Code still runs on your plan. See the news for the live state.
  • OccasionalPay-as-you-go API, or an open-model key, avoids paying monthly for capacity you leave idle. The cost calculator shows the crossover for your usage.

Run several models from one place

If juggling tabs is the pain, a unified client or a local runner helps. These are real tools you can use today.

  • OpenCodeAn open, unified client: point it at several models and drive them all from one interface, so you're not switching tabs and keys — good if you mix providers a lot.
  • HermesNous Research's local runner: it runs models on your own machine (via LM Studio or Ollama) and can carry out multi-step tasks with memory — good if privacy, offline use, or no per-token bill matters to you.

Want this picked for you?

If you'd rather answer a couple of questions than read the whole thing, these three give you a concrete answer in under a minute.

What's coming

We're packaging this guide into a downloadable kit — the ready-to-paste configs, prompts, and the routing table behind the picker — so you can set the whole stack up in an afternoon. This page is the free version of it.

Further out, Coily is a workflow layer we're building that routes each task to the right model and runs it for you — the stack above, automated, and aiming to be friendlier than Hermes or OpenCode.

The kit isn't for sale yet, and Coily is in development, not launched.

Need the short answer?

Fable 5 is currently unavailable. Use official status pages for access decisions, and use alternatives or preserved task briefs for active work.

Read the brief Fabel 5 spelling guide

FAQ

Is Opus 4.8 enough now that Fable 5 is gone?

For most Claude workflows, yes — it's the strongest still-available Claude, with a 1M-context version and effort modes. For the hardest long-horizon tasks you may notice gaps; record them rather than guessing.

Do I really need both ChatGPT and Claude?

Not to start — one frontier model covers a lot. The two-model habit pays off when correctness matters: a different lineage reviewing the work catches mistakes a self-review won't.

Are open models good enough?

GLM-5.2 and DeepSeek can get close to frontier on many coding tasks at a fraction of the cost — but official benchmarks for the newest versions aren't published yet, so treat that as a claim to verify on your own work. They're great for bulk and routine tasks; test them on your hardest ones before trusting them there.

What changed on June 15?

Anthropic announced, then paused, a change that would have metered automated and agent usage against a separate credit pool. As of now it did not take effect — programmatic usage still runs on your subscription. It's fast-moving, so check the news page.

Can I just use one tool?

Yes — Claude Code on Opus 4.8 alone gets a lot done. The extra pieces (a reviewer, cheap bulk models) are about quality and cost, so add them when you feel the need, not before.

Related

Sources

This page is independent. Official provider pages are the source of record for access, pricing, and policy.