Skip to content

v0.13.0

Latest

Choose a tag to compare

@cldmv-bot cldmv-bot released this 19 Nov 16:27
v0.13.0
8da6da9

llm-translator v0.13.0 Changelog

Release Date: November 2026
Release Type: Minor
Branch: next → master


Overview

Version 0.13.0 adds the OpenAI Responses API on both sides of the translator. Clients such as Codex CLI can call /v1/responses, and an upstream can be reached over its own Responses API.

The upstream protocol is now one per-upstream api setting, and its default changes from Chat Completions to auto. Under auto each request goes over the client's own protocol when the server speaks it, and over Chat Completions otherwise. The most visible effect is that Claude Code pointed at vLLM 0.11.1 or later now uses vLLM's /v1/messages with no setting. Set api: "chat" on an upstream to keep the old behavior.


✨ Features

Responses API front (#174)

The OpenAI front serves POST /v1/responses and POST /v1/responses/input_tokens. Requests are stateless: input items, instructions, function tools, reasoning and structured output are converted, and the reply or SSE stream comes back as a Responses object or semantic events (response.created, response.output_text.delta, response.completed, and so on). Stateful and hosted features (previous_response_id, store: true, hosted tools) are refused with a 400. See docs/protocol-support.md. Resolves #6.

Responses API as an upstream (#173)

An upstream can be reached over /v1/responses from either client protocol. Requests are always sent with store: false, and encrypted reasoning items are carried between turns so reasoning models keep their context. The new reasoningSummary setting asks the server for reasoning summaries. A server that answers 404, 405 or 501 to /v1/responses drops back to Chat Completions, which is remembered until the next detection and reported as a fallback event. See docs/protocol-support.md. Resolves #7.

One api setting for the upstream protocol, auto by default (#177)

api takes a protocol id or an alias:

Protocol Value Aliases
Anthropic Messages anthropic.messages messages, anthropic, claude
OpenAI Chat Completions openai.chat chat, openai, chatgpt
OpenAI Responses openai.responses responses, codex
Ollama native /api/chat ollama.chat native, ollama
Detect auto (default)

Each driver lists the protocols its server speaks; vLLM, for example, speaks Messages, Chat Completions and Responses. Under auto a request uses the client's own protocol when the driver lists it, then Chat Completions. A 404, 405 or 501 moves that upstream to the next protocol until the next detection. vLLM's /v1/messages is used when the detected version is 0.11.1 or later, with the existing vLLM fixes and the conversion of bodies that endpoint can't take. An explicit value never falls back, and a value the driver doesn't list fails detection with unsupported_api. status() reports the protocol in use and the upstream's protocol list.

nativeMessages still works as a deprecated alias (true → anthropic.messages, "auto" → auto, false → openai.chat) and logs a deprecated detect event. api wins when both are set. See docs/drivers.md. Resolves #175.

🐛 Bug Fixes

  • reasoningRoundTrip after a fallback (#177): it was turned on for every request to a Responses upstream and stayed on after the upstream dropped to Chat Completions. It now follows the protocol each request actually uses, and an explicit setting still wins.
  • Token counting on vLLM (#177): a token count for an Anthropic client could pick the native /v1/messages route and send the Anthropic body to /tokenize. Token counts now always use the Chat Completions body.

📚 Documentation


Upgrade notes

  • The default upstream protocol is now auto. A Chat Completions client still gets Chat Completions on every driver. An Anthropic client now reaches vLLM 0.11.1 and later over /v1/messages, and a Responses client reaches a server that has /v1/responses over it. To keep Chat Completions for every client, set api: "chat" on the upstream.
  • api: "openai" and api: "native" keep their meaning as aliases of openai.chat and ollama.chat. An existing api: "auto" now prefers the client's protocol rather than always trying the Responses API first.
  • nativeMessages is deprecated. Replace nativeMessages: true with api: "messages" and nativeMessages: false with api: "chat", or remove it to get auto.
  • status() reports api and protocols per upstream. protocol, responses and messages are still there.

coverage

Metric Coverage
Statements 100.0%
Branches 100.0%
Functions 100.0%
Lines 100.0%

Avg: 100.0% · cb8905d · Node lts/*

👥 Contributors