feat(ai-anthropic): support native on-demand compaction
Los mantenedores suelen responder en 1 día
@tombeckenham ya está trabajando en esto.
Desde el 7/11/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Request
Implement explicit, on-demand native compaction in @tanstack/ai-anthropic, exposed through the existing optional TextAdapter.compact() capability and consumed by withCompaction({ native: adapter }).
Current behavior
Checked @tanstack/ai-anthropic 1.1.1 and current main. The Anthropic text adapter has no compact() implementation. Passing it as native therefore uses the configured strategy. createAnthropicSummarize is ordinary chat-based summarization, not Anthropic's native compaction operation.
The existing abstraction appears suitable: #1729 added provider-native compaction, with an OpenAI Responses implementation and strategy fallback. I found no existing issue or PR requesting the Anthropic equivalent.
Why this is useful
Claude applications using TanStack's compaction middleware currently need their own provider bridge to call native compaction. That duplicates provider request mapping, capability checks, cancellation, error handling, and usage parsing. Keeping those responsibilities in the adapter would make this capability reusable across applications while retaining the existing portable strategy fallback and full-transcript/provider-context split.
This is an additional provider strategy, not a claim that native summaries are lossless or always preferable to application-defined summaries.
Provider requirements and interface gap
Anthropic documents on-demand compaction as a separate Messages request with compaction: { type: "summarize" } and the compact-2026-09-04 beta. Models expose support through capabilities.compaction.
Unlike the initial OpenAI implementation, it needs the conversation's system prompt and tool definitions, plus an explicit output allowance. TextCompactOptions currently carries system prompts but neither tools nor model options. A supported way to provide the relevant chat configuration would be needed rather than silently dropping tools or asking applications to rebuild provider serialization.
Other important behavior:
- Propagate cancellation and
wrapFetch. - Keep the compaction call outside ordinary tool execution.
- Validate
stop_reason === "compaction"and a nonempty compaction block. HTTP 200 can otherwise contain no usable summary. - Preserve provider data in the returned result, including the signature.
- Let unsupported models or unusable results enter the existing strategy fallback.
- Account for compaction usage, which Anthropic reports in
usage.iterations.
Scope
This request concerns explicit native compaction through the existing adapter/middleware model. Provider-managed threshold compaction, new persistence infrastructure, and a general signed-block replay or retained-thinking redesign are outside this request. The detailed replay contract can be discussed separately, while ensuring the native result is not reduced to unsigned text.
#1959 and #2040 address signed thinking blocks after history rewriting. They do not implement the native compaction operation requested here.
Is extending TextCompactOptions with the required chat configuration the preferred direction, or would maintainers prefer adapter-specific compaction options?
- Lenguaje dominante
- TypeScript
- Estrellas
- 3.3k
- Forks
- 378
- Merge medio
- 1 d 3 h
- PR fusionados (30 d)
- 253
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de TanStack/ai
-
openai-base: a Responses max_output_tokens cutoff ends as RUN_ERROR without usage instead of finishReason 'length'Posiblemente ocupada @tombeckenham la tomó hace 9 días. Abiertohas-pr waiting-on: maintainer
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
TanStack/ai#1916 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
@tanstack/openai-base: strict structured output skips $defs/definitions, so recursive zod schemas are rejectedPosiblemente ocupada @jherr la tomó hoy. Abiertohas-pr waiting-on: maintainer
TanStack/ai#2076 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Approval resume validates null-widened history args, so approved tools fail with repairToolInput: falsePosiblemente ocupada @tombeckenham la tomó hoy. Abiertowaiting-on: maintainer
TanStack/ai#2073 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
ai-sandbox: encrypt snapshot blobs at rest with an encrypting blob store wrapperPosiblemente ocupada @AlemTuzlak la tomó hace 1 día. Abiertowaiting-on: maintainer
TanStack/ai#2062 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Sandbox takeover: the saved transcript loses everything the first host delivered before the restartPosiblemente ocupada @tombeckenham la tomó hace 1 día. Abiertowaiting-on: maintainer
TanStack/ai#2061 · 1 asignado ·
Los mantenedores suelen responder en 1 día
Todos los issues de TanStack/ai
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
binding:python bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
coollabsio/orbit#72 ·
Los mantenedores suelen responder en 1 día
-
Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
Los mantenedores suelen responder en 1 día
-
bug needs-triage potential-regression
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
aws/aws-sdk-js-v3#8408 ·
Los mantenedores suelen responder en 1 día