Skip to content
agentgateway has joined the Agentic AI FoundationLearn more

For the complete documentation index, see llms.txt. Markdown versions of all docs pages are available by appending .md to any docs URL.

Release notes

Page as Markdown

What’s new, changed, and fixed in each agentgateway standalone release.

Review the release notes for agentgateway standalone.

Note

✨ Highlights

🔥 Breaking changes

agctl catalog import reads from the github source by default

The agctl catalog import command used to accept only one pricing source, models.dev, which was also its default. The command now accepts a second source, github, and defaults to it. The github source is the curated model catalog that the agentgateway project publishes at agentgateway.dev/model-catalog.

Flag1.5.x1.6.x
--source omittedImports from models.devImports from github
--source models.devImports from models.devUnchanged
--source githubRejected as an unsupported sourceImports from agentgateway.dev/model-catalog

The catalog file format does not change, so a catalog that you generated earlier still loads. The two sources can price a model differently, and the github source covers the models that the agentgateway project tracks rather than everything that models.dev lists.

The two sources also name some providers differently, and they disagree about what to do with an ID that they do not recognize. A --providers list that was written for models.dev can therefore go quiet rather than fail.

Behaviormodels.devgithub
Provider ID namespacemodels.dev IDs, such as google and amazon-bedrockagentgateway IDs, such as gcp.gemini and aws.bedrock
Unrecognized --providers IDFails with no providers matchedReports imported 0 providers and writes the catalog without it

Actions to take: If you regenerate your catalog on a schedule and you want to keep importing from models.dev, add --source models.dev to the command. Otherwise, regenerate the catalog and compare the rates for the models that you care about before you load the new file, because a rate change alters the costs that appear in logs, traces, metrics, and any CEL policy that reads llm.cost. For the flags, see the agctl catalog import reference.

🌟 New features

Operations

OpenTelemetry field names for stdout access logs

The stdout access log uses short, human-oriented field names, such as http.path. A new preset field on the access log policy selects a built-in field set instead. Set preset: otel to rename the built-in HTTP fields to their OpenTelemetry semantic convention equivalents, such as url.path, and to emit network.protocol.version as 1.1 rather than HTTP/1.1. The preset also adds url.scheme, and it adds server.port and url.query when the request supplies them. Note that url.path carries the path only: a query string that used to appear on http.path now appears on url.query instead.

Only the built-in HTTP field set is renamed. The gen_ai.* and mcp.* fields already use semantic convention names, fields that you add yourself keep the names that you give them, and an OTLP export is unaffected.

For the field rename table and an example, see Use OpenTelemetry field names.

Was this page helpful?
Agentgateway assistant

Ask me anything about agentgateway configuration, features, or usage.

Note: AI-generated content might contain errors; please verify and test all returned information.

Tip: one topic per conversation gives the best results. Use the + button in the chat header to start a new conversation.

Switching topics? Starting a new conversation improves accuracy.
↑↓ navigate select esc dismiss

What could be improved?

Your feedback helps us improve assistant answers and identify docs gaps we should fix.

Need more help? Join us on Discord: https://discord.gg/y9efgEmppm

Want to use your own agent? Add the Solo MCP server to query our docs directly. Get started here: https://search.solo.io/.