Skip to content

docs: add Claude Fable 5.1 to the model choice page - #670

Merged
hongyi-chen merged 1 commit into
mainfrom
factory/fable-5-1-model-choice
Sep 2, 2026
Merged

docs: add Claude Fable 5.1 to the model choice page#670
hongyi-chen merged 1 commit into
mainfrom
factory/fable-5-1-model-choice

Conversation

@warp-agent-staging

@warp-agent-staging warp-agent-staging Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds Claude Fable 5.1 and its five effort variants to the public docs model catalog, per a Slack request from Hongyi Chen.

  • src/content/docs/agents/inference/model-choice.mdx — added claude-5-1-fable-low/medium/high/xhigh/max to the Anthropic table, ordered above the existing Claude Fable 5 rows (newest-first). high is labeled as the default-effort variant, matching the Fable 5 row shape/precedent (no separate "default" flag exists in the server catalog for either family; high is the most defensible choice given Fable 5.1 has the identical Low/Medium/High/XHigh/Max effort ladder as Fable 5).
  • Extended the ZDR data-retention caution directly below the table to cover Claude Fable 5.1 alongside Claude Fable 5.

Verification against warp-server (authoritative catalog source):

  • Model IDs confirmed in model/types/ai/types.go (ClaudeFable51LowEffort ... ClaudeFable51MaxEffort) and logic/ai/llm/model_choice.go (BaseNameClaude51Fable, LLMDisplayNameParts).
  • claude_5_1_fable feature flag is true in config/prod.yaml, so the model is live in production.
  • ZDR/data-retention: logic/ai/llm/anthropic/util/util.go's requiresDataRetentionWorkspace and logic/llm_policy/llm_policy.go's defaultDisabledForEnterpriseLlmIds both list the Fable 5.1 variants alongside Fable 5, and client/src/components/admin/utils/uiStrings.ts's MODEL_ADMIN_TOOLTIPS shows the same Anthropic data-retention tooltip for the Fable 5.1 ids — confirming the same ZDR caution applies.
  • Swept other docs pages that mention "Fable" (pricing-faqs.mdx, security-overview.mdx, admin-panel.mdx, byollm-gemini-enterprise.mdx) — these already use generic, version-agnostic "provider-specific data retention requirement" / "Claude ... Fable families" language with no hardcoded Fable 5 model names, so they already cover Fable 5.1 without changes. Grepped the rest of src/ for claude-5-fable/claude-5-1-fable/model enumeration surfaces (llms.txt-style listings, changelog, pricing) and found no other place to update.

Verification

Docs-only content change (table rows + prose), not user-facing UI code, so no computer-use pass — verified via the repo's documented checks:

  • npm run build — clean (Complete!, 380 pages generated)
  • python3 .agents/skills/style_lint/style_lint.py --changed — 0 issues on the changed file (3 pre-existing warnings on unrelated lines of the same file, not introduced by this change)
  • python3 .agents/skills/check_for_broken_links/check_links.py --internal-only — 0 broken links across 3971 internal links

Originating thread: https://warpdev.slack.com/archives/C09BVK0PL3Y/p1788291338237139

Add Claude Fable 5.1 and its five effort variants
(claude-5-1-fable-low/medium/high/xhigh/max) to the Anthropic model
table in model-choice.mdx, ordered above the existing Claude Fable 5
rows per the newest-first convention. Model IDs and the default-effort
variant (high) were verified against warp-server authoritative sources
(model/types/ai/types.go, logic/ai/llm/model_choice.go,
logic/ai/llm/llm_role.go) and the enabled claude_5_1_fable feature flag.

Extend the ZDR data-retention caution below the table to cover Claude
Fable 5.1: warp-server's requiresDataRetentionWorkspace and
defaultDisabledForEnterpriseLlmIds lists both Fable 5 and Fable 5.1, so
the same off-by-default-for-Enterprise / not-available-under-ZDR
behavior applies to the new model.

Other docs surfaces that mention Fable (pricing-faqs, security-overview,
admin-panel, byollm-gemini-enterprise) already use generic
provider-retention-requirement language with no version-specific model
names, so they already cover Fable 5.1 without changes.

Co-Authored-By: Warp <agent@warp.dev>
@vercel

vercel Bot commented Sep 1, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
docs Ready Ready Preview Sep 1, 2026 7:53pm UTC

Request Review

@warp-agent-staging warp-agent-staging Bot added the warpy-factory Opened by the Warp factory agents label Sep 1, 2026
@warp-agent-staging
warp-agent-staging Bot marked this pull request as ready for review September 1, 2026 19:50
@warp-for-oss

warp-for-oss Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

@warp-agent-staging[bot]

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@warp-agent-staging

Copy link
Copy Markdown
Contributor Author

This PR was generated with Warp.

Comment @warp-factory on this PR to send it follow-up work.

View run View conversation View on Slack

@warp-for-oss warp-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This PR adds Claude Fable 5.1 model IDs to the Agent model choice reference and updates the Anthropic data-retention caution to cover the new variants. I did not find correctness, documentation-style, security, or spec-drift concerns in the annotated diff.

Concerns

  • None.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@warp-factories warp-factories Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

Small, well-scoped docs change: adds the 5 Claude Fable 5.1 effort variants to the Anthropic model table and extends the ZDR caution to cover Fable 5.1 alongside Fable 5.

Verification

  • Model IDs (claude-5-1-fable-low/medium/high/xhigh/max) match the live model catalog.
  • --changed style lint: 0 new issues (the 3 warnings on lines 164/175/191 are pre-existing and outside this diff).
  • Broken-link check: 0 broken links (3971 internal links scanned).
  • Table placement (newest-first, grouped with the existing Fable 5 rows) and caution wording/pluralization are consistent with the rest of the page.

Concerns

  • 💡 One inline suggestion below — worth a quick double-check, not blocking.

Verdict

Found: 0 critical, 0 important, 1 suggestion, 0 nits

Approve

| Claude Opus 5 | `claude-5-opus-xhigh` | Extra high effort |
| Claude Opus 5 | `claude-5-opus-xhigh-fast` | Fast mode |
| Claude Opus 5 | `claude-5-opus-max` | Max effort |
| Claude Fable 5.1 | `claude-5-1-fable-high` | Default effort |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 [SUGGESTION] The PR description notes there's no explicit "default" flag in the server catalog for Fable 5.1 (or Fable 5) — high is inferred here by matching the Fable 5 row shape. That's a reasonable inference, but since a wrong "Default effort" label would misinform readers about actual out-of-the-box behavior, it's worth a quick confirmation against the client's actual default selection (e.g. the model picker default) before merge, rather than relying solely on precedent-matching with Fable 5.

@hongyi-chen
hongyi-chen merged commit e5dc80d into main Sep 2, 2026
8 checks passed
@hongyi-chen
hongyi-chen deleted the factory/fable-5-1-model-choice branch September 2, 2026 00:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed warpy-factory Opened by the Warp factory agents

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant