Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Cerrado
  • ¿Algo no está bien?
#1,736 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Ya se ha fusionado un pull request relacionado.

  • #1737 de @tombeckenham — fusionado

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
20/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
backend-api-design

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
TypeScript
Estrellas
3.2k
Forks
361
Merge medio
1 d 8 h
PR fusionados (30 d)
266

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TanStack/ai

Todos los issues de TanStack/ai

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.