docs: recommend Opus 4.8 over Opus 4.7#1262
Open
shashank-factory wants to merge 1 commit into
Open
Conversation
Update model recommendations to lead with the new Opus 4.8 flagship in the choosing-your-model guide, mixed-models config, and the power-user prompt-crafting / token-efficiency guides (English + Japanese mirrors). Opus 4.7 stays listed as a fallback/alternative. Catalog, benchmark, changelog, and EU-availability references are left unchanged (Opus 4.8 is not yet available in the EU).
Contributor
|
Droid encountered an error —— View job Droid is reviewing code and running a security check… |
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Updates model recommendations to lead with the new Opus 4.8 flagship instead of Opus 4.7, across English docs and their Japanese mirrors:
cli/user-guides/choosing-your-model.mdx— §2 "Match the model to the job" rows, the Tip, and §4 reasoning-effort listing (adds an Opus 4.8 line + includes it in the "Max is available on…" sentence)cli/configuration/mixed-models.mdx— Spec-mode model recommendationguides/power-user/prompt-crafting.mdx— "Complex architecture" rowguides/power-user/token-efficiency.mdx— "Architecture planning" rowjp/mirrors of all four filesOpus 4.7 is retained as a fallback/alternative everywhere. The stale "1× promotional multiplier through April 30" wording is dropped, since Opus 4.8 is a flat 2× with no promo.
Deliberately NOT changed
These are catalog/data/historical references, not recommendations:
models.mdx(model catalog table)snippets/leaderboards/review-benchmark.mdx(numbers measured for 4.7)changelog/1-9.mdx(historical)enterprise/eu-deployment.mdx— Opus 4.8 is not yet available in the EU, so changing this would be inaccurateCompanion PR
CLI splash screen: Factory-AI/factory-mono#15401
Testing
mint broken-linkssurfaces only a pre-existing parse error injp/web/machine-connection/cloud-templates/index.mdx(unrelated, not touched here)