The daily firehose — everything the toolchain shipped today, already filtered.
// HOW THIS ISSUE IS MADE
We read every release from the 187 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.
VIEW
ISSUE VIEWfull issue
Do you prefer full issue?
▾
↕
filter by tool name…
$ tct list# 27 tools matched
Same issue, same prompt, two writers:
A read across the whole issue before you read any of it: what stands out in today's releases, grouped by what it lets you do. Every tool named links to its entry below.
Three unrelated things stand out. xalgorix now chains source-code sink discovery into live proof-of-exploit, so a static finding arrives already validated. Cline's PreToolUse hook actually blocks agent reads and edits of .clineignore-matched files rather than politely asking. And Claude Code adds an org-wide managed MCPMCPModel Context Protocol, an open standard from Anthropic that lets an AI model call external tools and data sources through a uniform interface, so cyber tools can expose capabilities directly to LLM-based agents. server setting, moving agent tool access out of per-developer config.
detect
Prove a source-code finding is actually reachable at runtime
New agent tools scan_source_sinks, scan_source_routes and probe_hypothesis walk from a sink found in code to a live request that demonstrates it. That closes the gap that makes SASTSASTStatic application security testing: automated analysis of source code or binaries without executing them, used to surface vulnerabilities early in development before deployment. output expensive: the triage pass where a human decides whether a flagged path is reachable in a deployed app, done by hand per finding.
Stop a coding agent from touching files you told it to leave alone
Cline's PreToolUse hook blocks reads and edits of .clineignore-matched paths at the tool boundary instead of relying on the model to respect the ignore list, so secrets and vendored code stay out of context. Kiro replaces trusted commands with capability-based permissions, moving from a list of blessed strings to what an agent is allowed to do.
Set agent tool access and platform accounts centrally instead of per developer
Claude Code adds an organization-wide managed MCPMCPModel Context Protocol, an open standard from Anthropic that lets an AI model call external tools and data sources through a uniform interface, so cyber tools can expose capabilities directly to LLM-based agents. server setting, so which external tools an agent can reach is an admin decision rather than whatever each engineer pasted into local config. OpenAI's TerraformTerraformAn open-source infrastructure-as-code tool by HashiCorp that provisions cloud and on-premises resources through declarative configuration files, letting cyber tools automate repeatable environment deployments without manual setup. provider puts projects, users and service accounts under code review and state, which is where API key sprawl and orphaned service accounts usually start.
Three unrelated things stand out today: xalgorix can now turn source-code sink findings into live exploit probes; Claude Code lets orgs centrally manage MCPMCPModel Context Protocol, an open standard from Anthropic that lets an AI model call external tools and data sources through a uniform interface, so cyber tools can expose capabilities directly to LLM-based agents. servers; OpenAI makes API projects, users, and service accounts manageable as TerraformTerraformAn open-source infrastructure-as-code tool by HashiCorp that provisions cloud and on-premises resources through declarative configuration files, letting cyber tools automate repeatable environment deployments without manual setup. instead of console drift.
detect
Prove a source-code finding against the running target
New agent tools connect sink and route discovery to runtime hypothesis probing. That lets a team move from “this path looks exploitable” to a live validation loop without hand-building each request chain.
Control agent tool servers at the organization level
An organization-wide managed MCP server setting gives admins a central place to govern which external tool surfaces Claude Code can use. That reduces per-developer configuration drift and makes agent access policy less dependent on local workstation state.
The official Terraform provider brings API platform resources such as projects, users, and service accounts into code review and state management. Teams can replace console-only changes with repeatable provisioning and auditable diffs.
Block agent reads and edits of ignored files before the tool runs
The PreToolUse hook now stops access to .clineignore-matched files before a read or edit happens. That closes a common gap where an agent’s planning looks safe, but the actual file operation still reaches secrets, private notes, or excluded project material.
The xalgorix platform runs AI pentesting agents for reconnaissance, vulnerability detection, and exploitation workflows.
xalgorix shipped a full whitebox-to-runtime bridge this window — three new agent tools (scan_source_sinks, scan_source_routes, probe_hypothesis) that turn source-code sink discovery into live, provable exploitation — alongside matching expansions to the xalgorix-bench benchmark harness (a whitebox challenge, a wall-clock timeout flag, and four new vulnerability classes).
└──▷ 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. Under60 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
scan_source_sinks tool for whitebox sink discoveryNEW90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
Adds scan_source_sinks command that sweeps an attached source tree for dangerous sinks — RCE/command injection, SQLi, SSRF, file I/O→LFI, template→SSTI, deserialization, open redirect — using the same curated patterns as code_search. Each hit is seeded into the shared ledger as a source-sink: data-flow hypothesis tagged with file:line, the first automated populator of Hypothesis.DataFlow; sink classes map to canonical vuln classes (cmdi→rce, fileio→lfi, template→ssti), with each sweep bounded to a maximum of 40 seeds and idempotent dedup by class + file:line. Seeded hypotheses feed into claim_next_hypothesis so specialists can trace a sink back to a reachable route on the live target; it degrades to a black-box fallback message when no source tree is configured, and discovery-only classes (secrets, auth, crypto) are deliberately excluded from seeding.
— Names the exact command, mapping rules and capsv4.6.23
02
scan_source_routes route-to-sink correlation and auto-seedingNEW90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
Adds scan_source_routes tool that extracts HTTP route declarations from source across Flask/FastAPI, Django, Express, Spring, Go routers, and Rails, seeding each as a hypothesis with a real, reachable path — including internal/admin routes a black-box crawler never reaches. Routes are correlated with dangerous sinks by handler-file co-location — a route whose file contains a sink is seeded class-typed (by worst sink class present) at higher confidence with a data-flow note (e.g. 'POST /admin/exec reaches an RCE sink') — while uncorrelated routes are seeded as idor authz/attack-surface leads; seeding is bounded to 40 hypotheses per sweep with idempotent dedup by vuln class and path, and degrades to a black-box fallback when no source is configured. This route↔sink correlation now also runs automatically at scan start (matching the behaviour already provided by uploaded OpenAPI/HAR context) — deterministic, bounded by per-sweep caps, idempotent via ledger dedup, and a no-op when no source is configured.
— Names frameworks, caps and auto-seed behaviour in detailv4.6.24v4.6.26
03
probe_hypothesis live request verification toolNEW88how completely this was documenteddepth35/40specificity28/30actionability25/3088 / 100
Adds probe_hypothesis tool that resolves a source-route hypothesis (or ingested/authenticated endpoint) against the scan target, issues a baseline HTTP request, and records the response as evidence — promoting confirmed routes to testing, flagging 401/403 responses as authz_matrix candidates, and marking 404/connection failures as blocked. It automatically uses the scan session's auth, honors the configured request-rate policy and cancellation, and refuses to probe the operator's own machine/listener via a self-scope check; it skips file:line source-location endpoints, does not follow redirects (treating a 3xx redirect to /login as a meaningful signal), and is disabled entirely in passive mode.
— Full mechanism with status-code handling and guardrails namedv4.6.25
04
Per-challenge timeout in xalgorix-benchNEW80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Adds -timeout flag to xalgorix-bench (and the bench.RunWithTimeout API) to bound each challenge scan with a configurable wall-clock limit, defaulting to 8 minutes; timeouts are marked on the scorecard while partial findings gathered before the deadline are still scored.
— Exact flag name, API and default value givenv4.6.21
05
Whitebox benchmark challenge for source-to-runtime bridgeNEW78how completely this was documenteddepth30/40specificity28/30actionability20/3078 / 100
Adds SourceFiles source tree support to Challenge, letting the benchmark harness materialize a real source repo to a temp directory and wire it to a scan via SetSourceRepo for end-to-end whitebox testing. Ships the whitebox-cmdi challenge — an app with a command-injectable route unreachable by black-box crawling — requiring the full bridge (scan_source_sinks, scan_source_routes, probe_hypothesis, and auto-seeding) to discover the hidden route, identify the os.popen sink, probe it live, and achieve RCE class exploitation.
— Names the API and challenge but is a test harness, not user-facingv4.6.27
06
Four new vulnerability classes in xalgorix-benchNEW68how completely this was documenteddepth25/40specificity28/30actionability15/3068 / 100
Adds four new challenge classes to xalgorix-bench: SSRF (cloud-metadata-like secret returned from an internal fetch), SSTI ({{7*7}} evaluates to 49), LFI/path traversal (../../etc/passwd returns passwd-like content), and command injection (a shell metacharacter yields uid=0(root)).
— Concrete test payloads named but is benchmark content onlyv4.6.20
LangSmith is a platform for debugging, testing, and monitoring LLM applications built with LangChain.
LangSmith's July 6-10 2026 update adds an API to test thread evaluators before saving, promotes POST /v2/datasets/{dataset_id}/experiment-runs as the public experiment-comparison endpoint while retiring legacy dataset comparison helpers, switches cloud bulk export compression to zstdzstdA fast lossless compression algorithm and library maintained by Meta, offering compression ratios comparable to zlib at much higher speeds, which lets cyber tools shrink data with minimal CPU overhead., and adds OpenTelemetryOpenTelemetryA CNCF-maintained open standard and SDK collection for capturing traces, metrics, and logs from applications in a vendor-neutral format, letting cyber tools ingest observability data without locking into a proprietary pipeline. resource-attribute tracing alongside project-scoped monthly trace limits and a batch of smaller UI and ingestion fixes.
└──▷ 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. Under60 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
Thread evaluator validation APINEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds test_thread_id and session_id parameters to POST /runs/rules/validate so a multi-turn thread evaluator can be tested against a real conversation before it is saved, catching misconfiguration early.
Test a multi-turn thread evaluator against a real conversation before saving to catch misconfiguration early.
— Named endpoint and params with a runnable curl examplesnapshot-20260903
02
Bulk export compression defaults and controlIMPROVED90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds FF_BULK_EXPORT_DEFAULT_COMPRESSION environment variable to control bulk export compression on self-hosted deployments; self-hosted retains a gzip default while cloud deployments now default to zstd for improved performance.
Keep gzip compression for bulk exports on a self-hosted deployment instead of adopting the new zstd default.
$ export FF_BULK_EXPORT_DEFAULT_COMPRESSION=gzip
— Named env var with both defaults and an example commandsnapshot-20260903
03
OTel resource attributes as trace metadataNEW85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
OpenTelemetry resource attributes set via OTEL_RESOURCE_ATTRIBUTES now appear on traces as metadata namespaced under otel.resource.*, letting teams attach details like user IDs without changing span emission.
Attach user IDs and environment metadata to traces without changing span emission by setting OTel resource attributes.
— Named env var and metadata namespace with examplesnapshot-20260903
04
Dataset split visibility and editing in experiment comparisonIMPROVED60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Adds a reorderable 'Splits (latest)' column to the experiment comparison view showing each example's current dataset split assignments as chips reflecting live membership; each split chip is now interactive with an 'Edit splits' action that opens the single-example split picker.
Project-scoped monthly trace limitsNEW55how completely this was documenteddepth30/40specificity15/30actionability10/3055 / 100
Enforces user-defined monthly trace limits scoped to individual projects and users; new traces exceeding a configured limit are rejected while patches and feedback for already-accepted traces continue to be processed.
Oversized field handling in multipart ingestionIMPROVED45how completely this was documenteddepth25/40specificity15/30actionability5/3045 / 100
LangSmith now preserves traces in multipart ingestion batches when one run has oversized inputs or outputs — oversized fields are replaced with a placeholder rather than rejecting the entire batch.
OTel child span ordering fixIMPROVED40how completely this was documenteddepth25/40specificity10/30actionability5/3040 / 100
Native OpenTelemetry child spans are no longer dropped when they arrive before an SDK-attributed parent span; they are buffered and correctly nested regardless of arrival order.
Thread evaluator config preview refinementsIMPROVED40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
The thread evaluator config preview now shows only the thread message formats the evaluator actually maps, and displays a locked 'Trace count >= 2' filter for managed thread evaluators.
!Legacy dataset comparison helpers are removed from the public OpenAPI spec and generated SDKs; POST /v2/datasets/{dataset_id}/experiment-runs is now the supported public API (existing HTTP routes continue to work for LangSmith UI clients).
agentacct rebuilt its terminal dashboard into a four-tab, keyboard-native TUI with deep receipt drill-down and introduced a more honest 'Inactive' task state derived from stored timestamps rather than the wall clock.
The agentacct dashboard records coding-agent work steps, tools, file changes, tests, time, and token costs locally.
agentacct rebuilt its terminal dashboard into a four-tab, keyboard-native TUI with deep receipt drill-down and introduced a more honest 'Inactive' task state derived from stored timestamps rather than the wall clock.
└──▷ 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. Under60 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
Receipt drill-down in TUINEW90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
Opening a receipt inside agentacct tui shows its sessions and steps, the checks timeline behind the verdict, and files touched, plus a 'Needs attention' section for currently-failing checks, a / filter, status tabs on Work, an Evidence Sources pane, and a ? help overlay.
— Names every UI element and keybinding involvedv0.10.6
02
Honest 'Inactive' task stateNEW70how completely this was documenteddepth35/40specificity25/30actionability10/3070 / 100
A task with open steps, nothing recorded as finished, and a newer session active elsewhere for 48h past that session's start is downgraded to an 'Inactive' state, computed from stored timestamps rather than the wall clock, with provenance marked inferred and kept out of the review queue.
— Detailed mechanism but no direct user action to invoke itv0.10.6
03
Four-tab keyboard-native TUI with theme toggleNEW65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
Rebuilds agentacct tui into a four-tab (Dashboard / Work / Usage / Sources) keyboard-native terminal dashboard with light and dark themes mirroring the macOS app, and adds a T keybinding inside agentacct tui to toggle between light and dark themes.
Launch the rebuilt keyboard-native terminal dashboard to review agent receipts, drill into sessions and steps, and monitor usage across all agents.
$ agentacct tui
— Names tabs and keybinding but not underlying rendering changesv0.10.6
Arize Phoenix added new model provider support (Z.ai GLM and Gemini 3.8 Flash) across the CLI and playground, shipped a REST endpoint for programmatic trace deletion, and reorganized the assistant settings UI.
AI Observability & Evaluation
Arize Phoenix added new model provider support (Z.ai GLM and Gemini 3.8 Flash) across the CLI and playground, shipped a REST endpoint for programmatic trace deletion, and reorganized the assistant settings UI.
└──▷ 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. Under60 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
Delete traces API endpointNEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds DELETE /projects/{project_identifier}/traces API endpoint to programmatically delete traces for a given project, e.g. curl -X DELETE 'http://localhost:6006/projects/my-project/traces' to reset trace state between CI test runs.
Delete all traces for a project via the new REST endpoint — useful in CI pipelines to reset trace state between test runs.
New model providers in CLI and playgroundNEW52how completely this was documenteddepth20/40specificity22/30actionability10/3052 / 100
Adds ZAI as a built-in OpenAI-compatible model provider, enabling Z.ai GLM models to be used directly within Phoenix without custom provider configuration, available both in the CLI and in the assistant/playground. Also adds support for Gemini 3.8 Flash in the playground for model comparison and prompt optimization.
Unified AI Gateway for 30+ LLMs (OpenAI, Anthropic, Bedrock, Azure etc) with Caching, Guardrails, A/B test & cost controls. Go-native Fastest & Scalable AI Gateway LiteLLM & Kong AI Gateway alternative.
ai-gateway v1.5.2 adds full request-attribution headers and trace spans, richer conditional routing (target chains, new predicates, request metadata), sticky sessions, per-target timeouts, pluggable model catalogs, cross-request 429 parking, and reworked latency- and cost-based load-balancing scoring, alongside two breaking changes to failover behaviour and config validation.
└──▷ 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. Under60 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
Per-target request timeoutNEW93how completely this was documenteddepth35/40specificity28/30actionability30/3093 / 100
targets[].timeout bounds a single physical attempt against a target, independent of the overall request_timeout; a timed-out attempt triggers failover, and an all-timeouts outcome returns 504 gateway_timeout.
Limit a single upstream attempt to 10 s so a hung primary triggers failover quickly rather than consuming the whole request budget.
— Behavior and outcome fully specified with runnable examplev1.5.2
02
Conditional routing: target chains, new predicates, metadata headerNEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
target_keys: [a, b] on conditions[] and content_conditions[] specifies an ordered failover chain per rule (target_key remains valid as the single-entry form). Four new conditional routing predicates were added: key: user, key: stream, key: has_tools (values "true"/"false"), and key: metadata with field: <entry>. The new X-Gateway-Metadata request header on /v1/chat/completions and /v1/completions carries a JSON object of up to 32 scalar values within 4 KiB, is never forwarded to providers, and is readable via the key: metadata predicate.
Route a request carrying custom metadata to a dedicated target without exposing that metadata to the upstream provider.
— Every field, key, and endpoint named with a runnable curl examplev1.5.2
03
Sticky routing per userNEW85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
strategy.sticky: { on: user, ttl: "1h" } under loadbalance and ab-test strategies pins each user field to the same target or A/B variant for a configurable TTL, using a stateless hash with no shared state.
Pin users to the same backend for the duration of a multi-turn session so prompt caches and A/B variants stay consistent.
yaml
strategy:
mode: loadbalance
sticky:
on: user
ttl: "1h"
— Exact config keys with a runnable YAML examplev1.5.2
04
Cost-optimized scoring reworkIMPROVED85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
cost-optimized scoring now covers input plus output cost for chat (using max_tokens / max_completion_tokens, defaulting to 256), per-token for embeddings, per-image, and per-minute or per-character for audio, replacing the previous chat-input-only formula; equal-cost targets break ties by targets[].weight.
Routing attribution headers and trace spanNEW83how completely this was documenteddepth30/40specificity28/30actionability25/3083 / 100
Every routed surface (chat, streaming chat, legacy completions, embeddings, images, rerank, moderations, transcriptions, translations, speech) now returns X-Gateway-Provider, X-Gateway-Target, X-Gateway-Model, and X-Gateway-Attempts response headers, accessible to Go embedders via aigateway.WithRoutingAttribution. The ferro.routing.attempt span attribute, declared since v1.1.0 but never emitted, now actually fires on every routed request span with a count matching X-Gateway-Attempts.
— Names exact headers, API and span; no example givenv1.5.2
06
Custom failover status codesNEW83how completely this was documenteddepth25/40specificity28/30actionability30/3083 / 100
strategy.failover_on_status_codes: [409] (or any operator-chosen status) extends the built-in failover-safe classes with provider-specific upstream codes; 400, 401, 403, 404, and 422 are refused.
— Exact config key and refused codes, directly usablev1.5.2
07
Pluggable model catalog for Go embeddersNEW80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
aigateway.WithCatalog(models.Catalog) option on aigateway.New supplies a custom model catalog for cost-optimized routing and request pricing, replacing the embedded or remote catalog; usage is reported as source="supplied" in the gateway_catalog_loads_total metric.
— Exact API and metric named, no code example givenv1.5.2
08
Context-window-exceeded failoverIMPROVED75how completely this was documenteddepth30/40specificity30/30actionability15/3075 / 100
Pool modes now fail over on context-window-exceeded errors from OpenAI-compatible (code: context_length_exceeded), Anthropic (prompt is too long), and Gemini (INVALID_ARGUMENT token-count) providers, unified under a single classifier, core.IsContextLengthError.
— Named error codes and classifier but automatic, no config surfacev1.5.2
09
Cross-request 429 parkingNEW70how completely this was documenteddepth35/40specificity20/30actionability15/3070 / 100
A target that returns 429 is now parked for its Retry-After duration (bounded to 1 minute; 5 seconds when absent), so subsequent requests skip it without paying another 429; park state is process-local.
— Mechanism and bounds given but behavior is automatic, no configv1.5.2
10
Least-latency sampling reworkIMPROVED70how completely this was documenteddepth35/40specificity25/30actionability10/3070 / 100
least-latency samples are now keyed by target AND upstream model, expire after 5 minutes, and one request in ten probes a non-leader target; streaming samples measure time-to-first-chunk rather than full drain.
— Mechanism fully described but no config surface to act onv1.5.2
11
Breaking: single-target circuit-open behaviorBREAKING70how completely this was documenteddepth30/40specificity20/30actionability20/3070 / 100
A conditional or content-based rule that names a single target now returns 503 when that target's circuit is open, rather than borrowing a healthy sibling as v1.5.1 did; add target_keys to name a stand-in explicitly.
— Before/after and mitigation named, exact status code givenv1.5.2
12
Breaking: ab_variants label requiredBREAKING60how completely this was documenteddepth20/40specificity20/30actionability20/3060 / 100
Configuration loading now refuses an ab_variants[] entry without a label; a v1.5.1 config with an unlabelled variant will not load until a label is added.
Dashboard strategy panel detailIMPROVED45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
The embedded dashboard strategy panel now displays each target's model_map, a rule's target_keys chain in order, and metadata predicates by field.
— Names UI fields but no navigation path givenv1.5.2
└──▷ BREAKING ON UPGRADE
!A conditional or content-based rule that names a single target now returns 503 when that target's circuit is open, rather than borrowing a healthy sibling as v1.5.1 did; add target_keys to name a stand-in explicitly.
!Configuration loading now refuses an ab_variants[] entry without a label; a v1.5.1 config with an unlabelled variant will not load until a label is added.
Ship quality agents at scale. Braintrust is the AI observability platform for tracing production, running evals, and catching regressions before they reach users.
Braintrust's biggest window changes are workflow-privacy and reliability controls: a blind human reviews setting for independent scoring, pause/resume for alerts and scoring rules instead of deletion, automatic Agno eval instrumentation in the Python SDK, and score/metric filtering for CI PR comments, alongside smaller provider-picker and table-validation updates.
└──▷ WHAT SHIPPED · 7 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. Under60 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
Agno eval instrumentation in Python SDKNEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Python SDK v0.36.0 adds eval instrumentation for Agno via auto_instrument(): AccuracyEval, AgentAsJudgeEval, ReliabilityEval, and PerformanceEval, plus eval suites, are now traced automatically, with suite runs opening a Braintrust experiment automatically.
Automatically trace all Agno evals and open a Braintrust experiment for the suite run, without manual instrumentation.
python
from braintrust import auto_instrument
from braintrust.agno import AccuracyEval, ReliabilityEval
auto_instrument()
# Eval suite runs are now traced and open a Braintrust experiment automatically
— Names SDK version, function and classes with runnable code.snapshot-20260903
02
Score and metric filtering in eval-actionNEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
The braintrustdata/eval-action GitHub Action (v2.1.0) adds report_scores and report_metrics inputs to filter PR comments down to only the scores and metrics specified, e.g. report_scores: 'accuracy, relevance' and report_metrics: 'latency, cost'.
Filter a noisy PR comment down to only the scores and metrics your team cares about, using the new report_scores and report_metrics inputs in your GitHub Actions workflow.
— Names exact action version and config inputs with runnable YAML.snapshot-20260903
03
Pause and resume automationsNEW85how completely this was documenteddepth35/40specificity25/30actionability25/3085 / 100
Log alerts, environment alerts, time window alerts, scheduled Loop jobs, and online scoring rules can now be paused and resumed instead of deleted, preserving their configuration across incidents or noisy deploys; each automation shows an 'Active' or 'Paused' status and last-run time.
Pause a noisy alert during a deploy without losing its configuration, then resume it afterward.
📍Navigate to the automation (log alert, environment alert, time window alert, scheduled Loop job, or online scoring rule), click the 'Active' status indicator, and select 'Pause'. The automation shows 'Paused' with the last-run time. Click 'Resume' when the deploy is complete.
— Names five automation types and exact pause/resume UI steps.product docs
04
Blind human reviews project settingNEW72how completely this was documenteddepth30/40specificity22/30actionability20/3072 / 100
The Blind human reviews project setting hides peer scores, comments, and aggregates from reviewers for the entire review session, preserving independence even after a reviewer submits their own scores; users with the project Update permission are exempt and always see all reviews. Enable it via Settings > Human Review in the project, then save.
Preserve reviewer independence for a full review session by enabling blind reviews in project settings.
📍In the project, go to Settings › 'Blind human reviews' and enable the toggle. Reviewers will never see peer scores, comments, or aggregates — even after submitting their own scores.
Enable blind reviews for a project so that peer scores and comments stay hidden for the entire review session, preserving reviewer independence.
📍1. Open your project in Braintrust.
2. Go to Settings › Human Review.
3. Toggle on 'Blind human reviews'.
4. Save. Reviewers will no longer see peer scores or aggregates at any point during their review.
— Names setting, permission exemption and exact UI steps.snapshot-20260903
thinner coverage below
05
Inline provider key editing in provider pickerIMPROVED50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Configured AI provider tiles in the provider picker now show an edit icon, allowing inline update of a provider's API key or settings without navigating away from the picker.
— Names UI surface but gives no exact navigation path.snapshot-20260903
06
Default score hiding for unscored review rowsIMPROVED40how completely this was documenteddepth20/40specificity12/30actionability8/3040 / 100
By default, human review now hides peer scores, comments, and aggregates until a reviewer fills in their own scores, with unscored rows opening as a blank form.
— Describes default behavior but gives no action to take.snapshot-20260903
07
Validation for conflicting custom column namesBREAKING33how completely this was documenteddepth15/40specificity10/30actionability8/3033 / 100
Custom column names that conflict with built-in table fields are now rejected at creation time.
— States the rule but no mechanism or affected surfaces detailed.snapshot-20260903
Groq is a high-speed inference engine that runs large language models significantly faster than traditional GPUs.
Groq: Adds openai/gpt-oss-120b model: 120B MoEMoEMixture of Experts: a neural network architecture where input is routed to a subset of specialized sub-networks, reducing compute per token while scaling total model capacity — useful for building large, efficient AI inference pipelines. with 128 experts, 131K token context, 32K max output tokens, ~500+ TPS, built-in browser search and code execution, and structured output support.
└──▷ TRY IT
Run a reasoning query against the 20B model at high throughput — useful for latency-sensitive agentic pipelines.
HyperFrames' Capture CLI now surfaces the reason a referenced asset can't be found rather than failing without explanation.
Write HTML. Render video.
HyperFrames' Capture CLI now surfaces the reason a referenced asset can't be found rather than failing without explanation.
└──▷ 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. Under60 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
Asset-missing diagnostics in Capture CLIIMPROVED35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Capture now reports the reason why a referenced asset is not found in the output folder instead of failing silently.
— Describes behavior change but no exact command or error format.v0.8.27
Tensors and Dynamic neural networks in Python with strong GPU acceleration
PyTorch 2.14 adds multi-way branching and declarative dynamic shapes to the compiler stack, a new nccl2 distributed backend with first-class fault tolerance, experimental torch.compile support for complex tensors, and native linear algebra on Apple Silicon, alongside a large set of breaking API removals (torch.cholesky, torch.qr, tvm relaytvm relayAn intermediate representation and compiler framework maintained by Apache TVM for machine learning models, letting cyber tools optimize and deploy neural networks across hardware backends without rewriting model code per target., profiler use_cuda) that require code changes.
└──▷ 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. Under60 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
tvm backend moves to relax frontendBREAKING90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
Updates the tvm backend to use TVM's relax frontend exclusively, replacing relay; the pipeline is now passed as options={'pipeline': ...} to torch.compile(..., backend='tvm'). The relay path is removed along with its scheduler/trials options and the tvm_meta_schedule/tvm_auto_scheduler entry points, and the backend now requires TVM >= 0.20.
— Gives exact new call syntax and removed options/entry points.v2.14.0
02
Legacy cholesky() and qr() removedBREAKING80how completely this was documenteddepth25/40specificity30/30actionability25/3080 / 100
torch.cholesky() and Tensor.cholesky() are removed and now raise RuntimeError; use torch.linalg.cholesky() (and .mH for upper-triangular results) instead. torch.qr() and Tensor.qr() are also removed and now raise RuntimeError; use torch.linalg.qr(mode='reduced') or torch.linalg.qr(mode='complete') instead.
— Names all four functions and their exact replacements.v2.14.0
03
use_cuda argument removed from profilerBREAKING80how completely this was documenteddepth25/40specificity30/30actionability25/3080 / 100
The use_cuda argument is removed from torch.profiler.profile and torch.autograd.profiler.profile; passing it now raises TypeError. Use activities=[..., ProfilerActivity.CUDA] for torch.profiler.profile or use_device='cuda' for torch.autograd.profiler.profile.
— Names both classes and the exact replacement arguments.v2.14.0
04
Native linear algebra on Apple Silicon (MPS)NEW75how completely this was documenteddepth30/40specificity30/30actionability15/3075 / 100
Adds native linear algebra to Apple Silicon (MPS): Jacobi-kernel SVD, eigh, QR, and Cholesky, plus a five-part reduction rewrite and further MPSGraph-to-Metal kernel migration.
— Names four specific ops and the underlying rewrite/migration work.v2.14.0
05
nccl2 distributed backendNEW70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Adds a new nccl2 backend for PyTorch Distributed, implementing the full collective contract with nonblocking communicators and eager communicator splitting.
— Names the backend and its two key mechanisms.v2.14.0
06
CUTLASS kernels in Inductor via NVGEMMNEW70how completely this was documenteddepth30/40specificity30/30actionability10/3070 / 100
Brings CuTeDSL-generated CUTLASS kernels to Inductor via NVGEMM, with epilogue fusion, scaled and NVFP4 GEMM, and grouped-reduction epilogues autotuned alongside Triton and ATen.
— Rich mechanism detail but no direct flag or invocation shown.v2.14.0
07
NCCL symmetric-memory pool re-registration requirementBREAKING70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
NCCL symmetric-memory pools no longer automatically upgrade late-allocated segments to symmetric windows after register_mem_pool(..., symm=True); pools must be collectively deregistered and re-registered after new allocations.
— Names the API and the exact remediation steps.v2.14.0
08
Declarative dynamic shapes via @dynamic_specNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Introduces declarative dynamic shapes via @dynamic_spec, shared across torch.compile, torch.export, and make_fx.
— Names the decorator and the three consumers sharing it.v2.14.0
09
Fault tolerance as first-class c10d conceptNEW65how completely this was documenteddepth30/40specificity25/30actionability10/3065 / 100
Promotes fault tolerance to a first-class c10d concept: in-place process-group reconfiguration, one-sided RMA windows, and a Flight Recorder that now works for any backend, not only NCCL.
— Describes three mechanisms but no API entry points given.v2.14.0
10
LinearCrossEntropyOptions acc_policy changeBREAKING65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
torch.nn.LinearCrossEntropyOptions no longer accepts acc_policy='balanced'; use acc_policy='compact' instead, or a ValueError is raised.
— Names exact option values and the resulting error.v2.14.0
11
Gradient tie-break change for clamp and fmin/fmaxBREAKING65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Scalar clamp/clamp_min/clamp_max gradient at equality changes from 1 to 0; Tensor-bound clamp, clamp_min, clamp_max, fmin, and fmax now split the gradient evenly at ties instead of assigning it entirely to the input.
— Names all five affected ops and the before/after gradient values.v2.14.0
12
split_group() non-member return value changeBREAKING65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
torch.distributed.split_group() now returns GroupMember.NON_GROUP_MEMBER instead of None for nonmember ranks; is None checks must be replaced with == torch.distributed.GroupMember.NON_GROUP_MEMBER.
— Gives exact before/after values and required code fix.v2.14.0
13
C++ isIntegral overloads removedBREAKING65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
C++ zero-argument overloads c10::Scalar::isIntegral() and c10::isIntegralType(ScalarType) are removed; pass includeBool explicitly, e.g. isIntegral(false).
— Names the exact removed overloads and replacement call.v2.14.0
14
torch.switch for multi-way branchingNEW60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Adds torch.switch to generalize torch.cond for multi-way branching in compiled and exported graphs.
— Names the API and its relation to torch.cond but no usage example.v2.14.0
15
Custom process-group backend keyword requirementBREAKING60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Custom Python process groups whose new_group() method does not accept a backend keyword argument will now raise TypeError when torch.distributed.new_group() delegates subgroup creation to them.
— Names the method and the resulting exception.v2.14.0
thinner coverage below
16
torch.compile support for complex-valued tensorsNEW55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Adds experimental torch.compile support for complex-valued tensors, decomposing supported complex operations into real and imaginary computations for compiler-backend optimization.
— Explains the decomposition mechanism but marked experimental with no usage path.v2.14.0
17
torch.while_loop capture in CUDA graphsNEW40how completely this was documenteddepth10/40specificity20/30actionability10/3040 / 100
Enables torch.while_loop capture inside CUDA graphs.
— Bare one-line addition with no mechanism detail.v2.14.0
18
Inductor GPU targets extended to RubinNEW40how completely this was documenteddepth10/40specificity20/30actionability10/3040 / 100
Extends Inductor GPU targets to include Rubin (sm_107).
setup.py deprecated as build entry pointDEPRECATED30how completely this was documenteddepth10/40specificity10/30actionability10/3030 / 100
setup.py is now a deprecation shim; builds must go through the replacement build system.
— No replacement build system named, thin detail.v2.14.0
└──▷ BREAKING ON UPGRADE
!torch.nn.LinearCrossEntropyOptions no longer accepts acc_policy='balanced'; replace with acc_policy='compact' or raises ValueError.
!Scalar clamp/clamp_min/clamp_max gradient at equality changes from 1 to 0; Tensor-bound clamp, clamp_min, clamp_max, fmin, and fmax now split the gradient evenly at ties instead of assigning it entirely to the input.
!Custom Python process groups whose new_group() method does not accept a backend keyword argument will raise TypeError when torch.distributed.new_group() delegates subgroup creation to them.
!NCCL symmetric-memory pools no longer automatically upgrade late-allocated segments to symmetric windows after register_mem_pool(..., symm=True); pools must be collectively deregistered and re-registered after new allocations.
!torch.distributed.split_group() now returns GroupMember.NON_GROUP_MEMBER instead of None for nonmember ranks; is None checks must be replaced with == torch.distributed.GroupMember.NON_GROUP_MEMBER.
!torch.cholesky() and Tensor.cholesky() are removed and now raise RuntimeError; use torch.linalg.cholesky() (and .mH for upper-triangular results) instead.
!torch.qr() and Tensor.qr() are removed and now raise RuntimeError; use torch.linalg.qr(mode='reduced') or torch.linalg.qr(mode='complete') instead.
!The use_cuda argument is removed from torch.profiler.profile and torch.autograd.profiler.profile; passing it now raises TypeError. Use activities=[..., ProfilerActivity.CUDA] for torch.profiler.profile or use_device='cuda' for torch.autograd.profiler.profile.
!The tvm backend's relay path is removed along with scheduler/trials options and the tvm_meta_schedule/tvm_auto_scheduler entry points; pass a TVM pipeline via options={'pipeline': ...} and requires TVM >= 0.20.
!C++ zero-argument overloads c10::Scalar::isIntegral() and c10::isIntegralType(ScalarType) are removed; pass includeBool explicitly (e.g., isIntegral(false)).
!setup.py is now a deprecation shim; builds must go through the replacement build system.
Daytona provisions isolated development sandboxes for AI coding agents through an API and SDK.
└──▷ 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. Under60 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
Consistent daemon error codes across SDKsIMPROVED35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Propagates daemon error codes consistently across all SDKs, enabling uniform error handling for client applications.
— Describes behaviour change but no specific codes or SDK names listedsnapshot-20260903
Command Code expanded its model picker with two new options: Qwen 3.8 Max 0902 and a free LongCat 2.0 model.
The first AI coding agent that learns your coding taste. Powered by taste-1, a meta neuro-symbolic model.
Command Code expanded its model picker with two new options: Qwen 3.8 Max 0902 and a free LongCat 2.0 model.
└──▷ 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. Under60 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 selectable models: Qwen and LongCatNEW35how completely this was documenteddepth10/40specificity15/30actionability10/3035 / 100
Adds Qwen 3.8 Max 0902 as a selectable model option, and adds LongCat 2.0 as a free model option.
— Names two models but no mechanism or usage detailv1.42.0v1.41.0
$ git clone --branch commits-2026-08-11 https://github.com/cathrynlavery/diagram-design.git
# already have the repo? check out this version:$ git checkout commits-2026-08-11
└──▷ TRY IT
Verify that a beeswarm diagram's dot positions match their declared values and no two dots overprint — catch silent rendering errors before shipping.
$ python3 scripts/verify-beeswarm.py
Catch clipped SVG paint, collapsed diagrams, and page overflow by linting examples as rendered in headless Chromium rather than from source.
$ python3 scripts/lint-render.py
Validate a Draw.io file through the import extractor to confirm deterministic extraction and security hardening before integrating into the design system.
$ python3 scripts/verify-drawio-import.py
›Adds the /diagram-design:import workflow for deterministic extraction of raw, compressed, PNG-embedded, and SVG-embedded Draw.io files, with bounded decoding, malformed-container checks, and DTD/entity rejection.
›Adds scripts/verify-beeswarm.py to enforce nine geometric invariants on beeswarm diagrams — shared value scale, no-overprint, packing-only swarm offset, and related contracts — catching silent rendering errors that no other gate catches.
›Adds scripts/lint-render.py, a headless-Chromium render linter that screenshots diagrams at authored viewport size and with overflow released, diffs the two to catch clipped paint, collapsed SVGs, and page overflow invisible to source-only linters.
›Adds dumbbell as a Bar variant for comparing two states per category (PR #107).
›Adds GitHub Actions CI workflow (.github/workflows/ci.yml) running lint-skin.py, verify-sequence-oauth.py, verify-drawio-import.py, and build-icons.py on push and pull request to main, with multi-OS matrix (Linux, Windows, macOS), visual artifact upload on linter failures, and GitHub Step Summary table generation.
Cline shipped a PreToolUse hook that actively blocks reads and edits of .clineignore-matched files, and added image generation plus clearer environment scoping for scheduled runs in the desktop beta.
Autonomous coding agent as an SDK, IDE extension, or CLI assistant.
Cline shipped a PreToolUse hook that actively blocks reads and edits of .clineignore-matched files, and added image generation plus clearer environment scoping for scheduled runs in the desktop beta.
└──▷ 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. Under60 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
.clineignore enforcement via PreToolUse hookNEW96how completely this was documenteddepth37/40specificity29/30actionability30/3096 / 100
Adds PreToolUse_ClineignoreGuard.sh, a hook script installable at .clinerules/hooks/PreToolUse (VS Code extension) or .cline/hooks/PreToolUse.sh (CLI, also discoverable via ~/.cline/hooks/ or a custom --hooks-dir) that cancels any read_files, editor, apply_patch, or run_commands tool call whose target matches a .clineignore pattern before the file is accessed. .clineignore uses .gitignore-style syntax (directories, globs, ! negations) evaluated via git check-ignore scoped to that file alone, so the workspace need not be a git repo; the agent is also blocked from modifying .clineignore itself. VS Code hooks require the 'Enable Hooks' setting; hooks are disabled in --yolo mode but active under --act and --plan. Cancellations return a structured JSON reason, e.g. {"cancel": true, "errorMessage": "Blocked read_files: .env matched a .clineignore pattern…"}.
Install the .clineignore enforcement hook into a workspace so Cline can never read or edit secrets, even when instructed to.
— Full mechanism, exact paths, config syntax, and install command givenproduct docs
thinner coverage below
02
Image generation in desktop Customize → ToolsNEW46how completely this was documenteddepth18/40specificity13/30actionability15/3046 / 100
Adds an opt-in image generation capability, configurable under Customize → Tools, with provider credentials kept server-side and generated images retained in session history.
Scheduled run environment scoping in desktopIMPROVED38how completely this was documenteddepth18/40specificity12/30actionability8/3038 / 100
Scheduled runs are now grouped within their runtime environment so local and SSH schedules with similar names stay separate, and it is clarified that media-generation settings configure only the local runtime while an SSH environment is selected.
Codex CLI's latest releases center on an experimental context-management mode for ChatGPT Plus/Pro sessions, alongside a new plugin marketplace, vim undo/redo in the TUI, and several config and app-server refinements.
OpenAI Codex CLI is a terminal-based coding agent for reading, changing, and testing code in local repositories.
Codex CLI's latest releases center on an experimental context-management mode for ChatGPT Plus/Pro sessions, alongside a new plugin marketplace, vim undo/redo in the TUI, and several config and app-server refinements.
└──▷ 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. Under60 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
Experimental context management for ChatGPT sessionsNEW85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
The features.context_management.experimental_mode config key (disabled by default) enables experimental context management—token-budget context, history notes, and the new_context tool—for eligible ChatGPT Plus, Pro, and Pro Lite sessions on the Codex backend.
Opt a Plus/Pro session into experimental context management to unlock token-budget context, history notes, and the new_context tool.
Automatic recap suppression via tui.auto_recapNEW65how completely this was documenteddepth20/40specificity20/30actionability25/3065 / 100
A new tui.auto_recap = false config key disables automatic session recaps in the TUI while keeping the manual /recap command available on demand.
Disable automatic session recaps so the TUI never interrupts your flow, while still letting you run /recap on demand.
toml
[tui]
auto_recap = false
— Exact config key with runnable example, but scope narrow.rust-v0.153.0
03
Vim mode undo and redo in TUI composerNEW65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
Vim mode in the TUI composer now supports undo with u and redo with Ctrl+R, preserving complete drafts including pasted content and attachments.
— Exact keybindings named but no runnable command example.rust-v0.153.0
04
App-server thread metadata and async user inputIMPROVED65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
App-server thread metadata now includes nullable model and reasoningEffort fields, and structured asynchronous questions are supported via request_user_input_async when enabled by the model catalog.
— Named fields and function but API-level, no direct usage sample.rust-v0.153.0
thinner coverage below
05
Guardian scoring skipped in User approval modeIMPROVED55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Guardian prewarming and asynchronous scoring are skipped when approvalsReviewer is 'user', automatically accepting ordinary node_repl.js execution confirmations while still surfacing sensitive-action checks.
— Names config value and behavior but no direct config key path shown.rust-v0.153.0-alpha.5.1
06
Plugin marketplace management in plugin CLINEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
The plugin CLI can now list, install, and remove plugins from remote marketplaces.
— Names the capability but no exact subcommands given.rust-v0.153.0
07
disable_paste_burst moved under tui namespaceIMPROVED50how completely this was documenteddepth15/40specificity20/30actionability15/3050 / 100
disable_paste_burst is now nested as tui.disable_paste_burst, though the top-level setting remains supported as a fallback.
— Exact config key path named but no example of use.rust-v0.153.0
08
Earlier usage allowance warning for Plus/TeamIMPROVED45how completely this was documenteddepth20/40specificity20/30actionability5/3045 / 100
Plus and Team users now receive an earlier warning when less than half of their allowance remains in an approximately five-hour usage window.
— Concrete threshold and window given, but no action for user.rust-v0.153.0
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.259 adds an organization-wide managed MCP server setting alongside a breaking change to how MCP server allow/deny lists work, plus a headless permission-denial flag, GitLab MR recognition, and small workflow/VSCode UI improvements.
└──▷ 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. Under60 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
managedMcpServers managed setting for MCP serversNEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds managedMcpServers managed setting so organizations can push HTTP/SSE MCP servers, using the same entry shape as .mcp.json, to every user; entries that specify a command to run are skipped.
Push a shared internal MCP server to every user in the organization via managed settings.
— Exact config key and runnable JSON example given.v2.1.259
02
--permission-prompts none flag for headless hostsNEW85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
Adds --permission-prompts none flag for unattended headless hosts: any action that would trigger a permission prompt is automatically denied while the active permission mode (including auto mode) continues to decide other actions.
— Exact flag name and mechanism, ready to run.v2.1.259
03
deniedMcpServers replaces allowedMcpServers for managed blockingBREAKING80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
Adds deniedMcpServers as the correct mechanism to block a managed-mcp.json server. allowedMcpServers now governs only user-added servers and no longer filters managed servers — a server previously blocked by your allowlist will load on upgrade unless moved to deniedMcpServers.
— Names all three config surfaces and the upgrade impact, no runnable command.v2.1.259
04
GitLab merge request recognition in tool summariesNEW75how completely this was documenteddepth25/40specificity30/30actionability20/3075 / 100
Adds recognition of glab mr create/merge/close/reopen/note/update commands so GitLab merge requests appear as MR !N in the collapsed tool summary and update the footer MR badge.
— Names all recognized subcommands and UI effect.v2.1.259
05
--json output for claude plugin validateNEW65how completely this was documenteddepth15/40specificity20/30actionability30/3065 / 100
Adds --json flag to claude plugin validate to emit a machine-readable validation report.
— Exact command and flag given, but no output detail.v2.1.259
thinner coverage below
06
Improved /workflows agent detail viewIMPROVED55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Improves the /workflows agent detail view with pretty-printed, syntax-colored JSON outcomes and an expand toggle for long outcomes.
— Clear UI change but no navigation path spelled out.v2.1.259
07
Session list filters in VSCode extensionNEW55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Adds an Active quick filter and a status filter menu (Needs input, Working, Completed) to the session list sidebar in the VSCode extension.
— Names the filters and location, but only a UI path.v2.1.259
08
Faster headless/SDK session startIMPROVED45how completely this was documenteddepth20/40specificity20/30actionability5/3045 / 100
Improves headless/SDK session start so the first turn begins up to 50 ms sooner when MCP servers finish connecting.
— Concrete number but nothing for a reader to act on.v2.1.259
└──▷ BREAKING ON UPGRADE
!allowedMcpServers no longer filters out managed servers delivered via managed-mcp.json; a server previously blocked by your allowlist will now load on upgrade. Use deniedMcpServers to keep it off.
Zed v1.18.0 adds inline C/C++ variable values and finer debugger controls, persistent file finder history, and a configurable per-provider debounce for inline completions, alongside new model support for GPT-5.6, Gemini 3.5 Flash-Lite and Grok 4.5/4.6.
Code at the speed of thought – Zed is a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Zed v1.18.0 adds inline C/C++ variable values and finer debugger controls, persistent file finder history, and a configurable per-provider debounce for inline completions, alongside new model support for GPT-5.6, Gemini 3.5 Flash-Lite and Grok 4.5/4.6.
└──▷ 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. Under60 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
Per-provider inline completion debounce settingNEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds the edit_predictions.<provider>.prediction_debounce setting to control inline completion debounce timing per provider, for example setting "prediction_debounce": 300 under "copilot" in settings.json to reduce completion flicker on slow connections.
Reduce inline completion flicker on slow connections by increasing the debounce delay for a specific provider.
— Exact config key and runnable JSON snippet givenv1.18.0
02
Git diff base toggle actionNEW80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Adds the git: toggle diff base action, run from the Command Palette, to switch the diff base between HEAD and the default branch.
Toggle the diff base to compare working changes against the default branch instead of HEAD.
📍Open the Command Palette (cmd-shift-p / ctrl-shift-p), then run 'git: toggle diff base' to switch the diff base between HEAD and the default branch.
— Named action with exact command palette stepsv1.18.0
03
Debugger improvements for C/C++ and thread controlNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds inline variable values for C and C++ when debugging with CodeLLDB or GDB, and adds separate 'Continue Program' and 'Continue Thread' controls for debug adapters that support single-thread execution.
— Describes two debugger features but no exact UI path givenv1.18.0
04
New AI model support across providersNEW65how completely this was documenteddepth20/40specificity30/30actionability15/3065 / 100
Adds GPT-5.6 with a 1M-token context window on Amazon Bedrock, adds Gemini 3.5 Flash-Lite to the Google AI model list, and adds Grok 4.5 and Grok 4.6 to the xAI model list.
— Names specific models and providers but no usage stepsv1.18.0
thinner coverage below
05
Persistent file finder historyNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
File finder history now persists across workspace sessions, surfacing recently opened files from previous sessions.
— Explains behaviour change but no config or command givenv1.18.0
06
Reload broken external agent connectionIMPROVED50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Adds the ability to reload a broken external agent connection from the Agent Panel without restarting Zed.
— Names panel and behaviour, no exact UI stepsv1.18.0
07
Bash Language Server config keyNEW50how completely this was documenteddepth15/40specificity20/30actionability15/3050 / 100
Adds the lsp.bash-language-server.settings config key for configuring the Bash Language Server.
— Named config key but no example values givenv1.18.0
08
in_preview keybinding contextNEW50how completely this was documenteddepth15/40specificity20/30actionability15/3050 / 100
Adds the in_preview keybinding context for editors in preview mode, enabling preview-specific key mappings.
— Named context but no example keymap shownv1.18.0
09
Terminal ctrl-alt-letter keystroke supportNEW45how completely this was documenteddepth10/40specificity20/30actionability15/3045 / 100
Adds terminal support for ctrl-alt-<letter> keystrokes.
— Named keystroke pattern but no configuration detailv1.18.0
10
Permalink support for Tangled repositoriesNEW40how completely this was documenteddepth10/40specificity20/30actionability10/3040 / 100
Adds permalink support for Tangled repositories in the Git integration.
— Names the integration but no mechanism or stepsv1.18.0
11
Tabular data preview settings in popoverIMPROVED35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Tabular data preview settings moved into a popover, freeing vertical space for the table.
— Describes UI change but not exact navigationv1.18.0
12
Markdown preview styling improvementsIMPROVED30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Improved Markdown preview styling with better typography, spacing, and rounded inline code backgrounds.
— Cosmetic change with no specifics or pathv1.18.0
13
Git Graph and history search focusIMPROVED30how completely this was documenteddepth10/40specificity10/30actionability10/3030 / 100
Git Graph and Git history views now initially focus the search editor.
— Small UI behaviour change, minimally describedv1.18.0
mex v0.8.0 adds Project Hub team workflows — governed Spec authoring, a Team Inbox, Relay handoffs, and canonical Workstream/Member management — alongside explicit graph maintenance commands, agent-safe capability discovery via mex capabilities --json, provenance-gated graph reads, a Wiki index and read layer, and a release-performance gate.
Persistent project memory for AI coding agents. Structured scaffold + drift detection CLI.
mex v0.8.0 adds Project Hub team workflows — governed Spec authoring, a Team Inbox, Relay handoffs, and canonical Workstream/Member management — alongside explicit graph maintenance commands, agent-safe capability discovery via mex capabilities --json, provenance-gated graph reads, a Wiki index and read layer, and a release-performance gate.
└──▷ 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. Under60 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
Explicit graph maintenance commandsNEW80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Adds mex graph status, mex graph refresh, and mex graph rebuild for explicit graph maintenance; the bare mex graph command remains a safe rebuild alias.
Inspect graph freshness without triggering an implicit rebuild — useful in CI to assert the graph is up to date before running queries.
$ mex graph status
Explicitly refresh the graph index after making source changes, without relying on implicit maintenance during reads.
$ mex graph refresh
— Exact commands given with clear alias behaviourv0.8.0
02
Governed Spec authoring and Team InboxNEW75how completely this was documenteddepth35/40specificity25/30actionability15/3075 / 100
Adds a governed Team Inbox and Spec-authoring workflow supporting local drafts, portable canonical proposals, and explicit approval, rejection, withdrawal, stale detection, and repair — each bounded to a single Spec create or update.
— Detailed lifecycle but no exact commands or endpointsv0.8.0
03
Provenance-gated graph readsIMPROVED73how completely this was documenteddepth30/40specificity28/30actionability15/3073 / 100
graph get, graph query, and impact are now gated on fresh provenance-bound observations, using owner-token writer serialization and atomic snapshot publication to ensure reads reflect current state.
— Mechanism named but no runnable example shownv0.8.0
04
Agent-safe capability discoveryNEW70how completely this was documenteddepth20/40specificity20/30actionability30/3070 / 100
mex capabilities --json lists installed and currently available commands in machine-readable form, suitable for agent or script consumption.
Discover which mex commands are installed and currently available in a machine-readable format, suitable for agent or script consumption.
$ mex capabilities --json
— Exact flag and command given, minimal further mechanismv0.8.0
05
Canonical Workstream CLI and Hub surfacesNEW70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Adds bounded canonical Workstream CLI and Hub surfaces with signed preview/apply for create, update, and one-way archive operations; each successful canonical mutation emits exactly one immutable Activity event.
— Mechanism detailed but no exact command syntaxv0.8.0
06
Fresh-project setup automationNEW70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
New fresh-project setup populates the scaffold with Claude Code or Codex, builds the Graph, completes Wiki migration and indexing, installs official skills, and validates the result before Hub starts.
— Full setup sequence described, no exact command givenv0.8.0
07
Wiki index and read layerNEW65how completely this was documenteddepth25/40specificity28/30actionability12/3065 / 100
Adds a disposable Wiki index with schema, discovery, rebuild, atomic publish, and refresh operations, plus a read layer covering get, list, search, and related operations over stable index snapshots.
— Operations named but no exact command syntaxv0.8.0
08
Canonical Member workflowsNEW62how completely this was documenteddepth28/40specificity22/30actionability12/3062 / 100
Adds bounded Member workflows with signed preview/apply, local actor selection, exact revisions, and immutable Activity emission for accepted canonical mutations.
— Mechanism named but no exact commands shownv0.8.0
thinner coverage below
09
Project Hub Activity and Code workbenchesNEW55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Adds a read-only Activity workbench in the Project Hub, backed by a bounded activity timeline API and surfacing real activity summaries and actors, plus a read-only Code workbench backed by stable graph index snapshots.
— UI surfaces described but no navigation path givenv0.8.0
10
Relay handoffs for team workflowsNEW53how completely this was documenteddepth25/40specificity18/30actionability10/3053 / 100
Adds Relay handoffs with publication-time repository context and an acknowledge/close lifecycle for durable team handoffs.
— Lifecycle named but no commands or UI pathv0.8.0
11
Release-performance gateNEW52how completely this was documenteddepth22/40specificity25/30actionability5/3052 / 100
Adds a release-performance gate covering Hub startup, idle CPU/RAM, browser heap, API latency, maintenance working sets, asset closure, and Graph/Wiki database ratios.
— Scope named, no thresholds or commands givenv0.8.0
12
Schema v3 graph migrationIMPROVED46how completely this was documenteddepth20/40specificity18/30actionability8/3046 / 100
Adds schema v3 graph migration with a real migration ladder and a subject-keyed baseline.
— Mechanism named briefly, no migration command givenv0.8.0
Qwen Code's v0.2.0 release adds mid-session output-style switching, an OpenTUI renderer backend, hot-reloadable model provider configs, workspace-scoped MCPMCPModel Context Protocol, an open standard from Anthropic that lets an AI model call external tools and data sources through a uniform interface, so cyber tools can expose capabilities directly to LLM-based agents., a Mem0 extension, several web-shell UI additions, and tightens AUTO-mode approval for out-of-workspace writes.
An open-source AI coding agent that lives in your terminal.
Qwen Code's v0.2.0 release adds mid-session output-style switching, an OpenTUI renderer backend, hot-reloadable model provider configs, workspace-scoped MCPMCPModel Context Protocol, an open standard from Anthropic that lets an AI model call external tools and data sources through a uniform interface, so cyber tools can expose capabilities directly to LLM-based agents., a Mem0 extension, several web-shell UI additions, and tightens AUTO-mode approval for out-of-workspace writes.
└──▷ 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. Under60 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
OpenTUI renderer backendNEW75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
Activates the OpenTUI backend renderer, enabled via the QWEN_TUI_RENDERER environment variable, and adds a gated bun/OpenTUI preview flavor to standalone releases.
Enable the new OpenTUI renderer to try the next-generation terminal UI backend.
$ QWEN_TUI_RENDERER=1 qwen
— Named env var and preview flavor, but no behavior detail.live-host-v0.2.0
02
/output-style command for mid-session switchingNEW65how completely this was documenteddepth20/40specificity20/30actionability25/3065 / 100
Adds an /output-style slash command with an interactive picker to switch output style mid-session, available in both the standard and OpenTUI renderers.
Switch output style mid-session without restarting — useful when moving between verbose debugging and compact review modes.
$ qwen
# Inside the session:
/output-style
— Exact command given but no detail on style options.live-host-v0.2.0
thinner coverage below
03
Hot-reload for modelProviders configIMPROVED55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Supports hot-reloading modelProviders configuration without restarting the session.
— Names config key but no file path or reload trigger.live-host-v0.2.0
04
Web-shell interface additionsNEW55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Adds standalone chat sessions, an experimental session workflow cockpit, a Workspaces overview panel, sidebar conversation content search, and grouping of scheduled task run sessions to the web-shell interface.
— Five named UI surfaces but only reachable via navigation, not commands.live-host-v0.2.0
05
Per-session token auth for cross-session inboxNEW50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Authenticates cross-session inbox connections with per-session tokens, and gives a session's own processes a child token recognized by the inbound gate.
— Explains mechanism but no config or command to act on.live-host-v0.2.0
06
ACP backend adaptor and multi-backend routingNEW50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Adds an ACP backend adaptor and multi-backend routing (qwen-live M4), plus protocol v7 playback receipts and interactive init (M5).
— Named milestones and protocol version, but no usage steps.live-host-v0.2.0
07
PR creation bound inside session shellIMPROVED45how completely this was documenteddepth15/40specificity15/30actionability15/3045 / 100
Binds PRs created via gh pr create inside the session shell.
— Names the exact command but not the binding mechanism.live-host-v0.2.0
08
AUTO-mode approval restriction for out-of-workspace writesBREAKING45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
AUTO-mode classifier no longer auto-approves out-of-workspace writes; it always falls back to manual approval.
— Clear before/after behavior but no flag or config to adjust it.live-host-v0.2.0
09
Workspace-scoped MCP managementNEW40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Adds workspace-scoped MCP management via the serve subsystem.
— Bare description with no commands or scope detail.live-host-v0.2.0
10
NDJSON budget diagnostics namingIMPROVED35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
Names the saturated NDJSON budget in channel-teardown diagnostics for easier debugging.
— Minor debugging aid with no reproduction steps.live-host-v0.2.0
11
Mem0 extension for external contextNEW25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Publishes the Mem0 Extension package for external context support.
— Just a package name, no usage or mechanism given.live-host-v0.2.0
Cursor's biggest addition this window is self-hosted machine execution — personal 'My Machines', scalable team pools, sandbox integrations, and computer use on Linux/Mac — alongside new BugBot review effort levels and a /autopilot command for autonomous PR completion.
Built to make you extraordinarily productive, agents turn ideas into code. Accelerate development by handing off tasks to Cursor.
Cursor's biggest addition this window is self-hosted machine execution — personal 'My Machines', scalable team pools, sandbox integrations, and computer use on Linux/Mac — alongside new BugBot review effort levels and a /autopilot command for autonomous PR completion.
└──▷ 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. Under60 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
Team pools with pool hibernationNEW65how completely this was documenteddepth35/40specificity20/30actionability10/3065 / 100
Team pools are named queues of self-hosted workers that scale capacity dynamically as requests arrive and shrink as workers disconnect, with no repository lock-in. Pool hibernation lets idle machines sleep and restores them within a reconnect window on follow-up requests, avoiding keeping idle capacity warm.
Computer use for self-hosted workersNEW65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Adds computer use (click, type, screenshot, browser control) for self-hosted workers on Linux and Mac, with live desktop observation and takeover from the Cursor UI.
— Describes capabilities and platforms; UI path is a clear startSelf-hosted machines
03
Self-hosted machines and My MachinesNEW60how completely this was documenteddepth30/40specificity15/30actionability15/3060 / 100
Introduces self-hosted machines that run tool execution entirely within your own network, keeping codebases, build outputs, and secrets on internal infrastructure. Adds 'My Machines' for connecting a single laptop or VM to a personal account for individual workflows.
— Explains network-locality mechanism but no exact setup commandSelf-hosted machines
04
Cloud agent execution on external sandboxesNEW60how completely this was documenteddepth15/40specificity30/30actionability15/3060 / 100
Enables cloud agents to execute on AWS Lambda, Coder, Cloudflare, Daytona, Modal, Namespace, Vercel, and E2B sandboxes.
BugBot Low and Smart effort levelsNEW55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Adds a Low effort level to BugBot that optimizes for cost while keeping review quality close to Default. Adds a Smart effort level that lets you describe conditions for when to use Low, Default, or High, and Cursor dynamically sets the effort level based on those instructions.
— Names both levels and their logic but no config path givenproduct docs
06
/autopilot command for PR handoffNEW50how completely this was documenteddepth15/40specificity15/30actionability20/3050 / 100
New /autopilot command lets a cloud subagent autonomously take over and drive a pull request to completion.
— Exact runnable command named, but behaviour described brieflyproduct docs
Kiro is an agentic development environment that uses spec-driven workflows to plan, build, and maintain software.
Kiro shipped cloud-synced personal configuration spanning the CLI and IDE, a new capability-based permissions system that replaces trusted commands, and a wave of IDE workflow features including Custom Agents, Agent Focus, Dockable Chat, and a restructured hooks format.
└──▷ 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. Under60 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
Cloud configuration sync across CLI and IDENEW88how completely this was documenteddepth35/40specificity28/30actionability25/3088 / 100
Kiro Web's cloud configuration syncs personal Steering, custom agents, Skills, Powers, and Hooks to both the CLI and IDE. In CLI V3 sessions, after uploading a .kiro configuration file you enable 'Apply cloud configuration to local CLI sessions' in Kiro Web, which loads cloud Steering, custom agents, Skills, Powers, and Hooks into new local sessions without writing files to the local directory. In the IDE, synced items appear across their usual surfaces with cloud indicators; Steering, Skills, and Hooks sourced from cloud open as read-only previews with an 'Edit in web' action, and cloud-synced Powers appear in the installed Powers list where you can select 'Try power' to review bundled Skills and MCP configuration.
Enable cloud configuration sync so new local CLI sessions automatically inherit your cloud-uploaded Steering, agents, and Skills — without copying files locally.
📍In Kiro Web, go to Configuration Sync and upload your personal .kiro configuration, then enable 'Apply cloud configuration to local CLI sessions'.
Access cloud-managed Powers and review their bundled Skills and MCP configuration without leaving the IDE.
📍In the IDE, go to Powers › Installed, locate a cloud-synced Power (marked with a cloud indicator), and select 'Try power' to review its bundled Skills and MCP configuration.
Configuration inspection panel via /configNEW80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
The /config command in V3 CLI sessions inspects all configured agents, MCP servers, Powers, Steering, Skills, and Hooks in one terminal view, labeling each item as local, cloud, or both.
Audit every configured resource (agents, MCP servers, Powers, Hooks) in a running V3 session to confirm what is loaded and whether each item comes from local, cloud, or both.
Session dashboard in CLI V3NEW75how completely this was documenteddepth25/40specificity20/30actionability30/3075 / 100
The kiro-cli chat --sessions flag and /sessions command open a V3 session dashboard to browse, search, resume, and delete both local and cloud sessions.
Resume a past cloud session without hunting through local files — launch the session dashboard directly from the CLI.
Capability-based permissions via permissions.yamlBREAKING75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
Trusted Commands and Command Denylist are replaced by permissions.yaml shell rules, allowing allow and deny entries scoped to a workspace or globally, with defaults applying without any configuration. Existing trusted command prefixes must be translated to allow rules and denylist entries to deny rules, or shell commands other than read-only Git commands will prompt for approval.
Restructured hook configuration formatBREAKING75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
Hooks now use a structured v1 JSON format stored in .kiro/hooks/, with triggers for file events, tool use interception, spec tasks, and prompt submission; legacy 0.x hooks can be migrated directly from the Agent Hooks panel. Manual hooks are replaced by manual steering files.
Custom Agents defined in MarkdownNEW75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
Custom Agents are defined in a Markdown file using read, write, shell, and web tags to declare tool access, can embed MCP servers and permission rules inline, and can be shared via version control; the agent appears in the agent selector on save.
Dockable Chat as editor tabNEW65how completely this was documenteddepth25/40specificity15/30actionability25/3065 / 100
Any chat session can be opened as a full-width editor tab via right-click > 'Open in Editor', with support for horizontal/vertical splits, dragging between editor groups, and multi-monitor setups; the panel and tab stay in sync.
Open a long chat session as a dockable tab so you can review agent output alongside your source files on a second monitor.
📍Right-click a chat tab in the panel › select 'Open in Editor' › drag the resulting editor tab to a second monitor or split group.
Inline Chat retired in favor of unified chat shortcutsBREAKING65how completely this was documenteddepth20/40specificity20/30actionability25/3065 / 100
Inline Chat is retired; selecting code and pressing Cmd+L (macOS) or Ctrl+L (Windows/Linux) brings it into the current chat, while Cmd+Shift+L / Ctrl+Shift+L starts a new session with the selection.
Agent Focus experimental modeNEW60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
An experimental Agent Focus mode launches independent, parallel agent sessions from a chat-first layout with inline diffs, status-at-a-glance, and structured workflow starters (Spec, Plan, Bug Fix, Quick Spec); it is toggled from the top-right corner.
Agent Selection in chat input barNEW45how completely this was documenteddepth20/40specificity10/30actionability15/3045 / 100
A new agent selector in the chat input bar lets you switch between Default, custom, or Spec agents mid-session without losing conversation history, with a persistent preferred default agent across restarts.
!Trusted Commands and Command Denylist are removed; existing trusted command prefixes must be translated to allow rules and denylist entries to deny rules in permissions.yaml shell rules, or shell commands other than read-only Git commands will prompt for approval.
!Inline chat is retired in IDE 1.0; the equivalent workflow is selecting code and using Cmd+L / Ctrl+L (or right-click > Kiro > Ask Kiro) to bring it into a chat session.
!Manual hooks are replaced by manual steering files.
PydanticAI v2.38.0 adds context-window visibility, a self-hosted vLLM provider, typed custom events for the run stream, and support for three new models.
How Python does AI. Agents, realtime voice, image generation, embeddings.
PydanticAI v2.38.0 adds context-window visibility, a self-hosted vLLM provider, typed custom events for the run stream, and support for three new models.
└──▷ 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. Under60 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
Context window tracking on runsNEW80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Adds a context_window field to ModelProfile and a context_window_used field to RunContext so agent code can inspect how much of the model's context window has been consumed during a run, e.g. to gate expensive downstream calls from inside a tool.
Check how much of the model's context window your agent has consumed inside a tool, to gate expensive downstream calls.
python
from pydantic_ai import Agent, RunContext
agent = Agent('openai:gpt-5.6-sol')
@agent.tool
def context_guard(ctx: RunContext[None]) -> str:
used = ctx.context_window_used
return f'Context used so far: {used} tokens'
— Named fields with a runnable code examplev2.38.0
02
Typed custom events in the run streamNEW60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Enables application code and capabilities to emit typed CustomEvents and CapabilityEvents into the run event stream, with @on_event for subscribing to them.
CAMEL AI added a new telephony toolkit, a search API integration, and improved logging for truncated tool outputs.
CAMEL: The first and the best multi-agent framework. Finding the Scaling Law of Agents. https://www.camel-ai.org
CAMEL AI added a new telephony toolkit, a search API integration, and improved logging for truncated tool outputs.
└──▷ 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. Under60 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
PlivoToolkit for telephony actionsNEW50how completely this was documenteddepth15/40specificity20/30actionability15/3050 / 100
Adds PlivoToolkit for programmatic telephony actions via the Plivo API.
— Names toolkit and API but no methods or usage shownv0.2.91a6
02
Querit integration in SearchToolkitNEW50how completely this was documenteddepth15/40specificity20/30actionability15/3050 / 100
Adds Querit content-fetch API integration to SearchToolkit.
— Names module and provider but no method signaturev0.2.91a6
03
Truncated tool-output logging to filesIMPROVED40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
Saves truncated tool outputs to log files so full payloads are not silently dropped at runtime.
— Explains behavior but no file path or config key givenv0.2.91a6
vMLX 1.6.52 adds video loading support and an opt-in BF16BF16A 16-bit floating-point format that truncates the 32-bit IEEE float's mantissa while keeping its full exponent range, trading precision for half the memory and faster matrix math on supported hardware.DSADSAA public-key signature algorithm standardized by NIST that generates and verifies digital signatures; tools use it to authenticate code, certificates, or data without exposing the private key. indexer for GLM5 models, while also smoothing automated deployments with non-interactive gateway starts and broader install-time compatibility.
The vMLX server runs compressed MLX models on Apple Silicon with disk caching, paged memory, continuous batching, and hybrid SSM scheduling.
vMLX 1.6.52 adds video loading support and an opt-in BF16BF16A 16-bit floating-point format that truncates the 32-bit IEEE float's mantissa while keeping its full exponent range, trading precision for half the memory and faster matrix math on supported hardware.DSADSAA public-key signature algorithm standardized by NIST that generates and verifies digital signatures; tools use it to authenticate code, certificates, or data without exposing the private key. indexer for GLM5 models, while also smoothing automated deployments with non-interactive gateway starts and broader install-time compatibility.
└──▷ 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. Under60 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
BF16 DSA indexer state for GLM5NEW40how completely this was documenteddepth15/40specificity20/30actionability5/3040 / 100
Adds opt-in BF16 DSA indexer state and scoring for GLM5 models.
— Names model and mechanism but no flag or config givenv1.6.52
02
Non-interactive gateway model startsIMPROVED35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Keeps gateway model starts non-interactive, removing prompts that could block automated or headless deployments.
— Explains behavior change but no exact flag or commandv1.6.52
03
Video loading support via mlx-vlmNEW30how completely this was documenteddepth10/40specificity15/30actionability5/3030 / 100
Adds support for current mlx-vlm video loading (#265).
— Names issue and library but no usage detailv1.6.52
04
Packaged Python launcher in install proof harnessIMPROVED25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Accepts packaged Python launcher in the installed proof harness, broadening install-time compatibility.
— Vague on what changed for install harnessv1.6.52
Solution for long term memory for agent coding CLIs and to facilitate handoff between different agent vendors
ai-memory v2.0 is a major release centered on local hybrid embeddings enabled by default and a new OKF on-disk format with strict migration safeguards, alongside time-travel queries, typed relation edges, and a new retrieval benchmark harness.
└──▷ 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. Under60 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
OKF on-disk format with export subcommand and migration safeguardsBREAKING93how completely this was documenteddepth35/40specificity30/30actionability28/3093 / 100
Adds ai-memory export-okf subcommand to stream a validated Open Knowledge Format v0.2 bundle importable anywhere. First start of v2.0 migrates the wiki to OKF in place, gated on a verified full backup written to your home directory or the path set via AI_MEMORY_BACKUP_DIR — the server refuses to start if the backup cannot be written and verified. Once migrated, pre-2.0 binaries refuse to open the data directory, shared stores require all machines to be upgraded simultaneously, and downgrading is not supported.
Export your entire wiki as a portable, validated OKF v0.2 bundle to share with or import into another tool.
$ ai-memory export-okf
— Names subcommand, format version, env var, and migration constraints.v2.0.0
02
Local hybrid embeddings enabled by defaultBREAKING83how completely this was documenteddepth30/40specificity28/30actionability25/3083 / 100
In-process sentence embeddings (pure Rust, no API key) now run by default, with existing pages automatically backfilled; add embedding_provider = "none" to opt out. First start downloads the ~87 MB model in the background and hybrid search activates on the next restart, while air-gapped installs remain FTS-only unless model files are placed manually.
Opt out of local embeddings on an air-gapped host so the server stays FTS-only without attempting a model download.
toml
embedding_provider = "none"
— Names config key, model size and restart behavior.v2.0.0
03
Retrieval benchmark harness (ai-memory-eval retrieval)NEW83how completely this was documenteddepth30/40specificity28/30actionability25/3083 / 100
Adds ai-memory-eval retrieval subcommand to run the LongMemEval-S benchmark end-to-end against a live server; hit@5 improved from 0.617 to 0.823 in this release.
Run the LongMemEval-S retrieval benchmark end-to-end against a live server to measure and track search quality over time.
$ ai-memory-eval retrieval
— Names subcommand, benchmark, and before/after metric.v2.0.0
04
Time-travel queries via as_of parameterNEW67how completely this was documenteddepth25/40specificity22/30actionability20/3067 / 100
Adds as_of parameter to memory_query to retrieve knowledge as it stood at a past point in time, including entries that have since been superseded.
— Names parameter and query but no usage example.v2.0.0
05
Typed relation edges in page frontmatterNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds causes, fixes, and contradicts typed relation edges in page frontmatter; declared contradictions surface as lint findings with zero LLM cost.
— Names edge types and lint behavior, no example given.v2.0.0
thinner coverage below
06
Offline durability for TypeScript integrationsIMPROVED59how completely this was documenteddepth25/40specificity22/30actionability12/3059 / 100
Adds offline durability for TypeScript integrations (OpenCode, OMP, Pi, OpenClaw) — failed hook deliveries are spooled and drained automatically once the server is reachable again.
— Names integrations and spooling mechanism, no config surface.v2.0.0
07
Expanded status reportingIMPROVED55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Extends status output to truthfully report embedding coverage, wiki format, typed edges, and write-queue backpressure.
— Names status fields but no example or exact syntax.v2.0.0
08
Opt-in cross-session experience reviewNEW47how completely this was documenteddepth22/40specificity15/30actionability10/3047 / 100
Adds a cross-session experience pass (opt-in) that periodically reviews recent trajectories for knowledge only visible across sessions, staged through the gated auto-improve path.
— Describes mechanism but no config key or trigger given.v2.0.0
09
Configurable LLM reasoning effortNEW40how completely this was documenteddepth10/40specificity15/30actionability15/3040 / 100
Adds llm_reasoning_effort config key supported across providers.
— Names config key but no values or scope explained.v2.0.0
10
macOS launchd service agentNEW30how completely this was documenteddepth10/40specificity10/30actionability10/3030 / 100
Adds a macOS launchd agent for service management.
!First start of v2.0 migrates the wiki to OKF in place; migration is gated on a verified full backup written to your home directory or AI_MEMORY_BACKUP_DIR — the server refuses to start if the backup cannot be written and verified.
!Once a data directory is migrated to OKF, pre-2.0 binaries refuse to open it; shared stores require all machines to be upgraded simultaneously — downgrading is not supported.
!Hybrid search (local embeddings) is enabled by default; first start downloads the ~87 MB model in the background and backfills existing pages, with hybrid search activating on the next restart. Air-gapped installs remain FTS-only unless model files are placed manually.
Pinecone shipped general availability of Nexus, a knowledge engine that lets agents query curated data sources for grounded, cited answers.
Pinecone is the vector database for AI agents and applications, built for semantic search, knowledge retrieval, and long-term memory at scale.
Pinecone shipped general availability of Nexus, a knowledge engine that lets agents query curated data sources for grounded, cited answers.
└──▷ 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. Under60 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
Pinecone Nexus knowledge engine GANEW50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Pinecone Nexus is now generally available. It lets users point it at data sources, curate them into a context, and query that context to receive grounded, cited answers for AI agents.
— Describes workflow but no concrete API, flag, or UI path givensnapshot-20260903
OpenAI shipped an official Terraform provider that lets teams manage API platform resources like projects, users, and service accounts as infrastructure as code.
Docs and resources to help you build with, for, and on OpenAI.
OpenAI shipped an official Terraform provider that lets teams manage API platform resources like projects, users, and service accounts as infrastructure as code.
└──▷ 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. Under60 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
Official Terraform provider for OpenAI platformNEW76how completely this was documenteddepth30/40specificity28/30actionability18/3076 / 100
A new official OpenAI Terraform provider is available from the Terraform Registry for infrastructure-as-code management of OpenAI API platform resources. It supports provisioning and managing projects, users, groups, roles, access assignments, service accounts, certificates, invitations, and project-level rate limits, and works with standard Terraform workflows including plan/apply, importing existing resources, and drift detection and reconciliation.
— Names resources and workflows but no exact provider address or example config.snapshot-20260903
Gemini API shipped generally-available gemini-3.8-flash — a 1M-token-context, 64k-output model now the default for Managed Agents and the Antigravity SDK — rolled out across nearly every API surface, alongside new agentic video timeline understanding and a breaking change dropping support for the minimal thinking level.
Build with Gemini 2.0 Flash, 2.5 Pro, and Gemma using the Gemini API and Google AI Studio.
Gemini API shipped generally-available gemini-3.8-flash — a 1M-token-context, 64k-output model now the default for Managed Agents and the Antigravity SDK — rolled out across nearly every API surface, alongside new agentic video timeline understanding and a breaking change dropping support for the minimal thinking level.
└──▷ 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. Under60 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
Gemini 3.8 Flash model launch across API surfacesNEW85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
The new gemini-3.8-flash model is now generally available via the Gemini API, offering a 1M token context window and 64k max output tokens, and is engineered for long-horizon software engineering, autonomous multi-step agent workflows, and complex enterprise data pipelines. It is selectable via "model": "gemini-3.8-flash" across custom agents, the Antigravity agent, managed agents, structured output requests, the thinking endpoint, audio, text generation, and omni docs, and is now the default model for Managed Agents and the Antigravity SDK, replacing the previous default.
Target the new Gemini 3.8 Flash model when configuring a managed agent request.
json
{
"model": "gemini-3.8-flash"
}
Use the new Gemini 3.8 Flash model for faster, cost-efficient text generation calls.
$ curl https://generativelanguage.googleapis.com/v1beta/models/gemini-3.8-flash:generateContent?key=$GEMINI_API_KEY \
-H 'Content-Type: application/json' \
-d '{"contents": [{"parts": [{"text": "Explain SQL injection in one paragraph."}]}]}'
Call the new Gemini 3.8 Flash model via the REST API for an agentic or complex enterprise task.
— Names surfaces, specs and default change, includes runnable curl calls.September 2, 2026
thinner coverage below
02
Minimal thinking level removed for Gemini 3.8 FlashBREAKING50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
The minimal thinking level is not supported on gemini-3.8-flash; workflows that set thinking effort to minimal must be updated before migrating to the new model.
— Names the exact setting and required migration action, no mechanism detail.product docs
└──▷ BREAKING ON UPGRADE
!The minimal thinking level is not supported on gemini-3.8-flash; workflows that set thinking effort to minimal must be updated before migrating.