The daily firehose — everything the toolchain shipped today, already filtered.
// HOW THIS ISSUE IS MADE
We read every release from the 174 tools on our watchlist at the source — GitHub and GitLab release notes, vendor release pages and changelogs, project blogs and feeds, vendor press releases, and the source code behind the tag. Bug-fix-only releases and non-product newsroom noise are dropped; what's left is summarized down to the new capability, how to try it, and any screenshots or videos the release itself published. Every entry links to the sources it was built from.
Groq is a high-speed AI inference platform that runs large language models extremely fast with minimal latency.
Groq's biggest addition this window is the OpenAI GPT-OSS 20B and 120B mixture-of-experts models with built-in browser search and code execution, alongside a broad rollout of the Qwen 3.8 27B model across Remote MCP, structured outputs, reasoning, and vision.
└──▷ WHAT SHIPPED · 4 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
OpenAI GPT-OSS 20B and 120B models addedNEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Groq added openai/gpt-oss-20b (131K token context, 32K max output, ~1000+ TPS, 32-expert MoE) and openai/gpt-oss-120b (131K token context, 32K max output, ~500+ TPS, 128-expert MoE), both with built-in browser search, code execution, and structured output support, available via the existing POST https://api.groq.com/openai/v1/chat/completions endpoint using the model field. GPT-OSS 20B scores 60.7% SWE-Bench Verified, 98.7% AIME 2025, and 85.3% MMLU; GPT-OSS 120B scores 90.0% MMLU, 62.4% SWE-Bench Verified, and 57.6% HealthBench Realistic.
Run a reasoning query against the high-throughput 20B model for latency-sensitive pipelines.
$ curl https://api.groq.com/openai/v1/chat/completions \
-H "Authorization: Bearer $GROQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "openai/gpt-oss-20b", "messages": [{"role": "user", "content": "Explain why fast inference is critical for reasoning models"}]}'
Target the 120B model for high-accuracy tasks such as health or multilingual analysis where benchmark quality matters most.
— Endpoint, model ids, curl examples, and benchmark numbers given.snapshot-20260826
02
Qwen 3.8 27B reasoning model with effort levelsNEW75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
Groq added qwen/qwen3.8-27b as a supported reasoning model with a reasoning_effort parameter accepting low, medium, or high values to tune reasoning depth.
Call the Qwen 3.8 27B reasoning model with high effort to maximise reasoning depth on complex tasks.
— Full curl example with model, param, and value shown.product docs
03
Qwen 3.8 27B multimodal vision supportNEW70how completely this was documenteddepth30/40specificity30/30actionability10/3070 / 100
Groq added qwen/qwen3.8-27b as a supported vision model — a 27B multimodal model accepting up to 3 images per request, with thinking and instruct modes, tunable reasoning effort, tool use, and JSON mode; each image counts as 2048 input tokens.
— Rich specs but no runnable example given.product docs
thinner coverage below
04
Qwen 3.8 27B added to Remote MCP and structured outputsNEW35how completely this was documenteddepth10/40specificity15/30actionability10/3035 / 100
Groq added qwen/qwen3.8-27b (Qwen 3.8 27B) as a supported model for Remote MCP tool-use and for structured outputs.
— No mechanism or example given, just model availability.product docs
OpenAI provides APIs and tools for accessing advanced language models like GPT for building AI-powered applications.
OpenAI shipped the GPT-5.6 model family with a routing alias, added persisted max-effort reasoning, Pro mode, and beta multi-agent orchestration via the Responses API, plus a full-resolution image detail option for image inputs.
└──▷ WHAT SHIPPED · 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Full-resolution image detail level in Responses APINEW85how completely this was documenteddepth25/40specificity30/30actionability30/3085 / 100
The Responses API image_url input now supports a detail: "original" option to preserve full-resolution fidelity when analysing diagrams or screenshots, demonstrated via POST https://api.openai.com/v1/responses with image_url.detail set to original.
Pass a full-resolution image with original detail to preserve fidelity when analysing diagrams or screenshots.
Darkbloom's latest releases add Qwen 3.5 video inference and EXIF-aware image decoding for Qwen vision requests, strip hardware identifiers from public APIs, refresh earnings calculators with new Mac hardware profiles, and turn on atomic first-token deadline admission by default with a documented environment-variable override.
└──▷ WHAT SHIPPED · 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Atomic first-token deadline admissionIMPROVED85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
Sets atomic first-token deadline admission to default-on for eligible requests, returning a health-neutral deadline_unreachable status before GPU prompt work begins so the coordinator can retry another provider. To fall back to unlimited partial-prefill interleave (bypassing forecast admission) while keeping hard absolute expiry, run DARKBLOOM_CBV2_MAX_PARTIAL_PREFILLS=0 darkbloom restart.
Fall back to unlimited partial-prefill interleave (bypassing forecast admission) while keeping hard absolute expiry in place.
— Includes a runnable command to override the new default.v0.8.12
02
Qwen 3.5 video inference via EngineV2NEW75how completely this was documenteddepth30/40specificity30/30actionability15/3075 / 100
Supports Qwen 3.5 video inference via EngineV2, sampling at most 8 frames at no more than 512×512 pixels per frame and bounding the vision score tensor to 512 MiB, replacing the previous 400 invalid media input failure.
— Named limits and replaced error code, but no client example given.v0.8.13
03
EXIF-aware image decode defaults for Qwen visionIMPROVED70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds EXIF-orientation-aware full-raster image decode for Qwen vision requests, defaulting enable_thinking=false for media unless the client explicitly sets reasoning.enabled.
— Named flags give reader an exact override to set.v0.8.13
04
Earnings calculator hardware inputs and profilesIMPROVED60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Updates earnings calculators to require Mac model, chip family, and unified memory inputs before showing an estimate, grounded in bandwidth-limited capacity; adds M5 Ultra and M6 hardware profiles.
— Named hardware profiles but no exact UI path given.v0.8.13
thinner coverage below
05
Hardware identifier redaction from public APIsBREAKING55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Removes hardware serial numbers, UDIDs, and raw MDA certificates from public APIs, headers, URLs, and enrollment flows; public surfaces now expose only opaque provider IDs and trust-verdict status.
— Describes scope of removal but names no specific endpoint or migration step.v0.8.13
06
mlx-swift-lm pin adds Qwen3-VL 30B-A3B supportNEW50how completely this was documenteddepth15/40specificity25/30actionability10/3050 / 100
Pins libs/mlx-swift-lm to commit fe01df9, adding Qwen3-VL 30B-A3B model support.
— Exact commit and model named but no usage example.v0.8.13
HyperFrames v0.8.15 tightens font localization so preview and final renders match, and adds compiler version stamping for traceability.
└──▷ WHAT SHIPPED · 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
thinner coverage below
01
Deterministic font localization for previewsIMPROVED50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Preview publishers now use the same font resolver as final renders, preventing CSS case transforms from altering typography between preview and export.
— Explains mechanism but no config key or flag namedv0.8.15
02
Font compiler version stamp in outputNEW30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
The font compiler version is now stamped into localized HTML output for traceability across render pipelines.
— States what changed but no field name or example shownv0.8.15
An MCP that lets AI tools securely connect to your infrastructure, write IaaS code, debug issues, and assist during incidents - without risking production stability. Built for security teams to approve and infrastructure teams to experience like magic.
emisar v0.43.0 makes a breaking change to how authorization mappings bind to identity groups, requiring a one-way migration on upgrade, alongside tighter OIDC identity verification for Okta and Entra ID, plus smaller improvements to Okta group mapping, provider setup docs, approval overrides, and transactional emails.
└──▷ WHAT SHIPPED · 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Immutable directory-group ID binding for role mappingsBREAKING85how completely this was documenteddepth35/40specificity25/30actionability25/3085 / 100
Role and runner-access mappings now bind to emisar's immutable directory-group ID rather than group name, so same-name groups stay distinct, renames preserve grants, and deleting and recreating a group never inherits old access. Upgrading to v0.43.0 requires a one-way migration: stop SSO/SCIM and mapping writes, drain every v0.42 Portal node, run the migration once, then start only the v0.43 image; after the migration commits, v0.42 is not a rollback candidate and the migration must not be run down, so rollback requires an image that understands immutable directory-group mappings.
— Full migration procedure given, but no exact CLI commandv0.43.0
thinner coverage below
02
Stricter OIDC identity convergence for Okta and EntraBREAKING55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
OIDC convergence for Okta and Microsoft Entra ID now accepts only the exact active SCIM identity under the provider's configured identifier claim; unverified email claims are denied.
— Mechanism explained, no config key or remediation step givenv0.43.0
03
Updated SSO/SCIM provider setup guidesIMPROVED50how completely this was documenteddepth15/40specificity20/30actionability15/3050 / 100
Provider setup guides for Okta, Entra, JumpCloud, Google Workspace, and Keycloak are updated to match current screens and document which OIDC and SCIM paths were live-tested.
— Names five providers but no direct doc linksv0.43.0
04
Clearer approval override audit flowIMPROVED40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
The approval override flow now collects the audited reason once and clearly states which approval count is being bypassed and which policy and runner checks still apply.
— UX change described, no exact UI path or field namev0.43.0
05
Clearer transactional approval emailsIMPROVED35how completely this was documenteddepth20/40specificity10/30actionability5/3035 / 100
Transactional emails now surface the next action first, link account context when available, express approval state in words as well as color, and keep HTML and plain-text variants aligned.
— Content changes described, no template names or samplesv0.43.0
06
Direct mapping for Okta groups without external IDNEW30how completely this was documenteddepth10/40specificity10/30actionability10/3030 / 100
Okta groups that lack an external ID can now be mapped directly to roles and runner access.
— Single-line description, no mechanism or steps givenv0.43.0
└──▷ BREAKING ON UPGRADE
!v0.43.0 includes a one-way authorization-mapping migration: stop SSO/SCIM and mapping writes, drain every v0.42 Portal node, run the migration once, then start only the v0.43 image. After the migration commits, v0.42 is not a rollback candidate and the migration must not be run down; rollback requires an image that understands immutable directory-group mappings.
Fast inference and fine-tuning for open source models
Fireworks AI added opt-in support for IdP-initiated SAML SSO alongside its existing SP-initiated login flow.
└──▷ WHAT SHIPPED · 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
IdP-initiated SAML SSO supportNEW65how completely this was documenteddepth20/40specificity20/30actionability25/3065 / 100
Custom SSO now supports IdP-initiated SAML login as an opt-in, enabled via the --enable-idp-initiated-sso flag, extending the existing SP-initiated login flow.
Get up and running with Kimi-K2.6, GLM-5.2, MiniMax, DeepSeek, gpt-oss, Qwen, Gemma and other models.
Ollama v0.33.0 adds a Claude Desktop integration on macOS and a fix that preserves the KV cache when using Claude Code.
└──▷ WHAT SHIPPED · 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Claude Desktop integration via Apps connectNEW70how completely this was documenteddepth25/40specificity20/30actionability25/3070 / 100
Ollama can now be connected to Claude Desktop on macOS as a third-party gateway so Claude Desktop can use local Ollama models, with model selection, auto-mode, and install assistance available from the menu bar. Use ollama launch claude to launch the Claude Code integration through Ollama in place of Anthropic's API.
Launch the Claude Code integration through Ollama to use a local model in place of Anthropic's API.
$ ollama launch claude
— Names UI surface and a runnable command; lacks deeper mechanism detail.v0.33.0
thinner coverage below
02
KV-cache preserving fix for Claude CodeIMPROVED53how completely this was documenteddepth25/40specificity18/30actionability10/3053 / 100
Disables Claude Code's 'tokens left' token-countdown system message injection so the KV cache is preserved across requests.
— Explains mechanism but gives no direct action or config to trigger it.v0.33.0
Explore our guides and examples to deploy your AI/ML application on Runpod. Review setup and usage guidance in the Runpod documentation.
RunPod's biggest move this window is a full Batch Jobs API for Serverless endpoints supporting asynchronous bulk inference on dedicated workers, alongside a new AWS ECR integration for private container images and advance notice that REST API v1 and the GraphQL API are being retired.
└──▷ WHAT SHIPPED · 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Batch Jobs API for Serverless endpointsNEW98how completely this was documenteddepth38/40specificity30/30actionability30/3098 / 100
RunPod Serverless adds a full asynchronous bulk-inference workflow via REST API v2, running on dedicated workers isolated from standard /run traffic so submitting a batch never delays interactive requests. Endpoints include POST /v2/{endpoint_id}/batch (create a batch, optionally with initial requests as a JSON array), POST /v2/{endpoint_id}/batch/{id}/requests (append requests to a DRAFT batch, up to 10 MiB per call, callable repeatedly to build large batches incrementally), POST /v2/{endpoint_id}/batch/{id}/finalize (lock the batch and move it from DRAFT to FINALIZED), GET /v2/{endpoint_id}/batch/{id} (poll progress via requestTotal, requestInProgress, requestCompleted, requestFailed, with createdAt as a Unix epoch millisecond timestamp), GET /v2/{endpoint_id}/batch/{id}/requests (paginated child-request results with per-request status, output, error, startedAt, completedAt, using offset/limit query params and a hasMore field), POST /v2/{endpoint_id}/batch/{id}/cancel (cancel a batch; queued requests are cancelled and not billed, in-progress requests finish and are billed normally), DELETE /v2/{endpoint_id}/batch/{id}/requests/{requestId} (remove a single request from a DRAFT batch), PUT /v2/{endpoint_id}/batch/{id} (update batch attributes such as display name), and GET /v2/{endpoint_id}/batch (list all batches for an endpoint, newest first). Completion is inferred when requestCompleted + requestFailed equals requestTotal; batch lifecycle states are DRAFT → FINALIZED → FAILED/CANCELLED. Limits are 10 active batches per endpoint, 5,000 requests per batch, and 50,000 queued requests per endpoint (up to 1,000,000 daily for enterprise, configurable for enterprise accounts). Terminal states trigger Console Inbox notifications (batch ID, endpoint name, status, item counts) and optional webhook events, and a new Batch tab in the RunPod console shows batch name, status, progress counts, per-request rows with timestamps/errors, and links to child request detail views.
Create a batch with an initial set of embedding requests and get back a batch ID to track progress.
$ curl -X POST https://api.runpod.io/v2/{endpoint_id}/batch \
-H 'Authorization: Bearer {api_key}' \
-H 'Content-Type: application/json' \
-d '[{"input":{"text":"The quick brown fox"}},{"input":{"text":"Jumped over the lazy dog"}}]'
Finalize a draft batch to lock it and start processing, then poll for completion using request counts.
Incrementally build a large batch in chunks under the 10 MiB per-call limit before finalizing.
$ # Add a second chunk of requests to a DRAFT batch
curl -s-X POST 'https://api.runpod.io/v2/{endpoint_id}/batch/batch_01j9abc123/requests' \
-H 'Authorization: Bearer {api_key}' \
-H 'Content-Type: application/json' \
-d '{"requests":[{"input":{"text":"More text to embed"}},{"input":{"text":"Another piece of text"}},{"input":{"text":"And another one"}}]}'
REST API v1 and GraphQL API retirementDEPRECATED57how completely this was documenteddepth22/40specificity20/30actionability15/3057 / 100
REST API v1 will be retired on November 15, 2026; existing integrations must migrate to REST API v2 at the new base URL https://api.runpod.io/v2 before that date. The GraphQL API will be retired in early 2027, and new integrations should use REST API v2.
AWS ECR integration for container imagesNEW50how completely this was documenteddepth22/40specificity18/30actionability10/3050 / 100
AWS ECR Integration (BETA) allows private container images to be pulled into Pods and Serverless endpoints via ECR delegation, without migrating registries or managing credentials.
!REST API v1 will be retired on November 15, 2026; existing integrations must migrate to REST API v2 at the new base URL https://api.runpod.io/v2 before that date.
!The GraphQL API will be retired in early 2027; new integrations should use REST API v2.
Daytona is an open-source development environment platform that enables developers to spin up standardized, reproducible coding environments instantly.
Daytona 0.202.0 promotes sandbox fork and snapshot creation APIs from experimental to stable.
›Promotes sandbox fork and create-snapshot to stable API, replacing the previous experimental aliases.
└──▷ BREAKING ON UPGRADE
!The experimental API aliases for sandbox fork and create-snapshot are deprecated — callers using the experimental endpoints must migrate to the stable API equivalents.
Command Code added two new free model options for users.
└──▷ WHAT SHIPPED · 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
thinner coverage below
01
MiniMax M3 Free and M2.7 Free modelsNEW35how completely this was documenteddepth10/40specificity15/30actionability10/3035 / 100
Command Code adds MiniMax M3 Free and M2.7 Free as available models.
— Names two models but no usage detail or mechanismv1.33.0
An open-source AI coding agent that lives in your terminal.
Qwen Code's desktop-v0.2.2 release adds a fast single-pass --topology minimal review mode, a new DingTalk IM channel, containerized command execution during reviews, and several daemon reliability and scheduling improvements, alongside breaking changes that migrate the desktop app from Electron to Tauri and simplify the web shell UI to compact-only view.
└──▷ WHAT SHIPPED · 13 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
`--topology minimal` review modeNEW80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
The /review skill gains a --topology minimal flag that runs a single-pass A/B review arm instead of the full multi-arm topology, reducing review overhead.
Run a fast single-pass code review in CI without the full multi-arm topology.
Autonomous coding agent as an SDK, IDE extension, or CLI assistant.
Cline shipped a new Marketplace page for plugins, MCP servers, and skills alongside a redesigned sidebar and schedule UI, while the SDK added seven new model providers, redacted git credentials from prompts, and changed the resolved default model for seven existing providers.
└──▷ WHAT SHIPPED · 11 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Default model changes across seven providersBREAKING75how completely this was documenteddepth25/40specificity30/30actionability20/3075 / 100
The resolved default model changes for ClinePass (now GLM 5.3), Z.ai, Hugging Face, evroc, LLM Gateway, NanoGPT, and Weights & Biases — users who use any of these providers without pinning a model will get a different default after upgrading.
— Names exact providers and new default, with pinning as remedysdk/sdk/v0.0.80
02
Marketplace page for plugins, MCP servers, and skillsNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds a dedicated Marketplace page consolidating plugins, MCP servers, and skills in one list with type-filter and tag chips, linked from sidebar sub-tabs and Customize headers.
— Names UI location and filters, a clear navigation starting pointdesktop-v0.0.18
03
Schedule management UX overhaulIMPROVED65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Schedule cards are now full click targets that open schedule details, with larger edit, run, pause, and delete controls. Schedule details are now a single scrollable view showing the meta grid, configuration, and most recent runs with a 'Show all N runs' expander — replacing the Overview/Runs tabs. 'Run now' now navigates directly into the session it starts.
— Detailed before/after of schedule UI behaviordesktop-v0.0.18
04
installMcpServer separator parsing fixIMPROVED65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
installMcpServer no longer treats a -- separator in the install arguments as part of the stdio command.
— Names exact command and fixed parsing behaviorsdk/sdk/v0.0.80
thinner coverage below
05
Sidebar redesign with time-sorted sessionsIMPROVED55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Sidebar is now time-sorted by default with collapsible Pinned, Scheduled, and Tasks sections and a one-click toggle to switch to project grouping; session rows now show a trash button on hover for quick deletion.
— Describes UI changes and toggle but no exact pathdesktop-v0.0.18
06
Hidden system messages in scheduled run outputIMPROVED55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Scheduled and automation runs no longer render internal [SYSTEM] steering messages, so finished sessions display as prompt, work summary, and answer.
— Clear before/after but no configuration control mentioneddesktop-v0.0.18
07
Seven new model providers addedNEW55how completely this was documenteddepth15/40specificity25/30actionability15/3055 / 100
Refreshes the model catalog with seven new providers: Agnes AI, Aixy, IteraCompute, LLM Tech, NeoSmith, Pendra, and Standard Compute.
— Names all seven providers but no setup detailsdk/sdk/v0.0.80
08
Scheduled-only mode for tasks toolNEW55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
The tasks tool can now be configured to offer only scheduled work, disabling the Todo kind while leaving the Agenda backend intact.
— Names tool and behavior but no config key givensdk/sdk/v0.0.80
09
Claude Code marked as subscription-billed providerIMPROVED50how completely this was documenteddepth25/40specificity20/30actionability5/3050 / 100
Claude Code is now marked as a subscription-billed provider, suppressing per-token prices and API-rate cost estimates; its models reuse Anthropic API pricing metadata.
— Clear behavior change but no reader action requiredsdk/sdk/v0.0.80
10
Git credential redaction from system promptIMPROVED40how completely this was documenteddepth20/40specificity15/30actionability5/3040 / 100
Credentials embedded in git remote URLs are now redacted from the workspace information included in the system prompt, preventing them from leaking into workspace context sent to models.
!The resolved default model changes for ClinePass (now GLM 5.3), Z.ai, Hugging Face, evroc, LLM Gateway, NanoGPT, and Weights & Biases — if you use any of these providers without pinning a model, you will get a different default after upgrading.
Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.
Claude Code v2.1.246 focuses on permission and safety visibility, adding an Auto mode rules tab and Bash wildcard warnings, alongside smoother directory switching, subagent turn handling, and non-interactive session resilience.
└──▷ WHAT SHIPPED · 8 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
/cd applies settings immediatelyIMPROVED80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
Improves /cd so the new directory's project settings, hooks, .mcp.json servers, skills, and agents all take effect immediately instead of waiting for --resume.
— Exact command with clear before/after behaviorv2.1.246
02
Bash wildcard rule safety warningNEW75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
Adds a startup warning when Bash allow rules contain a wildcard before the subcommand (e.g. Bash(git * main)), flagging rules that also match options injected before the subcommand.
— Concrete example and mechanism of the flagged riskv2.1.246
03
Subagent partial output on maxTurns limitIMPROVED70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Improves subagent results: a subagent that hits its maxTurns limit now returns output marked as partial with a hint to continue via SendMessage, rather than appearing finished.
— Names the limit and continuation mechanismv2.1.246
04
Auto mode tab in /permissionsNEW60how completely this was documenteddepth20/40specificity20/30actionability20/3060 / 100
Adds an Auto mode tab to /permissions for viewing and editing auto mode classifier rules.
— Names exact command but not classifier rule mechanicsv2.1.246
05
Auto-continue for interrupted non-interactive responsesIMPROVED60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Improves non-interactive sessions (-p, SDK, cloud sessions) to automatically continue a response cut off mid-stream by a server error, connection loss, or stall.
— Names affected session types, no config detailv2.1.246
06
/code-review works across more platformsIMPROVED60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Changes /code-review so Claude can initiate it on Bedrock, Vertex AI, Foundry, the Claude apps gateway, and when telemetry or non-essential traffic is disabled.
— Lists platforms but no mechanism of the fixv2.1.246
07
/goal idle check-in limitsIMPROVED60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Changes /goal idle sessions to start at most three check-ins per goal on long-running background work; the next user message allows three more.
— Specific numeric limit and reset condition givenv2.1.246
thinner coverage below
08
Turn completion wall-clock timestampNEW40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Adds the turn's wall-clock completion time to the end-of-turn duration line, e.g. ✻ Sautéed for 23s · done 6:05 PM.
— Cosmetic addition described only brieflyv2.1.246
Lightweight coding agent that runs in your terminal
OpenAI Codex CLI's alpha releases add per-turn cyber access program selection, a computer-use-only scope for Guardian v2 approvals, and managed AWS Bedrock authentication, alongside hardened MCP OAuth callback handling and a breaking restriction of --code-mode-host to HTTP(S) gRPC endpoints.
└──▷ WHAT SHIPPED · 12 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
gRPC-only restriction for `--code-mode-host`BREAKING80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
The app server --code-mode-host flag now accepts only http:// and https:// gRPC endpoints; WebSocket (ws://, wss://) host URLs are rejected at CLI parse time, so any configuration passing a WebSocket URL will fail at startup.
— Exact flag with before/after behavior and startup failure impact.rust-v0.150.0-alpha.11
02
Per-turn cyber access program selectionNEW75how completely this was documenteddepth25/40specificity30/30actionability20/3075 / 100
Adds an experimental turn/start.cyberAccessProgram option with standard, daybreakBlue, and daybreakRed values, forwarded as access_programs.cyber on Responses, WebSocket, and remote-compaction requests when using ChatGPT authentication.
— Config key and values named but marked experimental with no usage example.rust-v0.150.0-alpha.11
03
Time-bounded diagnostics flag for `codex doctor`NEW70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
Adds a hidden --feedback flag to codex doctor that bounds each SQLite database integrity scan to a one-second deadline when collecting diagnostic attachments.
— Exact command and flag given, though hidden and narrow in scope.rust-v0.150.0-alpha.11
04
Amazon Bedrock authentication supportNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds an amazonBedrockAccessKeys login flow that persists SigV4-signed credentials in the configured auth store and reports bedrockAccessKeys as a distinct auth mode, plus Amazon Bedrock setup added to the TUI onboarding flow.
Hardened MCP OAuth callback handlingIMPROVED60how completely this was documenteddepth30/40specificity20/30actionability10/3060 / 100
Validates issuer-bound authorization responses, persists registered callback URLs for MCP servers and plugins, and inserts the active listener port into portless loopback redirects.
— Mechanism described but no config surface for the reader to act on.rust-v0.150.0-alpha.11
thinner coverage below
06
`root_turn_id` field in turn analyticsNEW50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Adds a root_turn_id field to turn and tool-item analytics events to associate subagent activity with its originating top-level turn.
!The app server --code-mode-host flag no longer accepts ws:// or wss:// URLs; only http:// and https:// gRPC endpoints are valid. Any configuration passing a WebSocket URL to --code-mode-host will fail at startup.
An open-source AI agent that brings the power of Gemini directly into your terminal.
Gemini CLI's biggest addition this window is Agent Skills — installable, on-demand expertise bundles with a full CLI and in-session command surface — alongside smaller improvements to eval diagnostics.
└──▷ WHAT SHIPPED · 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Agent Skills system with install, discovery and session managementNEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Adds a full Agent Skills subsystem: skills are installable, on-demand expertise bundles discovered from four precedence-ordered tiers — built-in, extension, user (~/.gemini/skills/ or ~/.agents/skills/), and workspace (.gemini/skills/ or .agents/skills/), the last two using an interoperable .agents/skills/ path alias so directories stay compatible across other AI tools. CLI commands: gemini skills install <url|path> --consent (with --scope user|workspace) installs a skill from a Git repo or local directory; gemini skills list --all lists all discovered skills across every tier including hidden built-ins; gemini skills uninstall <name> --scope workspace removes one. In-session commands: /skills list [all] [nodesc] shows discovered skills (with flags to surface built-ins or suppress descriptions), /skills link <path> [--scope user|workspace] links skills from an arbitrary local directory, /skills disable <name> and /skills enable <name> toggle skills without uninstalling, and /skills reload (alias /skills refresh) rescans all discovery tiers mid-session. A new activate_skill tool is called automatically by the model when a task matches a skill's description, injecting the skill's SKILL.md and granting the agent read access to its bundled assets.
Install a team-shared security-auditing skill from a Git repo into your workspace so every contributor picks it up via version control.
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
Graphify extended its enum graph modeling to C# and TypeScript, and shipped fixes to postgres SQL grammar installation, multi-repo community detection, and ignore-pattern performance.
└──▷ WHAT SHIPPED · 4 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Postgres extra installs SQL grammar dependencyIMPROVED85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
Installing graphifyy[postgres] now includes the tree-sitter-sql grammar required by the SQL introspection path, and a missing or ABI-incompatible grammar raises an actionable error instead of silently returning zero nodes.
Install Graphify with the postgres extra to get the SQL introspection grammar and actionable errors on grammar mismatches.
Enum member nodes for C# and TypeScriptNEW70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
C# and TypeScript enum members now each emit a graph node with a case_of edge to their parent enum, covering explicit and implicit values, const enum, and quoted TypeScript member names — matching existing Java/Kotlin/Swift enum handling.
— Names edge type and edge cases but no runnable example given.v0.9.50
03
Community id offsetting for multi-repo analysisIMPROVED70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Multi-repo community detection now offsets each input's community ids so community 0 of one repo no longer fuses with community 0 of another; the original id is preserved in the local_community field.
— Names the field and bug fixed but no command to invoke.product docs
thinner coverage below
04
Faster ignore-pattern evaluation in monoreposIMPROVED55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Ignore-pattern evaluation in pattern-heavy monorepos is dramatically faster: relative paths are now computed lexically, each pattern is parsed once into a bounded process cache, and per-entry work is memoized; ignore decisions themselves are unchanged.
— Explains mechanism but offers no user-facing action or flag.product docs
An old coder's strategy for the agent era: don't read the code — make it run the gauntlet. Evidence-first development skill for coding agents, inspired by Uncle Bob.
Adds Java, Scala, SQL, and Emacs Lisp support; new source-state binding, fail-closed gauntlet orchestration, and PYTHONDONTWRITEBYTECODE mutation isolation.
└──▷ GET THIS VERSION
$ git clone --branch commits-2026-07-27 https://github.com/AmazingAng/old-coder.git
# already have the repo? check out this version:$ git checkout commits-2026-07-27
└──▷ TRY IT
Run mutation tests with bytecode caching disabled to prevent silent reuse of stale .pyc files between mutants of identical size written in the same second.
Capture a reproducible, fail-closed source-state binding before running the gauntlet, so evidence can be tied to a specific, provenance-verified tree.
$ python demo-rate-limiter/tools/source_state.py
Verify that the gauntlet fails closed when a layer is omitted or a layer command breaks, using the negative-control harness.
$ sh demo-rate-limiter/tools/test_gauntlet_orchestration.sh
›Adds PYTHONDONTWRITEBYTECODE=1 via MUTANT_ENV in demo-rate-limiter/tools/mutants.py to prevent stale .pyc bytecode from silently reusing a prior mutant's compiled code between mutation runs.
›Introduces demo-rate-limiter/tools/source_state.py, a new script that produces a deterministic, fail-closed binding for the demo source tree, withholding provenance when Git history is shallow.
›Adds demo-rate-limiter/tools/test_gauntlet_orchestration.sh, a negative-control harness that verifies the gauntlet fails closed when a layer is omitted and that a broken layer command halts execution and names the failed layer.
›Adds supply-chain and suite-health gauntlet layers to the orchestration set.
›Extends language support to Java, Scala, SQL, and Emacs Lisp (PR #2).
+4 moreshow less
›Specifies fail-closed gauntlet orchestration: a skipped or missing layer causes the final audit to fail and name the offending layer.
›Adds a VERIFY protocol step and two gauntlet rules derived from the independent verification experiment; verification is now explicitly source-state-specific and human-graded.
›Splits gauntlet templates out of gauntlet.md and divides 'skipped layers' into three distinct categories.
›Adds CONTRIBUTING.md defining the contribution bar and the rationale for the unusual review process here.
A high-throughput and memory-efficient inference and serving engine for LLMs
vLLM v0.28.0 ships disk-backed tiered KV cache offloading, a major Model Runner V2 expansion with E/P/D disaggregation, and broad hardware/quantization support spanning NVIDIA Blackwell, AMD ROCm, Intel XPU and s390x, alongside breaking changes that migrate bitsandbytes out-of-tree and remove deprecated attention/KV-scale options.
└──▷ WHAT SHIPPED · 14 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Legacy quantization and config options removedBREAKING80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
bitsandbytes support has been migrated to an out-of-tree plugin, so existing setups using bitsandbytes quantization will break without installing the plugin separately; the Transformers dependency has been bumped to 5.15.0, breaking incompatible models or configurations; the deprecated calculate_kv_scales runtime KV scale calculation has been removed; and override_attention_dtype has been removed, so any configuration or code using these options will fail.
— Names each removed/changed option and its exact breaking impactv0.28.0
02
Tiered KV cache offloading enhancementsNEW78how completely this was documenteddepth30/40specificity28/30actionability20/3078 / 100
Adds module_path config key for out-of-tree secondary KV cache tier managers, enabling custom offloading backends without forking vLLM; adds disk offloading support for SimpleCPUOffloadConnector, extending tiered KV cache to persistent storage; adds tiering offloading metrics for observability into KV cache tier behavior; adds a canonical CPU layout for parallelism-agnostic KV cache offload; adds partial secondary-tier KV load results support allowing partial cache hits from offload storage; and adds data-parallel topology exposure to offloading backends.
— Names config key and mechanisms but no runnable usage examplev0.28.0
03
New generation API request fieldsNEW75how completely this was documenteddepth25/40specificity30/30actionability20/3075 / 100
Adds count_reasoning_tokens field to the streaming parser engine for tracking reasoning token counts, content_parts field on /inference/v1/generate for richer multimodal generation requests, request priority parsed from an HTTP header enabling priority-based scheduling, session ID plumbing into requests for stateful session tracking, and makes model optional on all /derender request classes.
— Names endpoint and fields but no example payload providedv0.28.0
04
Hardware and quantization backend expansionNEW75how completely this was documenteddepth30/40specificity30/30actionability15/3075 / 100
Adds FlashInfer XQA decode support on SM12x (Blackwell), a CuTeDSL fused query kernel on SM100, an MLA backend enabling DeepSeek-V2/V3 inference on CPU, GPTQ and AWQ quantization support on s390x, AITER and FP8 inference on GFX120x (AMD ROCm), a triton-cpu wheel for CPU-based Triton kernels, an XPU wheel in the release pipeline, online MXFP4 quantization support, batch-invariant NVFP4 MoE via CUTLASS, a block-wise scaled_mm kernel for quantization, and AMD Quark NVFP4 support with an emulation kernel for DeepSeek-V4.
— Many named backends and kernels but no benchmark or setup stepsv0.28.0
05
Model Runner V2 capability expansionNEW73how completely this was documenteddepth30/40specificity28/30actionability15/3073 / 100
Model Runner V2 gains E/P/D (encode/prefill/decode) disaggregation support, encoder CUDA graphs, decoder token-wise pooling and Transformers pooling models, attention-free model support, multi-layer MTP KV cache support, weight offloading, and thinking_token_budget support for controlling reasoning token budgets.
— Lists several mechanisms but no config path shown to enable themv0.28.0
06
Speculative decoding advances for DeepSeek and KimiNEW70how completely this was documenteddepth30/40specificity28/30actionability12/3070 / 100
Adds sparse MLA end-to-end support for plain decode, MTP, and DSpark speculative decoding in DeepSeek V4; adds DFlash2 speculative decoding with local convolution and a candidate selector; adds DSpark confidence-scheduled verification for speculative decoding; adds async scheduling auto-enabled for draft models; and adds EAGLE3 speculative decoding support on KimiLinear.
— Detailed mechanisms named but no flag shown to enable themv0.28.0
07
Default scheduling and cache tuning changesIMPROVED70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Raises default max_num_batched_tokens from 8192 to 16384, raises the Blackwell CUDA graph capture default to 1024, and enables prefix caching by default for Mamba models.
— Exact before/after default values make this directly actionablev0.28.0
08
New model architectures and multimodal supportNEW68how completely this was documenteddepth28/40specificity28/30actionability12/3068 / 100
Adds vision tower LoRA support for Gemma4, Keye, and Ultravox models; adds native multimodal support for Dots3 NOTE; adds new models Muse Glimmer, Ling 3.0 Flash (BF16/MTP/FP8/MXFP4), and Interns2mobius; and adds a Transformers modeling backend with MLA support, hardware-agnostic model definition, logit softcapping, and generalized input embedding handling.
— Names models and formats but no load command shownv0.28.0
09
Reinforcement learning workflow supportNEW68how completely this was documenteddepth25/40specificity28/30actionability15/3068 / 100
Adds CuMemAllocator.discard() for tag-selective GPU memory release in RL workflows, Mooncake store group semantics and tenant ID support with official wheels shipped in the Docker image, and stateful trainer send over NCCL with sparse NCCL support for RL workflows.
— Names API method and NCCL mechanism but limited usage guidancev0.28.0
10
Rust/gRPC frontend multimodal and control featuresNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds a Rust frontend standalone renderer with gRPC multimodal image inference support, explicit data-parallel rank routing and RL lifecycle control, publishes protobuf schemas for the gRPC frontend to Buf, and adds dynamic tools from developer messages in the Rust frontend.
— Names schema publication surface but no endpoint usage detailv0.28.0
11
Kimi-K3 parallelism and memory optimizationsNEW62how completely this was documenteddepth25/40specificity25/30actionability12/3062 / 100
Adds Decode Context Parallel (DCP) support for Kimi-K3, and optional shared-expert sharding for Kimi-K3 saving ~17 GiB of memory per GPU.
— Concrete memory-savings figure but no enabling flag givenv0.28.0
12
Structured output validation hardeningIMPROVED60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Adds NUL byte rejection in structured_outputs.regex and negative token ID rejection for structured output robustness, and adds VLLMValidationError raised from structured output validators.
— Named config field and exception class, limited mechanism detailv0.28.0
thinner coverage below
13
Startup and execution reliability improvementsIMPROVED56how completely this was documenteddepth22/40specificity22/30actionability12/3056 / 100
Adds file:// rendezvous for single-node executors to eliminate startup port races, a CI GPU<->CPU sync check to guard against accidental synchronization regressions on the execution path, and JIT warmup infrastructure with predicate filtering.
— Named mechanisms but mostly internal/CI-focused with limited user actionv0.28.0
14
Developer observability and deployment toolingNEW52how completely this was documenteddepth20/40specificity20/30actionability12/3052 / 100
Adds output token IDs logged at DEBUG level, vLLM Recipes integration with native config-based deployment and benchmarking, and a minimal Triton Proton profiling backend.
— Names tools but no configuration steps givenv0.28.0
└──▷ BREAKING ON UPGRADE
!bitsandbytes support has been migrated to an out-of-tree plugin; existing setups using bitsandbytes quantization will break without installing the plugin separately.
!Transformers dependency bumped to 5.15.0; models or configurations incompatible with Transformers 5.15.0 will break.
!The deprecated calculate_kv_scales runtime KV scale calculation has been removed; any configuration or code referencing it will fail.
!override_attention_dtype has been removed; any configuration or code using this option will fail.
Open-Source Evaluation & Testing library for LLM Agents
Giskard v3 is a full rewrite into a modular monorepo (giskard-checks, giskard-agents, giskard-core, giskard-scan) that adds automated OWASP LLM Top-10 red-teaming, Suite-based batch evals with JUnit XML export, new LLM judge checks, and a provider-agnostic giskard-llm routing layer, alongside several breaking API removals.
└──▷ WHAT SHIPPED · 8 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
V3 rewrite into modular monorepo packagesBREAKING93how completely this was documenteddepth35/40specificity30/30actionability28/3093 / 100
Giskard v3 is a full rewrite structured around three installable packages — giskard-checks, giskard-agents, and giskard-core — with giskard-scan available via pip install 'giskard[scan]'. The rewrite drops v2 APIs (giskard.Model, giskard.Dataset, giskard.testing, Giskard Hub); those needing v2 must pin pip install 'giskard[llm]>2,<3'. It now requires Python 3.12+, removes Scenario.from_sequence and the scenario() factory in favor of the step-based mutable Scenario constructor, drops templating support in conformity rules, makes Jinja parsing in Workflow.chat opt-in instead of default, and switches the Interact injection to name-based instead of positional.
— Full breaking migration list with exact removed APIs and install commands.v3.0.0
02
OWASP LLM Top-10 vulnerability scanningNEW86how completely this was documenteddepth30/40specificity28/30actionability28/3086 / 100
Adds a vulnerability_scan function in giskard-scan for automated red-teaming across OWASP LLM Top-10 threat categories including prompt injection, harmful content, stereotypes, and misinformation, plus a minimal OWASP LLM suite generator covering LLM01 indirect injection.
Automatically red-team your agent across OWASP LLM Top-10 categories, including prompt injection probes, without writing test cases manually.
python
import asyncio
from giskard.scan import vulnerability_scan
async def my_agent(inputs: str) -> str:
return f"Echo: {inputs}" # replace with your real agent
async def main() -> None:
await vulnerability_scan(
target=my_agent,
description="A customer support chatbot for an e-commerce platform.",
languages=["en"],
)
asyncio.run(main())
— Named function with a runnable scan example against OWASP categories.v3.0.0
03
Suite batching and reporting for Scenario evalsNEW83how completely this was documenteddepth30/40specificity28/30actionability25/3083 / 100
Introduces Suite for running batches of scenarios with dynamic binding, with a chainable Suite.append(), and allows scenarios to run multiple times within a suite. Adds print_report() to result models for human-readable check output, adds scenario and check error details to suite reports, adds JUnit XML export for SuiteResult for CI integration, and adds annotations support to Scenario/trace objects for attaching metadata to eval steps.
Run a grounded-answer eval on your agent and print a human-readable report to spot hallucinations immediately.
python
import asyncio
from giskard.checks import Scenario, Groundedness
def get_answer(inputs: str) -> str:
return my_agent(inputs) # replace with your model/agent
async def main() -> None:
scenario = (
Scenario("test_capital")
.interact(inputs="What is the capital of France?", outputs=get_answer)
.check(
Groundedness(
name="answer is grounded",
context="France is in Western Europe. Its capital is Paris.",
)
)
)
result = await scenario.run()
result.print_report()
asyncio.run(main())
— Named Suite API plus a runnable Scenario/print_report example.v3.0.0
04
Opt-out telemetry via environment variablesNEW70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
Adds opt-out telemetry to giskard-core, disabled by setting DO_NOT_TRACK=1 or GISKARD_TELEMETRY_DISABLED=1, collected through optional PostHog analytics.
— Exact environment variable names to disable telemetry.v3.0.0
05
New evaluation checks in giskard-checksNEW68how completely this was documenteddepth25/40specificity28/30actionability15/3068 / 100
Adds RegexMatching for asserting outputs match a regular expression with ReDoS mitigation via regex timeout, AllOf, AnyOf, and Not composition operators for combining checks with boolean logic, AnswerRelevance and Toxicity LLM judge checks, a JSON validity check, and a new judges directory for LLM- and prompt-reliant checks. Checks now also accept pydantic-compatible input types.
— Lists each new check by name but no usage example.v3.0.0
06
giskard-llm provider-agnostic routing layerNEW65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
Introduces giskard-llm as a lean, provider-agnostic LLM routing layer replacing litellm, supporting provider extras such as openai and anthropic installable via pip install 'giskard[openai]'.
— Named replacement layer and install command but no usage example.v3.0.0
07
String-based default generator configurationIMPROVED65how completely this was documenteddepth20/40specificity20/30actionability25/3065 / 100
set_default_generator now accepts plain model name strings (e.g. 'openai/gpt-4o') in addition to generator objects, reducing boilerplate when configuring the default LLM judge or generator.
Set the default generator for LLM-as-judge checks using a model name string instead of constructing a generator object.
python
from giskard.checks import set_default_generator
set_default_generator('openai/gpt-4o-mini')
Generator improvements in giskard-agentsNEW59how completely this was documenteddepth22/40specificity25/30actionability12/3059 / 100
Adds personas and extended context support for UserSimulator in generators, a metadata parameter to the generator completion pipeline, generator retry and timeout policies, a step-level type discriminator with tool input coercion and output serialization, and a generator-as-protocol-adapter pattern for wrapping arbitrary LLM backends.
— Names each mechanism but has no usage example.v3.0.0
└──▷ BREAKING ON UPGRADE
!Giskard v3 is a full rewrite; v2 APIs (giskard.Model, giskard.Dataset, giskard.testing, Giskard Hub) are not available in v3. Install pip install 'giskard[llm]>2,<3' to keep v2.
!Requires Python 3.12+; Python versions below 3.12 are no longer supported.
!Scenario.from_sequence is removed; use the step-based Scenario API instead.
!Templating in conformity rules is no longer supported; configurations relying on template syntax in conformity rules will break.
!Jinja parsing in Workflow.chat is now opt-in; workflows that relied on Jinja template rendering by default will no longer render templates unless explicitly enabled.
!The Interact injection is now name-based; code using positional injection patterns will break.
!The scenario() factory is removed; use the mutable Scenario constructor directly.
OpenShell is the safe, private runtime for autonomous AI agents.
OpenShell v0.0.113 adds OTLP trace export for Docker sandboxes and corporate CA trust for Podman HTTPS proxies, improving observability and enterprise network compatibility.
└──▷ WHAT SHIPPED · 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
thinner coverage below
01
OTLP trace export for Docker driverNEW40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
OpenShell now exports Docker driver traces over OTLP, letting observability pipelines ingest sandbox container activity.
— Names OTLP and Docker but no config key or commandv0.0.113
02
Corporate CA trust for Podman proxiesNEW40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
OpenShell trusts corporate CA certificates for HTTPS proxies and intercepted TLS traffic in Podman-backed sandboxes.
— Describes behavior but no setup steps or flags namedv0.0.113
HolmesGPT 0.40.0 is primarily a security-hardening release — SSRF allowlisting for tcp_check probes, a diagnostic-pod target policy, and injection fixes in the bash and kubectl-run toolsets — alongside new personal skills with a per-account collision hierarchy, several MCP integration updates, and the removal of the Azure SQL toolset and MariaDB MCP integration.
└──▷ WHAT SHIPPED · 10 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
MCP integration auth and version updatesIMPROVED74how completely this was documenteddepth28/40specificity28/30actionability18/3074 / 100
Scopes the __robusta_user_approved field to relay-routed remote MCP calls instead of all MCP traffic, wires Kubernetes-remediation MCP bearer-token auth in the Helm chart, and updates the GitLab MCP integration to v2.1.46 with a whoami health check.
— Names field, integration, version and health check0.40.0
02
kubectl-run toolset executes without host shellIMPROVED65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Hardens the kubectl-run toolset to execute commands without a host shell, eliminating shell injection paths.
Removed Azure SQL toolset and MariaDB MCP integrationBREAKING65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Removes the experimental Azure SQL toolset entirely, and removes the MariaDB MCP integration, consolidating MariaDB support into the native MariaDB datasource; deployments using either must migrate accordingly.
— Names both removed surfaces and the migration path0.40.0
04
Oversized tool-error results capped and spilled to fileIMPROVED62how completely this was documenteddepth28/40specificity22/30actionability12/3062 / 100
Tool errors that produce oversized results are now capped: a 500-character gist is inlined in the response and the full content is spilled to a file.
— Gives exact character limit but no file path or flag0.40.0
thinner coverage below
05
Bash toolset validates arguments and redirectionsIMPROVED55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
The bash toolset now validates command arguments and redirections, not just the command prefix, closing injection vectors that could bypass prefix-only checks.
— Names the toolset and mechanism, no exact flag0.40.0
06
tcp_check allowlist required for private-network probesBREAKING50how completely this was documenteddepth22/40specificity18/30actionability10/3050 / 100
tcp_check probes can no longer reach private networks unless the target is on an allowlist, blocking SSRF to internal hosts by default.
— Describes the default-deny behavior but names no config key0.40.0
07
Personal skills with per-account collision hierarchyNEW45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Adds personal skills and a per-account name-collision hierarchy so individual users can define skills that don't conflict with shared or global ones.
— Explains behavior but gives no UI or config path0.40.0
08
Diagnostic-pod target policy limits SSRF and exfiltrationNEW41how completely this was documenteddepth18/40specificity15/30actionability8/3041 / 100
Adds a diagnostic-pod target policy to prevent SSRF and data exfiltration from pods spawned during investigations.
— Names the policy's purpose but not its config surface0.40.0
09
Skill titles surfaced in fetch_skill resultsIMPROVED35how completely this was documenteddepth10/40specificity15/30actionability10/3035 / 100
UI-added skills now surface their titles in fetch_skill results.
OpenWorker added support for the Ox Alpha stealth preview model via OpenRouter, giving users a large-context, tool-calling capable model option ahead of its official release.
└──▷ WHAT SHIPPED · 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Ox Alpha stealth model via OpenRouterNEW73how completely this was documenteddepth25/40specificity28/30actionability20/3073 / 100
Adds openrouter:stealth/ox-alpha to the model matrix, exposing the Ox Alpha stealth/cloaked lab preview via OpenRouter with a 1,048,576-token context window and tool-calling capability. Selectable in the model selector as 'Ox Alpha · via OpenRouter' from the OpenRouter section.
Select the Ox Alpha stealth preview to run long-context agentic tasks via OpenRouter before the model's official release.
📍In the model selector, choose 'Ox Alpha · via OpenRouter' from the OpenRouter section of the model list.
— Names exact model id, context size, and selection steps.v0.2.1
LangSmith is a platform for debugging, testing, and monitoring LLM applications built with LangChain.
LangSmith's biggest window changes are credential-free S3 exports via AWS IAM role assumption and a new natural-language Chat interface on the Engine page for triaging flagged issues; alongside these, the platform picked up thread-to-dataset UI support, a new paginated experiment-comparison API (with legacy helpers removed), thread-evaluator testing parameters, project/user trace-limit enforcement, split-management improvements in experiments, a workspace cap on reusable evaluators, a zstd default for bulk-export compression, and OpenTelemetry resource-attribute support on traces.
└──▷ WHAT SHIPPED · 5 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
New experiment-runs API, legacy comparison helpers removedBREAKING80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
A new public POST /v2/datasets/{dataset_id}/experiment-runs endpoint provides paginated experiment comparison; legacy dataset comparison helpers have been removed from the public OpenAPI spec and generated SDKs, though existing HTTP routes continue to work for LangSmith UI clients only.
— Exact endpoint and breaking scope named, but no usage example.snapshot-20260826
02
Chat interface on the Engine pageNEW65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
A new Chat interface on the Engine page lets practitioners ask natural-language questions about a detected issue and its linked traces, such as 'What went wrong?', 'Why was this flagged?', 'Explain the proposed fix', 'What are my most pressing issues?', and 'How many new issues do I have?'.
When triaging flagged traces in LangSmith Engine, open Chat to quickly understand a detected issue without manually inspecting each linked trace.
📍In LangSmith, go to Engine › (select an issue) › Chat, then ask 'What went wrong?' or 'Explain the proposed fix'.
— Gives exact navigation and example prompts, no deeper mechanism.product docs
03
zstd default for bulk-export compressionIMPROVED65how completely this was documenteddepth20/40specificity20/30actionability25/3065 / 100
Self-hosted LangSmith bulk exports now default to zstd compression instead of gzip; the previous gzip behavior can be retained by setting FF_BULK_EXPORT_DEFAULT_COMPRESSION=gzip.
Retain gzip compression for bulk exports on a self-hosted LangSmith deployment instead of the new zstd default.
$ FF_BULK_EXPORT_DEFAULT_COMPRESSION=gzip docker compose up
Add threads to a dataset from the UINEW25how completely this was documenteddepth10/40specificity5/30actionability10/3025 / 100
LangSmith's UI now lets you add threads directly to a dataset.
— Bare description with no navigation path or mechanism given.product docs
05
Workspace-level cap on reusable evaluatorsNEW20how completely this was documenteddepth10/40specificity5/30actionability5/3020 / 100
A workspace-level cap on reusable evaluators was introduced to prevent unbounded resource growth.
— No limit number, mechanism, or configuration path given.snapshot-20260826
└──▷ BREAKING ON UPGRADE
!Legacy dataset comparison helpers are removed from the public OpenAPI spec and generated SDKs (existing HTTP routes continue to work for LangSmith UI clients only).
Open-source observability tool that uses AI agents to self-heal your software
Superlog adds Railway structured log parsing, GCP log filters, Cloudflare Workers support, and Google Cloud integration disconnect
└──▷ GET THIS VERSION
$ git clone --branch commits-2026-07-27 https://github.com/superloglabs/superlog.git
# already have the repo? check out this version:$ git checkout commits-2026-07-27
└──▷ TRY IT
Disconnect a previously authorized Google Cloud integration via the API.
Phoenix 20.4.0 reshapes the model providers REST API with a breaking change, adds a per-project retention endpoint, a retrieval relevance evaluator, and an in-process MCP toolset, alongside smaller additions to Playground, PXI and trace filtering.
└──▷ WHAT SHIPPED · 9 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Model providers REST endpointBREAKING90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds GET /v1/model_providers exposing built-in model provider entries with a provider field. This is a breaking change: the endpoint no longer returns custom providers or a next_cursor field, and built-in entries now expose provider instead of kind and provider_key; custom providers are now served separately by GET /v1/custom_model_providers.
!GET /v1/model_providers no longer returns custom providers or a next_cursor field; built-in entries now expose a provider field instead of kind and provider_key. Custom providers are now served by GET /v1/custom_model_providers.
Open source AI engineering platform: LLM evals, observability, metrics, prompt management, playground, datasets. Integrates with OpenTelemetry, LangChain, OpenAI SDK, LiteLLM, and more. YC W23
Langfuse v4.19.0 adds a model definition upsert API endpoint and org-level feature flag default settings.
└──▷ WHAT SHIPPED · 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
thinner coverage below
01
Model definition upsert API endpointNEW40how completely this was documenteddepth15/40specificity10/30actionability15/3040 / 100
A new API endpoint enables programmatic create-or-update of model definitions, so model definitions can be managed without manual UI edits.
— Endpoint's method and path not specified in source.v4.19.0
02
Org-level feature flag defaultsNEW33how completely this was documenteddepth15/40specificity8/30actionability10/3033 / 100
Administrators can now set org-level settings for feature flag defaults, controlling feature preview defaults across an entire organization.
Braintrust is an open-source evals framework for testing and monitoring AI applications with custom test cases and metrics.
Braintrust shipped Topics, an automatic log-classification and monitoring system with custom facets, alongside a full REST API client, MCP server write tools, remote eval sandboxes, reasoning-model evaluation, and a wave of SDK tracing improvements and breaking changes across Python, TypeScript, and Go.
└──▷ WHAT SHIPPED · 21 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Eino span output format changeBREAKING90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
Go SDK v0.11.1 (Eino): ChatModel span output is now an OpenAI-compatible choices array ([{"index": 0, "finish_reason": "...", "message": {...}}]) instead of a flat message map; embedding input is now {"inputs": [{"content": "..."}]} and output is {"count": N}, removing embedding_length and renaming embeddings_count; provider metadata is now lowercase (e.g. "openai" instead of "OpenAI"). Update trace queries that rely on the previous formats.
Topics automatic log classification and managementNEW88how completely this was documenteddepth35/40specificity28/30actionability25/3088 / 100
Topics automatically classifies production logs by user intent, sentiment, and issues using built-in Task, Sentiment, and Issues facets, surfacing patterns as topic distributions and time-series trends; custom facets let teams define domain-specific classification dimensions using custom preprocessors and prompts beyond the built-in facets. Topics management adds on-demand pipeline runs, sampling adjustment, pause/resume, and history rewind after facet or filter changes, and hovering a row in the List view of a Topics facet card reveals a 'View logs' link that filters logs to that topic and all nested topics. Custom preprocessors whose output is not a recognized message array now render in thread layout as labeled text instead of failing.
Enable Topics on a project to automatically classify production logs by intent, sentiment, and issues.
📍In the Braintrust UI, go to your project › Observe › Topics › Enable Topics, confirm traces render with the Thread preprocessor, then select the facets (Task, Sentiment, Issues) you want active.
— Names every sub-capability plus an enable-in-UI walkthroughproduct docs
03
Firebase Genkit integration improvements in Go SDKIMPROVED78how completely this was documenteddepth30/40specificity28/30actionability20/3078 / 100
Go SDK v0.11.1 adds WithProvider and WithModel options on NewMiddleware for explicit model attribution with Firebase Genkit, plus traced tool wrappers DefineTool, DefineToolWithInputSchema, and DefineMultipartTool; auto-instrumentation now replaces genkit.DefineTool, genkit.DefineToolWithInputSchema, and genkit.DefineMultipartTool calls with their traced equivalents.
Full REST API client in SDK packageNEW75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
Adds DefaultBraintrustApiClient.Api, a generated REST API client covering every Braintrust REST endpoint, shipped inside the existing Braintrust.Sdk package with no separate install required.
— Names the exact client class and package, no usage sampleproduct docs
05
Go SDK span capture enhancements across providersIMPROVED75how completely this was documenteddepth32/40specificity28/30actionability15/3075 / 100
Go SDK v0.11.0 expands span instrumentation across providers: Anthropic spans capture prompt_cache_creation_5m_tokens and prompt_cache_creation_1h_tokens for TTL-specific prompt caching; Bedrock Runtime spans capture audio and video content blocks and InvokeModelWithResponseStream is now fully instrumented for Anthropic Claude models; Google ADK spans now include reasoning and cached token metrics.
— Names all fields and methods added across three providerssnapshot-20260826
06
Nested tool-call spans for OpenAI and Anthropic APIsIMPROVED73how completely this was documenteddepth30/40specificity28/30actionability15/3073 / 100
Web search, file search, code interpreter, and MCP calls in the OpenAI Responses API now appear as child tool spans nested under the LLM span for cleaner trace visualization; server_tool_use blocks in the Anthropic Messages API are similarly nested as child tool spans, with Anthropic spans now capturing new server_tool_use_* metrics.
— Names spans and metrics but no exact viewing stepsproduct docs
07
New open-source models via Braintrust GatewayNEW73how completely this was documenteddepth25/40specificity28/30actionability20/3073 / 100
Adds kimi-k3 and deepseek-v4-flash-0731 as built-in open-source models served through the Braintrust Gateway alongside GLM-5.2, with no external AI provider setup required; usage draws from monthly model credits shared with Topics.
LiveKit Agents audio attachments disabled by defaultBREAKING70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
Python SDK v0.32.0 disables LiveKit Agents audio attachments on agent_speaking spans by default; set BRAINTRUST_CAPTURE_AGENT_AUDIO_ATTACHMENTS=true to restore the previous behavior.
Google GenAI provider metadata field renamedBREAKING65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
The Google GenAI provider metadata field name changed from "gemini" to "google" (Go SDK v0.11.1); trace queries that filter on the previous value must be updated to use the new field name.
Loop agent and natural-language custom viewsNEW63how completely this was documenteddepth28/40specificity20/30actionability15/3063 / 100
The new Loop agent enables natural-language interaction to analyze logs, optimize prompts, build datasets, and generate custom React view components; custom views let teams describe a trace/dataset interface in natural language and have Loop generate an embeddable, customizable React component.
Reasoning model evaluation supportNEW62how completely this was documenteddepth25/40specificity22/30actionability15/3062 / 100
Braintrust now supports evaluating reasoning models (OpenAI o4, Claude, Gemini) with configurable thinking budgets, capture of intermediate reasoning traces, and scoring of final outputs.
— Names models and capabilities, no config keys givenproduct docs
thinner coverage below
12
Scorer functions receive case metadata across SDKsIMPROVED57how completely this was documenteddepth20/40specificity22/30actionability15/3057 / 100
Python SDK v0.34.0 forwards eval case fields to scorer functions, and TypeScript SDK v3.28.0 gives scorer functions in Eval() access to the id and tags of each case.
Monitoring dashboards and alertsNEW53how completely this was documenteddepth20/40specificity18/30actionability15/3053 / 100
Monitoring dashboards track request counts, latency, costs, and scores across logs and experiments over time; alerts add webhook and Slack notification configuration.
— Names metrics and notification channels, no config keysproduct docs
14
Remote evals and agent sandboxesNEW52how completely this was documenteddepth22/40specificity15/30actionability15/3052 / 100
Remote evals and sandboxes let teams connect custom agent code to a playground and run it in an isolated sandbox, enabling interactive testing of complex agents without modifying deployed code.
— Describes behavior, no setup steps givenproduct docs
15
Dataset pipelines from project logsNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Dataset pipelines transform spans or traces from project logs into dataset rows in bulk using declarative, version-controlled pipeline definitions.
— States mechanism but no config surface namedproduct docs
16
Dataset performance trackingNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Dataset performance tracking shows which experiments used a dataset and how each row performs over time, with chart and SQL filters.
— Names filter types, no exact navigation givenproduct docs
17
Multi-reviewer human review scoringIMPROVED49how completely this was documenteddepth22/40specificity15/30actionability12/3049 / 100
Human review now supports multiple reviewers with configurable score-combination rules and a base value for non-numeric scores.
— Describes mechanism but no UI or config path givenproduct docs
18
Multimodal log attachmentsNEW45how completely this was documenteddepth18/40specificity15/30actionability12/3045 / 100
Log attachments support images, audio, PDFs, and other binary files attached to traces and experiments for multimodal review in context.
— Names supported file types, no size limits or API givenproduct docs
19
Async eval invocation in Python SDKNEW40how completely this was documenteddepth10/40specificity15/30actionability15/3040 / 100
Python SDK v0.32.0 adds invoke_async() as an async counterpart to invoke().
Advanced tracing patternsIMPROVED38how completely this was documenteddepth15/40specificity15/30actionability8/3038 / 100
Advanced tracing patterns now cover distributed tracing across services, sensitive data masking, custom span rendering, and high-throughput performance tuning.
— Generic list with no mechanism or config namedproduct docs
21
Export of annotated traces and datasetsNEW35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Adds export of annotated traces and datasets for use in external evaluation frameworks, analysis pipelines, or training workflows.
— No format or endpoint named, thin descriptionproduct docs
└──▷ BREAKING ON UPGRADE
!The Google GenAI provider metadata field name changed; trace queries that filter on the previous value must be updated to use the new field name.
!Python SDK v0.32.0: LiveKit Agents audio attachments on agent_speaking spans are now disabled by default; set BRAINTRUST_CAPTURE_AGENT_AUDIO_ATTACHMENTS=true to restore the previous behavior.
!Go SDK v0.11.1 (Google GenAI): Provider metadata changed from "gemini" to "google"; update trace queries that filter on the previous provider value.
!Go SDK v0.11.1 (Eino): ChatModel span output is now an OpenAI-compatible choices array ([{"index": 0, "finish_reason": "...", "message": {...}}]) instead of a flat message map; embedding input is now {"inputs": [{"content": "..."}]} and output is {"count": N}, removing embedding_length and renaming embeddings_count; provider metadata is now lowercase (e.g. "openai" instead of "OpenAI"). Update trace queries that rely on the previous formats.