Update — July 8, 2026: Included Fable extended to July 12, 11:59pm PT — extension guide
July 1, 2026 — Fable 5 is live. Official Anthropic terms: 50% of weekly limits through July 12, then credits; classifiers may route some coding to Opus 4.8. Prioritize frontier tasks before July 13.
This is the expanded 35-use-case checklist. Use cases 1–10 link to deep dives in the original top 10 guide; 11–35 are July 1 quick-starts worth running this week.
Before you start (2 minutes)
| Check | Why |
|---|---|
| Fable in picker / API | Rollout may be gradual — status hub |
| Credits vs limits | 50% weekly through July 7 — official · limits guide |
| Classifier fallback | Cyber-adjacent coding may hit Opus 4.8 — not a picker bug |
| Sonnet 5 fallback | Cheaper for bulk agent steps |
| Harness ready | Claude Code commands · loop design |
| China / proxy users | Read fingerprint report + China availability |
The top 10 — full write-ups elsewhere
These are the highest-signal Fable workloads from June launch week. Each has a long-form section in Top 10 Fable 5 use cases:
- Greenfield app from a PRD + mockup — full stack in one session
- Large-scale refactor / migration — REST→GraphQL, TS strict, monolith split
- Autonomous deep research synthesis — papers + contradicting evidence
- Financial analysis — 10-K/10-Q, earnings prep, credit memos
- Legal due diligence — contract bundles, redlines, data room flags
- Vision document intelligence — charts, whiteboards, UI verify loop
- Self-correcting
/goalloops — test coverage, benchmark targets - GitHub Copilot enterprise coding — multi-file PR-aware edits
- Multi-day agent sessions — launch video edit story
- Scientific / genomics research — literature + experimental design
July 1 tip: Pick one from this list and run it end-to-end before trying exotic prompts.
11–35 — try these on restore week
Software engineering (11–18)
| # | Use case | One-line prompt shape |
|---|---|---|
| 11 | Flaky test hunt | "Find and fix the 5 flakiest tests; prove with 50 consecutive green runs" |
| 12 | Dependency upgrade blast radius | "Upgrade React 19→20 across monorepo; fix breaking API usage" |
| 13 | Security patch sweep | "Triage CVE list; patch critical; open PR with changelog" |
| 14 | Observability gap fill | "Add structured logging + tracing to payments path; no PII leaks" |
| 15 | API client SDK generation | "Generate typed SDK from OpenAPI; examples + integration tests" |
| 16 | Performance regression | "Profile p95 latency; optimize hot path; before/after benchmark" |
| 17 | Database migration with rollback | "Zero-downtime column migration + rollback script + runbook" |
| 18 | Minecraft-scale creative build | 3D world from one prompt |
Agents & DevOps (19–24)
| # | Use case | Harness notes |
|---|---|---|
| 19 | Incident runbook executor | Feed postmortem + logs; propose fix + prevention PR |
| 20 | IaC drift reconciliation | Terraform plan/apply loop with policy checks |
| 21 | CI pipeline author | GitHub Actions from repo conventions; cache + matrix |
| 22 | On-call handoff doc | Summarize week of alerts → actionable runbook updates |
| 23 | Multi-repo feature | Same change across 3 services with coordinated releases |
| 24 | Parameter golf / ML pipeline | 8-hour loop improvement vs Opus baseline |
Research & knowledge (25–29)
| # | Use case | Output |
|---|---|---|
| 25 | Competitive landscape memo | 20 competitors → matrix + strategic implications |
| 26 | Patent prior-art scan | Claims vs corpus; gap table for counsel |
| 27 | Policy brief from sources | EU AI Act section → exec summary + citations |
| 28 | Course syllabus builder | Learning objectives → 12-week outline + assessments |
| 29 | Literature review for grant | NIH-style background + gap statement |
Business & ops (30–33)
| # | Use case | Who benefits |
|---|---|---|
| 30 | Board deck from metrics | CFO: narrative + chart suggestions from raw CSV |
| 31 | Vendor RFP scoring | Weight criteria → ranked vendors + risk flags |
| 32 | Customer support taxonomy | 10k tickets → clusters + macro reply drafts |
| 33 | Sales battlecard refresh | Competitor launch → updated objection handling |
Frontier / Mythos-class (34–35)
| # | Use case | Why Fable not Sonnet |
|---|---|---|
| 34 | Cyber range scenario design | Mythos safeguards + long-horizon red-team planning (Mythos context) |
| 35 | Multi-day product rewrite | Spec → architecture → implementation → docs across sessions with memory |
How to run a July 1 session (template)
bash
# Claude Code example
/goal "Ship feature X with 90% test coverage and updated README"
# Model: Fable 5 (once restored)
# Fallback: Sonnet 5 for sub-steps if credits low
Loop checklist (Lance Martin pattern):
- Define pass condition — tests green, benchmark number, doc section complete
- Give environment access — repo, CI, browser if UI
- Let it fail once — Fable investigates better after real errors
- Verifier agent — separate grader if using Managed Agents
- Stop rule — max hours or credit cap from Console
Sonnet 5 vs Fable 5 — routing table
| Task type | Model |
|---|---|
| Bulk edits, daily coding, chat agents | Sonnet 5 |
| Multi-day, FrontierBench-hard, Mythos cyber | Fable 5 |
| Quick Q&A, drafts | Haiku / Sonnet |
| Peak general reasoning (non-Mythos) | Opus 4.8 |
Intro Sonnet API pricing $2/$10 through Aug 31 — use it to save Fable credits for items 34–35.
If Fable is not in your account yet
- Refresh Claude Code and Console
- Confirm international restore — not China consumer path
- Run 11–17 on Sonnet 5 — still strong agentic scores
- Open-source frontier: GLM-5.2, Kimi K2.7, OpenRouter Fusion
Related on explainx.ai
- Kimi K3 beta leaks — Moonshot agent flagship (Jul 2026)
- C&C Generals ported to macOS/iPad using Fable 5 — a real-world case study, including the HN debate over credit
- Top 10 Fable use cases (deep dives)
- Top 10 Claude Opus 5 use cases — parallel checklist after the July 24 Opus launch
- Is Fable 5 back?
- Fable rate limits on restore
- Claude Sonnet 5 launch guide
- Fable 5 on Claude Code
- Loop design guide
- Fable 5 advisor & orchestrator patterns — Sonnet + Fable advisor at ~63% cost (@ClaudeDevs, July 8)
- Claude Code China fingerprinting
- Enterprise alternatives
Use cases reflect June–July 2026 community patterns and Anthropic launch materials. Verify model availability in your account. Last updated: July 1, 2026.