💡 Fable 5 Apex Tier + Opus 4.8 Upgrade for engine.sh Model Chains #562
Replies: 2 comments
-
|
Cross-link. Canonical discussion for new-Claude-model enablement is #413 ("Enable enhanced model selection for agents"); tracked implementation is issue #553 (gated on the inert tier-routing bug #195). Fold this proposal's direction into that work rather than tracking it standalone. |
Beta Was this translation helpful? Give feedback.
-
Weekly UpdateWhat ChangedImplementation complete — PR #569 merged the Fable 5 and Opus 4.8 upgrade to engine.sh model chains. The core proposal is now implemented. New cost signals require attention:
Updated Assessment
RecommendationKeep watching. Core implementation is done. Next priority: ensure the Fable 5 audit tier interacts properly with the budget circuit breaker (#635) and batch API (#639) proposals. After June 22, monitor Token Cost Observatory data for Fable 5 cost impact and adjust the model chain order if Fable 5 costs exceed the quality benefit. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Add Claude Opus 4.8 (
claude-opus-4-8) and Claude Fable 5 (claude-fable-5) to engine.sh model configuration. Opus 4.8 replaces Opus 4.7 as the audit/single-reviewer model with improved long-horizon agentic coding and tool triggering. Fable 5 becomes an optional "apex" tier for the most complex reviews, activated only when PR complexity exceeds a threshold.Market Signal
Anthropic released Opus 4.8 on May 28, 2026 with: mid-conversation system messages (preserves cache hits in long agent sessions), adaptive thinking improvements (fewer wasted thinking tokens), better tool triggering, and a lower cache minimum (1,024 tokens). Fable 5 launched June 9 as the first Mythos-class model — $10/$50 per M tokens, capable of multi-day autonomous tasks, with automatic safety fallback to Opus 4.8 on high-risk queries (<5% of sessions). Both are available now on the Claude API.
User Signal
Issue #553 explicitly requests enabling Fable 5 and Opus 4.8 with capability-aware selection. Issue #382 requested Gemini 3.5 support, showing ongoing demand for model currency. The engine.sh architecture already supports per-tier model chains (
CLAUDE_TRIAGE_MODEL_CHAIN,CLAUDE_DEEP_MODEL_CHAIN, etc.) and cross-provider fallback.Technical Opportunity
engine.shalready defines per-tier model chains and supports claude/gemini/copilot providers. Adding new model IDs requires updatingset_engine_config()— the architecture was designed for exactly this kind of extension. Key Opus 4.8 features for the review pipeline:Assessment
Adversarial Review
Strongest objection: Fable 5 at $10/$50 per M tokens is ~2x Opus 4.7 pricing. Unrestricted use could balloon the token budget. The safety fallback to Opus 4.8 on sensitive topics could cause inconsistent behavior in security-focused reviews.
Rebuttal: Cost control comes from the existing tier architecture — Fable 5 would only activate for the audit tier on high-complexity PRs, not for triage or routine deep review. The safety fallback is actually beneficial for security reviews, routing sensitive code analysis to the more conservative Opus 4.8. The per-tier model chain pattern means adding Fable 5 to
CLAUDE_AUDIT_MODEL_CHAINis a minimal, reversible change. Updatemodel-pricing.tsvwith effective-dated rows to maintain cost reporting accuracy.Suggested Next Step
Update
set_engine_config()inscripts/engine.shto useclaude-opus-4-8for all currentclaude-opus-4-7slots, addclaude-fable-5as first entry inCLAUDE_AUDIT_MODEL_CHAINandCLAUDE_SINGLE_MODEL_CHAIN, and updatescripts/lib/model-pricing.tsvwith new pricing rows.Beta Was this translation helpful? Give feedback.
All reactions