Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

fix(ai-anthropic): chat({ reasoning }) on Claude 4.6 sends a top-level effort and gets a 400

Chiusa
  • Qualcosa non va?
#1,736 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Una pull request collegata è già stata integrata.

  • #1737 di @tombeckenham — integrata

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
20/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
backend-api-design

Direzione di ricerca

Read packages/ai-anthropic/src/text/reasoning.ts, then inspect the request assertions in packages/ai-anthropic/tests/reasoning-request.test.ts and the Anthropic adapter note in docs/adapters/anthropic.md. Update the Claude 4.6 effort shape, its test, and the documentation as described; done means the tests expect output_config.effort and the docs match. The reporter says they are also opening a PR, so check that work before starting.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

TanStack AI version

main at 7532b2b09 (@tanstack/ai 0.68.0, unreleased). The bug came in with #1692 and is not on npm yet. Release PR #1699 is still open.

Framework/Library version

None. This is in @tanstack/ai-anthropic, on the server.

Describe the bug and the steps to reproduce it

chat({ reasoning }) on claude-opus-4-6 or claude-sonnet-4-6 sends the effort as a top-level effort field. Anthropic rejects it with a 400. Both models accept output_config.effort, the same shape the adapter already sends for Claude 4.7 and later.

Every level other than off fails. A call that sets budgetTokens is not affected, because it takes the budget path and sends no effort.

import { chat } from '@tanstack/ai'
import { anthropicText } from '@tanstack/ai-anthropic'

chat({
  adapter: anthropicText('claude-sonnet-4-6'),
  messages: [{ role: 'user', content: 'Say hi' }],
  reasoning: 'low',
})
// 400 invalid_request_error: "effort: Extra inputs are not permitted"

Live results from the Messages API on 2026-10-13, with thinking: { type: 'adaptive', display: 'summarized' }:

Model Shape Result
claude-sonnet-4-6 top-level effort: "low" 400 effort: Extra inputs are not permitted
claude-sonnet-4-6 output_config: { effort: "low" } 200
claude-opus-4-6 top-level effort: "low" 400, same message
claude-opus-4-6 output_config: { effort: "low" } 200
claude-sonnet-4-6 on /v1/messages?beta=true top-level effort: "low" 400, same message

The adapter sends every call through client.beta.messages, so the last row is the path it uses. That request had no betas header.

Where it is:

  • packages/ai-anthropic/src/text/reasoning.ts:17 defines TOP_LEVEL_EFFORT for the two 4.6 models. Line 76 returns { thinking, effort } for them.
  • packages/ai-anthropic/tests/reasoning-request.test.ts:91 pins the wrong shape ("Claude 4.6: the effort is a top-level field").
  • docs/adapters/anthropic.md:321 says "Claude 4.6 gets adaptive thinking and the top-level effort".

Suggested fix: delete TOP_LEVEL_EFFORT and always return output_config: { effort }. Drop the effort? field from AnthropicThinkingFields. Flip the test and fix the docs line.

Your Minimal, Reproducible Example - (Sandbox Highly Recommended)
curl https://api.anthropic.com/v1/messages \
  -H "x-api-key: $ANTHROPIC_API_KEY" \
  -H "anthropic-version: 2023-06-01" \
  -H "content-type: application/json" \
  -d '{"model":"claude-sonnet-4-6","max_tokens":2000,"thinking":{"type":"adaptive","display":"summarized"},"effort":"low","messages":[{"role":"user","content":"Say hi"}]}'

Swap "effort":"low" for "output_config":{"effort":"low"} and the same request returns 200.

Screenshots or Videos (Optional)

No response

Do you intend to try to help solve this bug with your own PR?

Yes, I am also opening a PR that solves the problem along side this issue

Terms & Code of Conduct
  • I agree to follow this project's Code of Conduct
  • I understand that if my bug cannot be reliable reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.
Lingua principale
TypeScript
Stelle
3.2k
Fork
361
Merge medio
1g 8h
PR unite (30g)
252

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di TanStack/ai

Tutte le issue di TanStack/ai

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.