Weekly Update — May 4 – 11, 2026 #2125
missBerg
announced in
Weekly Updates
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
v0.6.0 shipped on Tuesday — the first production-ready API surface, with the core CRDs (
AIGatewayRoute,AIServiceBackend,BackendSecurityPolicy,GatewayConfig,MCPRoute) promoted tov1beta1. Main reopened after the cut, and a handful of provider-translation fixes plus the auth-aware MCPtools/listfilter landed in the back half of the week. Thanks to everyone who shipped, reviewed, and tested the RC. 🎉🛣️ Road to v1.0 GA
v0.6.0 is out: release notes · v0.6 docs. Headlines worth flagging if you skipped the RC:
v1beta1—AIGatewayRoute,AIServiceBackend,BackendSecurityPolicy,GatewayConfig, andMCPRouteare now served at v1beta1. v1alpha1 stays registered with deprecation warnings during the upgrade window.AIGatewayRoute.spec.filterConfigis removed — move ExtProc config to aGatewayConfigresource referenced from theGateway. The deprecatedVersionedAPISchema.version-as-prefix behavior is also gone — useprefix(e.g.prefix: /v1beta/openaifor Gemini's OpenAI-compatible API). Migration snippets are in the release notes./v1/messagesnow works on any OpenAI-compatible backend, a singlereasoning_effortknob (low/medium/high/xhigh) maps onto Anthropic, OpenAI, and Gemini thinking controls, and Gemini gets first-class embeddings plus Anthropic-style prefix context caching.forwardHeaders(with rename), JWT claim-to-header projection, andexclude/excludeRegexon tool selectors. Tool name now ships in dynamic metadata for access logs and dashboards.agent-session-id→session.idcorrelation by default, and a newReasoningTokencost type for budgeting thinking tokens separately.v1.0 tracking is still #2083 — end-of-June target unchanged.
✨ What's new
Post-release, main reopened and a small cluster of provider-translation polish and MCP work landed on top of v0.6.
MCP
tools/listfiltering — #2106 by @xadereq. MCPRoute now applies the same scope/CEL authorization rules totools/listthat already gatetools/call, so callers only see tools they can actually invoke. Closes #2105 — fixes both the wasted-turn UX and the information-disclosure footgun for consolidated/mcpendpoints.Provider & translation coverage
content_filterand adds proper OpenAI-compatible mappings forMAX_TOKENS,RECITATION,MALFORMED_FUNCTION_CALL, and friends. Big quality-of-life win for anyone debugging Gemini responses from logs.finish_reasonchunk fix — #2107 by @hustxiayang. Gemini streaming responses now always emit a finalfinish_reasonchunk with adeltaset, matching OpenAI streaming semantics.Developer experience
💡 New design proposals & feature requests
A few new threads worth a read if any of these are in your wheelhouse:
/messages→ AWS Bedrock translator — #2102 by @Killusions, with a draft implementation in #2103. Lets you point an Anthropic-format client at any Bedrock model, not just Claude — the Anthropic-shaped counterpart to today's OpenAI → Bedrock path./v1/chat/completionstoday; this adds/v1/responsestranslation against Azure's 2025-04-01-preview API. Unblocksweb_search_previewand other Responses-only tools on Azure.HTTPRoute.spec.rulesmaxItems: 16limit combined with the controller's catch-all rule means 15-ruleAIGatewayRoutes silently fail at admission with the status condition still reportingAccepted: True. Discoverability bug — design discussion is on the issue.gen_ai.client.token.usagehistogram drops requests on context cancellation — #2115 by @sc7565. ~28% of long-running Sonnet streams on Bedrock never get recorded in the histogram even though the access log captures them all; root cause looks like the OTELHistogram.Recordcall inheriting the cancelled request context. Fix is up in #2116.👀 PRs looking for review
If you have time to help review, these are open and waiting:
/messages→ AWS Bedrock translator by @Killusionsvalidatecommand in AI Gateway CLI by @Sakalya🙏 Thanks to this week's contributors
@missBerg, @nacx, @hustxiayang, @xadereq, @siddharth1036, @Killusions, @sc7565, @ajac-zero, @anurags25, @tim-peyeeye, @PatilHrushikesh, @Sakalya, @jenrik, @azaretsk, @xiaolin593, @gavrissh — and everyone who showed up to triage, review, and discuss.
See you next week!
All reactions