docs(readme): add Supported model IDs table with prices and routing notes - #63
Merged
Conversation
…otes Consumers setting model_id / REVIEW_MODEL_ID had no documented list of known-good values — routing rules are pattern-based and the de facto model list only existed as the PRICES table inside bedrock-harness-executor.yml. Adds a curated table (ID, executor, approximate price, gotchas: R1 inference-profile prefix, GPT-5.5 mantle outage, Bedrock model-access grants) and cross-links it from the CLAUDE.md routing table. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WwYuXTffpbKBmfWoZAVUvU
🤖 Bedrock Review —
|
sfreudenthaler
commented
Jul 3, 2026
sfreudenthaler
left a comment
sfreudenthaler
left a comment
Member
Author
There was a problem hiding this comment.
docs update to support users that choose to have repo or org vars
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
Adds a Supported model IDs section to the README: a curated table of the
model_idvalues this team has actually run, with the executor each routes to, approximate per-MTok prices (sourced from thePRICEScost-footer table inbedrock-harness-executor.yml), and per-model gotchas. Cross-linked from the CLAUDE.md multi-model routing table.Why
Consumers setting
model_id(e.g.REVIEW_MODEL_IDin dotCMS/core) had no documented list of known-good values — the routing docs are pattern-based ("anything Bedrock serves") and the de facto model list only existed buried in Python inside a workflow file. This came up while investigating the dotCMS/core reviewer-model feedback (Slack #ai-workflows thread, 2026-07-03).Notes captured in the table
us.deepseek.r1-v1:0), not the bare model IDmodel_idsince v3.3.2 (feat(orchestrator): accept comma-separated model_id; each model reviews the PR #59)Docs-only change — no workflow behavior affected.
🤖 Generated with Claude Code
https://claude.ai/code/session_01WwYuXTffpbKBmfWoZAVUvU