Skip to content

chase-review: Anthropic models are allowed in the picker #15

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
charlesponti merged 1 commit into from
Oct 20, 2026
Merged

chase-review: Anthropic models are allowed in the picker #15

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions skills/chase-review/references/data-and-trust.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,9 +37,10 @@
- Validate at the edge with a schema; return typed errors. No trusting the client.
- Reply costs, rate limits and paid calls are visible in code and docs; say what a live test costs.
- Models and vendors: keep the model list in one place, check live model availability and
deprecation dates before choosing, and prefer cheap fast defaults. Never an Anthropic model in
Thames's picker (word, 2026-10-13). A saved choice that is no longer listed falls back to the
default.
deprecation dates before choosing, and prefer cheap fast defaults. Any vendor is allowed in
Thames's picker, Anthropic included (word, 2026-10-20; it was banned 2026-10-13). Benchmark
candidates with the app's real request before picking, and confirm each passes the live test. A
saved choice that is no longer listed falls back to the default.

## Dev services
- You may start local dev services (Metro, `pnpm dev`, API, workers, databases, Docker) to verify a
Expand Down
Loading