The daily firehose — everything the toolchain shipped today, already filtered.
// HOW THIS ISSUE IS MADE
We read every release from the 354 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# 37 tools matched
Same issue, same prompt, two writers:
What stands out across today's releases, grouped by what it lets you do. Every tool named links to its entry below.
Three unrelated things stand out. Hermes's agent can now sign in and pay through 1Password, Bitwarden or a local vault without the secret ever entering the model's context; FailproofAI scans agent transcripts for credentials already leaked; and Pinecone ships a local Docker emulator, so index code runs offline instead of against a billed cloud index.
govern
Let an agent authenticate and transact without putting the secret in the prompt
Hermes brokers logins, payments and form fills through 1Password, Bitwarden or a local vault so credentials never reach the model, and browser-use Cloud's V4 secret bindings scope injected credentials to a run rather than the whole agent. OpenBot moves credentials off .env into platform-native stores, closing the most common way a key ends up in a repo.
Find credentials your agents already leaked into their own transcripts
FailproofAI 1.0.4 audits agent transcripts locally for credential exposure, with alerting and native OpenClaw SQLite support. Prevention only helps going forward; this tells you which of your existing session logs are now secret-bearing artifacts.
Develop and test vector-search code with no cloud index attached
Pinecone's Docker emulator lets retrieval code run in CI and on a laptop offline, removing the shared-staging-index bottleneck and the bill for test writes. DSPy's local CPython interpreter similarly keeps code-executing agents off a remote sandbox during development.
Three unrelated things stand out today: Pinecone now lets retrieval teams build against a local emulator before touching cloud state; Braintrust can run server-side trace automations instead of waiting for manual investigation; Together AI added fine-tune validation and live metrics so bad jobs fail earlier and tuning is easier to watch.
build
Develop retrieval features locally before provisioning cloud infrastructure
The local Docker emulator gives teams a target for offline development, while the schema-based Documents API formalizes how document data is represented. That makes retrieval app work less dependent on shared cloud projects and reduces the chance that early integration tests mutate production-like indexes.
Turn trace review into an automated production workflow
Loop automations add a managed server-side runtime, and Patterns automates trace investigation. Instead of exporting traces, writing one-off scripts, or waiting for a human to inspect recurring failures, teams can run repeatable checks and investigations where the traces already live.
Catch fine-tuning mistakes before and during the run
Pre-flight dataset validation can reject malformed or unsuitable training inputs before spend starts, while live metrics and early stopping give teams feedback during the job rather than after the model finishes. That removes some of the babysitting and post-hoc guesswork from tuning workflows.
Let agents use credentials without showing secrets to the model
Hermes added a password-blind vault backed by 1Password, Bitwarden, or a local vault; browser-use added scoped secret bindings for runs; OpenBot moved credentials out of .env into platform-native stores. The common outcome is narrower credential exposure: agents can complete authenticated work without copying raw secrets through prompts, logs, or ad hoc config files.
ⓘSourcesRelease page →1 RELEASE · seen 2026-09-12NOTES ↗RankWhy this ranktop features scored 85/80/60, +15 breaking change, +6 runnable example — 96How ranking works →
v0 shipped chat-visibility controls for teams (with a breaking default-visibility change), two new MCPMCPModel Context Protocol, an open standard from Anthropic that lets an AI model call external tools and data sources through a uniform interface, so developers avoid writing custom integrations for every service. server tools for automating chats, Platform API support for attaching memory/skills, and enforcement of team deployment policies in the deploy flow, alongside smaller Design Systems and permissions updates.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
The v0 generative UI platform builds web applications from natural-language prompts.
v0 shipped chat-visibility controls for teams (with a breaking default-visibility change), two new MCPMCPModel Context Protocol, an open standard from Anthropic that lets an AI model call external tools and data sources through a uniform interface, so developers avoid writing custom integrations for every service. server tools for automating chats, Platform API support for attaching memory/skills, and enforcement of team deployment policies in the deploy flow, alongside smaller Design Systems and permissions updates.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
8 FEATURES7 OF 8 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Default chat visibility setting for teamsBREAKING85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
Adds Settings → Workspace → Default Chat Visibility with three options — Private, Team can view, and Team can edit — letting team owners control the default visibility for all new chats.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ This is a breaking change: new chats in team workspaces are now visible to the team by default, so teams that relied on chats being private by default must update this setting to Private.
Lock down new team chats to invitation-only access to prevent unintended exposure of sensitive work in progress.
📍In v0, go to Settings → Workspace → Default Chat Visibility and select 'Private'.
— Exact setting path, values, and migration note given.snapshot-20260912
0202
New MCP server tools for chat automationNEW80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
Adds listMessages tool to the v0 MCP server for reading a chat's full message history, and resolveTask tool for answering plan approvals, questions, permission requests, and integration prompts programmatically. The v0 MCP server now also returns scope-aware chat URLs alongside tool responses.
— Names both tools and the response change but no invocation example.snapshot-20260912
0303
Team deployment policy enforcement in deploy flowNEW60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Enforces team Vercel deployment policies in v0's deploy button and GitHub import flow, hiding disallowed repositories and blocking production deploys the team forbids.
— Describes behavior and surfaces affected, no config keys given.snapshot-20260912
0404
Team default design system settingsNEW60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Team owners can now set a team default design system, including Design Systems 2.0 skills and built-in examples, and choose team or personal scope when saving from the save card.
— Names the feature and scoping options, no UI path given.snapshot-20260912
0500
Memories and Skills access controls expandedIMPROVED60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
The Restrict Memories and Skills setting is now available on any paid team plan instead of Enterprise only, and team members with v0 edit access can now manage team skills and memories without requiring a Vercel write role.
— Names the setting and the plan/role change precisely.snapshot-20260912
thinner coverage below
0605
Attach memory and skills via Platform APINEW55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
The Platform API now supports attaching memory and project skills when creating a chat or sending a message.
— Names the capability but no endpoint or parameter detail.snapshot-20260912
0706
Keyboard shortcut to open SettingsNEW55how completely this was documenteddepth15/40specificity20/30actionability20/3055 / 100
Adds a keyboard shortcut (Cmd+. / Ctrl+.) to open Settings directly from the editor.
— Exact keys given, but a minor convenience feature.snapshot-20260912
0807
Active teammate avatars on project cardsNEW45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Project cards now display avatars of teammates active in visible project chats within the last 24 hours, ordered by most recent activity.
— Clear description but purely visual, no actionable surface.snapshot-20260912
└──▷ BREAKING ON UPGRADE
!New chats created in a team workspace are now visible to the team by default; existing chats are unaffected, but teams that relied on chats being private by default must update Settings → Workspace → Default Chat Visibility to Private.
Letta Code is a terminal coding agent with persistent memory and identity across development sessions.
Letta Code's latest release focuses on sandbox targeting improvements in the CLI, enabling file transfers across conversations and simplifying cross-computer setups.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE1 OF 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Cross-conversation sandbox file transfers in CLIIMPROVED35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
The CLI now supports targeting another conversation when performing sandbox file transfers, and sandbox targeting has been simplified with added guidance for cross-computer scenarios.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names the capability but no exact flag or command syntax given.v0.32.3
Terminal-based AI coding assistant that integrates LLMs, LSPs, and MCP servers into your development workflow.
Crush v0.94.1 adds ChatGPT subscription login, a headless reasoning-depth control, and scroll performance improvements to the terminal UI.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
3 FEATURES2 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
ChatGPT OAuth login and logoutNEW80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Adds crush login openai (also aliased as crush login chatgpt) to authenticate with a ChatGPT subscription via OAuth, unlocking subscription-granted models without a separate API key.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ crush logout openai (also crush logout chatgpt) removes the stored OAuth credentials.
Authenticate with your existing ChatGPT subscription so Crush can use the models your plan grants, without needing a separate API key.
$ crush login openai
— Names exact commands and aliases, runnable directly.v0.94.1
0202
`--reasoning-effort` flag for headless runsNEW75how completely this was documenteddepth20/40specificity25/30actionability30/3075 / 100
Adds a --reasoning-effort flag to crush run for non-interactive/headless use, accepting values like max to control model reasoning depth — useful in CI pipelines or agent orchestration.
Run Crush headlessly with maximum reasoning effort — useful in CI pipelines or agent orchestration where you want the model to think hardest.
$ crush run --model "hyper/glm-5.3" --reasoning-effort "max"
— Exact flag and example command given, missing full value range.v0.94.1
thinner coverage below
0300
UI scroll performance gainsIMPROVED13how completely this was documenteddepth8/40specificity5/30actionability0/3013 / 100
The release includes performance improvements to UI scrolling, per the release summary, though no mechanism or metrics are given.
Claude Code v2.1.269 ships a new claude plugin eval command for scoring plugin eval suites, a batch of VSCode extension additions (agent map, Hooks dialog, Permission rules dialog, live subagent progress, account-switch cancel), and several new environment variables and settings covering Workflow concurrency, OpenTelemetryOpenTelemetryA CNCF open standard and SDK collection for emitting traces, metrics, and logs from applications in a vendor-neutral format, letting cyber tools ingest observability data without locking into a proprietary agent. repository tagging, gateway timeouts, and Bash-edit diffs, plus a queued-message take-back on the web.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Claude Code is Anthropic's terminal coding agent that plans, edits, and tests code in local repositories.
Claude Code v2.1.269 ships a new claude plugin eval command for scoring plugin eval suites, a batch of VSCode extension additions (agent map, Hooks dialog, Permission rules dialog, live subagent progress, account-switch cancel), and several new environment variables and settings covering Workflow concurrency, OpenTelemetryOpenTelemetryA CNCF open standard and SDK collection for emitting traces, metrics, and logs from applications in a vendor-neutral format, letting cyber tools ingest observability data without locking into a proprietary agent. repository tagging, gateway timeouts, and Bash-edit diffs, plus a queued-message take-back on the web.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
12 FEATURES12 OF 12 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
OpenTelemetry repository attribute taggingNEW81how completely this was documenteddepth25/40specificity28/30actionability28/3081 / 100
Adds OTEL_METRICS_INCLUDE_REPOSITORY to tag OpenTelemetry metrics and events with vcs.* repository attributes; commit events additionally get vcs.ref.head.* attributes when OTEL_LOG_TOOL_DETAILS is also set.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Enrich OpenTelemetry metrics with repository context so traces are filterable by branch and commit.
$ export OTEL_METRICS_INCLUDE_REPOSITORY=1
export OTEL_LOG_TOOL_DETAILS=1
claude
— Two env vars and exact attribute namespaces named with example.v2.1.269
0202
Configurable Workflow agent concurrency limitNEW80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Adds CLAUDE_CODE_WORKFLOW_MAX_CONCURRENT_AGENTS (range 1–256) to raise the Workflow tool's per-run concurrent agent limit for inference-bound fan-outs.
Allow a Workflow tool fan-out to run up to 32 agents in parallel when your workload is inference-bound.
$ export CLAUDE_CODE_WORKFLOW_MAX_CONCURRENT_AGENTS=32
claude
— Env var, numeric range, and runnable example all given.v2.1.269
0303
Plugin eval scoring commandNEW73how completely this was documenteddepth28/40specificity20/30actionability25/3073 / 100
Adds claude plugin eval to run a plugin's eval suite against Claude Code and produce scored, reproducible results in JSON and HTML report formats.
Score a plugin's eval suite to validate its prompts and agent behaviour before shipping.
$ claude plugin eval --help
claude plugin eval
— Command and two report formats named with runnable example.v2.1.269
0404
Output style switching slash commandNEW67how completely this was documenteddepth20/40specificity22/30actionability25/3067 / 100
Adds /output-style [name] slash command to list and switch output styles, including over Remote Control and in cloud and other headless sessions.
— Command syntax and session scope named, no example run.v2.1.269
0505
Extended LLM gateway discovery timeoutNEW65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
Adds CLAUDE_CODE_GATEWAY_MODEL_DISCOVERY_TIMEOUT_MS to extend the LLM gateway /v1/models discovery timeout beyond the 3s default.
— Env var and endpoint named but no usage example given.v2.1.269
0606
Agent map in VSCodeNEW65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Adds an agent map in the VSCode extension — an 'N agents' footer pill opens a map of the session's sub-agents with per-agent cards, a Stop agent action, and read-only transcripts.
— UI mechanism detailed but only a navigation path, no command.v2.1.269
0707
Hooks dialog in VSCode command menuNEW63how completely this was documenteddepth28/40specificity20/30actionability15/3063 / 100
Adds a Hooks dialog to the VSCode command menu for viewing hooks and adding, editing, or removing them in user, project, and local settings; managed, plugin, and session hooks remain read-only.
— Settings scope enumerated; UI path only, no command shown.v2.1.269
0808
Permission rules dialog in VSCodeNEW63how completely this was documenteddepth28/40specificity20/30actionability15/3063 / 100
Adds a Permission rules dialog that lists permission rules and adds or removes them in user, project, and local settings; startup-option, session-only, and managed rules remain read-only.
— Settings scope enumerated; UI path only, no command shown.v2.1.269
thinner coverage below
0909
Bash tool file-edit diff surfacingNEW58how completely this was documenteddepth20/40specificity20/30actionability18/3058 / 100
Adds bashEditDiffEnabled setting to surface a diff of files changed by a Bash command directly in the Bash tool result when the Bash tool handles file edits.
— Setting name given but no config file path or example.v2.1.269
1010
Take back queued message on the webNEW58how completely this was documenteddepth20/40specificity18/30actionability20/3058 / 100
Adds the ability to take back a queued message in a Claude Code on the web cloud session before Claude reads it: remove it from the queue, or press Esc o.
— Keybinding named; scope limited to cloud sessions.v2.1.269
1111
Live subagent progress in Focus viewNEW37how completely this was documenteddepth15/40specificity12/30actionability10/3037 / 100
Adds live progress rows for running subagents under the tool-call groups in Focus view in the VSCode extension.
— Bare description of a UI addition, no further mechanism.v2.1.269
1212
Cancel option on Switch account screenNEW35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Adds a Cancel button to the Switch account screen in the VSCode extension that returns to your session as the current account.
— Single UI control described briefly, no further scope.v2.1.269
OpenHands is an open-source software-development agent that writes code, runs commands, and browses the web.
OpenHands added OpenAI-compatible API endpoints for broader client integration and shipped several smaller improvements to automation management and the UI.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
4 FEATURES4 OF 4 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
OpenAI-compatible Chat Completions and Responses endpointsNEW60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
OpenHands now exposes its agent via OpenAI-compatible Chat Completions and Responses API endpoints, enabling it to be used from chat UIs, IDEs, voice platforms, and other OpenAI-style clients.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names the two endpoint types but not exact paths or params.product docs
thinner coverage below
0202
Cloud automation editing and identity visibilityNEW40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
Automations can now be edited on cloud backends, and the system shows which identity an automation runs as, giving operators visibility into the execution context.
— Describes two thin automation-area additions without named config or API surfaces.v1.18.0
0303
Full-size image attachment previewNEW30how completely this was documenteddepth15/40specificity5/30actionability10/3030 / 100
Users can now click an image attachment in the UI to open it at full size.
— Simple UI action described without further mechanism.v1.18.0
0404
Automation re-enable restricted to creatorBREAKING30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Re-enabling an automation is now restricted to its original creator only, tightening who can resume a disabled automation.
— States the restriction but not enforcement mechanism or scope.v1.18.0
OpenAI Codex CLI runs an agent in the terminal that reads, changes, and tests code in local repositories.
Codex CLI adds thread-scoped instructions and bundles voice support for both Linux and Windows terminals.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE1 OF 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Voice support bundled for Linux and WindowsNEW60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Bundles GNU voice helpers and runtimes into Linux musl release archives, with ALSA plugin discovery and increased capture/playback buffering for PipeWire compatibility, and bundles a Windows voice runtime into portable ZIP packages, enabling voice support on Windows.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Amp is Sourcegraph's agentic coding tool for the terminal and editor, running multi-step edits with subagents and shared team threads.
Amp introduces a Restack button that reorganizes a thread's changes into cleaner, logical commits before review.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE1 OF 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Restack button for commit reorganizationNEW55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
A new Restack button reorganizes a thread's changes into a cleaner set of commits — splitting large diffs into logical pieces, cleaning up intermediate agent commits, or combining small related commits — without altering final file contents.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
ⓘSourcesBlog / feed →1 RELEASE · 2026-08-29BLOG ↗RankWhy this ranktop features scored 85/85/75, +15 breaking change, +6 runnable example — 102.67How ranking works →
Kiro is an agentic development environment that uses spec-driven workflows to plan, build, and maintain software.
Kiro's Crew release (0.5) adds an AWS Control app for fleet-wide cloud account management, fleet-wide security policy publishing, cross-session agent coordination through a built-in conductor, persistent session tabs, and a consolidated in-process speech-to-text provider — alongside a wave of breaking changes retiring older speech providers, S3 snapshot backups, the standalone Knowledge and Auto-Triage apps, and narrowing legacy approval grants.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
22 FEATURES19 OF 22 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Secrets migration into encrypted vaultNEW85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
Adds kirocrew secrets import to move plaintext credentials from .env into the encrypted vault, leaving a secret:// reference behind; it runs as a dry run unless --apply is passed.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Safely migrate plaintext secrets out of a .env file into the encrypted vault before committing — run without --apply first to preview what will change.
Speech-to-text provider consolidationBREAKING85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
Retires the whisper, mlx parakeet, and faster speech-to-text providers in favor of a single in-process local provider that downloads its own model on first use (a 148 MB base model by default; a stored turbo setting still works but downloads 1.6 GB), enabling dictation without installing an external binary, with live text appearing as you speak and filtering of silence hallucinations and caption boilerplate. kirocrew doctor now reports stored provider defaults so users can decide which to adopt after the consolidation.
Fleet-wide security policy publishingNEW75how completely this was documenteddepth35/40specificity25/30actionability15/3075 / 100
Adds security_policy.json published from a URL so administrators can push one security policy to an entire fleet; hosts cache and refresh it without a restart, reject invalid documents, and fall back to the cached policy when the source is unavailable. A misspelled sandbox key in the file now fails validation, and a malformed publish section denies publishing instead of silently dropping restrictions.
Atomic in-place update via kirocrew updateNEW70how completely this was documenteddepth25/40specificity20/30actionability25/3070 / 100
Adds kirocrew update to install a new version into a signature-verified tree and switch to it atomically; on Windows, 'Restart & Update' shows installer progress and relaunches the new build.
Permission prompt display and bulk approval controlsNEW70how completely this was documenteddepth30/40specificity20/30actionability20/3070 / 100
kirocrew chat now displays permission prompts so users can answer approval requests directly instead of waiting silently, and approval controls let users approve or reject all waiting tool calls at once, or reject one call while continuing to review the rest; long shell commands show a readable summary with the full command available on hover.
MCP server management improvementsIMPROVED70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
MCP server health view now shows a consecutive-failure count with one-click reset; remote OAuth servers can be connected from the MCP Servers page; and enterprise Kiro accounts honor administrator-managed MCP registry controls, including version pins.
Trusted phone access via GatewayNEW70how completely this was documenteddepth30/40specificity20/30actionability20/3070 / 100
Adds phone access: one action enables trusted mobile access, restarts the Gateway, publishes through Tailscale, and shows a sign-in QR code; phone sessions survive Gateway restarts and updates.
AWS Control app for account managementNEW65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Adds the AWS Control app, a single surface to review account health, browse a versioned S3-backed drive, manage access, inspect billing, run cloud backups, and restore snapshots by replacing or merging components with a rollback ledger.
S3 snapshot backup removedBREAKING65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
kirocrew snapshot --to s3://... and the --aws-profile fetch path with s3:// are no longer available; cloud backups now go through the new AWS Control app instead.
Approval grant scope narrowedBREAKING65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Durable always-allow grants no longer cover structured non-shell tools, and commands that look like help or version checks no longer count as approval; app trust is now tied to the approved repository, so legacy grants that cannot be matched to a repository will prompt for re-consent and some commands may ask for approval again.
Persistent session tabsNEW65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Supports persistent session tabs above the transcript, openable with middle-click or modifier-click, showing live status per tab; pinned, running, and unread sessions stay always visible while dormant sessions fold behind a configurable threshold expander.
Knowledge content relocatedBREAKING60how completely this was documenteddepth20/40specificity20/30actionability20/3060 / 100
Moves Knowledge content into Agent Capabilities > Knowledge & instructions; the standalone Knowledge page is removed from the sidebar and old /knowledge links redirect there.
Cross-session agent coordinationNEW55how completely this was documenteddepth30/40specificity15/30actionability10/3055 / 100
Agents can send a message into another session as its next turn, and a built-in conductor can divide a larger goal into work items, start a session per item, check results, and decide the next round.
OAuth grant revoked on disconnectBREAKING50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Disconnecting a connection now revokes its local OAuth grant; reconnecting requires signing in again unless another agent or scope still shares the endpoint.
Auto-Triage Pipeline merged into Issue RadarBREAKING45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
The standalone Auto-Triage Pipeline app and its saved repository are retired; Auto-Triage Pipeline becomes a fourth Issue Radar board that follows the selected repository.
!The whisper, mlx parakeet, and faster speech-to-text providers are retired; saved settings fall back to the new in-process provider, which downloads the 148 MB base model on first use. A stored turbo setting still works but downloads 1.6 GB.
!Snapshot backup to S3 is removed: kirocrew snapshot --to s3://... and the --aws-profile fetch path with s3:// are no longer available. Use the AWS Control app for cloud backups.
!App trust is now tied to the approved repository; legacy grants that cannot be matched to a repository will prompt for re-consent, and some commands may ask for approval again.
!Durable always-allow grants no longer cover structured non-shell tools, and commands that look like help or version checks no longer count as approval.
!Custom bundle-path environment overrides for the Kiro CLI are removed; Kiro Crew now uses Kiro CLI's published relay.
!The standalone Knowledge page is removed from the sidebar; its content is now under Agent Capabilities > Knowledge & instructions.
!The standalone Auto-Triage Pipeline app and its saved repository are retired; its boards become a fourth Issue Radar board.
!Disconnecting a connection revokes its local OAuth grant; reconnecting requires sign-in again unless another agent or scope still shares the endpoint.
!A misspelled security_policy.json sandbox key now fails validation, and a malformed publish section denies publishing instead of silently dropping restrictions.
ⓘSourcesRelease notes →1 RELEASE · 2026-09-12NOTES ↗RankWhy this ranktop features scored 88/86/85, +15 breaking change, +6 runnable example — 107.33How ranking works →
Pipecat is a framework for realtime voice and multimodal agents, orchestrating speech-to-text, model inference, and text-to-speech as a streaming pipeline.
Pipecat v1.10.0 ships major breaking dependency upgrades (openai 3, anthropic 1, mcp 2.x), a full migration of Speechmatics STT to the Agent API, new server-side turn detection for Gradium STT, continuous TTS via Smallest AI's continuation API, LiveKit audio buffer tuning, DeepSeek reasoning/thinking fixes, and eval-suite dashboard improvements.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
10 FEATURES8 OF 10 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Gradium server-side turn detectionNEW88how completely this was documenteddepth30/40specificity28/30actionability30/3088 / 100
enable_turn_detection added to GradiumSTTService to delegate end-of-turn decisions to Gradium's server-side endpointing signal instead of the pipeline's VAD, tunable via eot_horizon_s, eot_threshold, and post_flush_cooldown_frames.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Enable Gradium's server-side turn detection so the STT service — not the pipeline VAD — decides when each user turn ends, reducing false cut-offs in noisy environments.
— Named flag and tuning params with a runnable code example.v1.10.0
0202
Speechmatics STT migrated to Agent STTBREAKING86how completely this was documenteddepth38/40specificity30/30actionability18/3086 / 100
SpeechmaticsSTTService now targets Speechmatics Agent STT (/v2/agent) via the speechmatics-agent-stt SDK, replacing speechmatics-voice[smart] in the speechmatics extra, with a new model setting defaulting to linden-1 and enable_partials replacing include_partials. Default turn_detection_mode is now TurnDetectionMode.VAD (pass TurnDetectionMode.EXTERNAL to drive turns from Pipecat's own VAD as before), and the service gains automatic reconnection with exponential backoff after dropped connections or recoverable server errors, with permanent-error reporting for rejected credentials or exhausted retries. Removed: SpeakerFocusMode, SpeakerFocusConfig, UpdateParams, update_params(), and the Settings/InputParams fields focus_speakers, ignore_speakers, focus_mode, speaker_passive_format, max_delay, end_of_utterance_silence_trigger, end_of_utterance_max_delay, split_sentences, include_results, and extra_params, plus TurnDetectionMode.FIXED, TurnDetectionMode.ADAPTIVE, and TurnDetectionMode.SMART_TURN; OperatingPoint is replaced by Model.
— Extensive named surfaces and mechanism, but no runnable usage example.v1.10.0
0303
openai 3 SDK supportBREAKING85how completely this was documenteddepth35/40specificity28/30actionability22/3085 / 100
The openai dependency is widened to >=1.74.0,<4 to support the openai 3 SDK, which uses httpx2 instead of httpx for HTTP and verifies TLS against the OS trust store rather than certifi. Container images without system CA certificates and TLS-inspecting proxy environments may need SSL_CERT_FILE or SSL_CERT_DIR set; a Timeout passed to OpenAITTSService or Whisper-based STT services must come from httpx2 on openai 3, or httpx on older versions. Pin openai<3 to stay on the previous HTTP stack.
— Names exact dependency bounds and migration remedy but no code sample.v1.10.0
0404
Continuous TTS via Smallest AI continuation APINEW81how completely this was documenteddepth28/40specificity25/30actionability28/3081 / 100
max_buffer_delay_ms added to SmallestTTSService to control the server-side buffering window for Smallest AI's continuation API, which joins text fragments within the same LLM turn under a shared context_id for unbroken prosody.
Use Smallest AI's continuation API with a 200 ms server buffer so fragments in the same LLM turn are joined into one continuous utterance instead of resetting prosody on each chunk.
— Named config key and mechanism with runnable code example.v1.10.0
0505
anthropic 1 SDK supportBREAKING71how completely this was documenteddepth28/40specificity25/30actionability18/3071 / 100
The anthropic dependency is widened to >=0.49.0,<2 to support the anthropic 1 SDK; AnthropicLLMService now routes temperature, top_k, and top_p through extra_body. If a Bedrock client is passed, anthropic 1 requires an explicit region via AsyncAnthropicBedrock(aws_region=...) or the AWS_REGION environment variable, where it previously defaulted to us-east-1.
— Named config surfaces and default change, no runnable example.v1.10.0
0600
Eval suite dashboard and recording statusIMPROVED70how completely this was documenteddepth28/40specificity24/30actionability18/3070 / 100
The pipecat eval suite live dashboard now shows pass rate for in-progress repeated (bot, scenario) rows and replaces the yellow middle band with green (all passed) / red (one failed) colouring. The recording line in pipecat eval suite settings reports which runs will actually record, e.g. on (3 of 6 runs; text mode skipped) or off (all runs text mode); pipecat eval run -a prints the same line.
— Names the exact CLI commands and output strings, no code example.v1.10.0
0706
DeepSeek reasoning content and thinking defaultsBREAKING67how completely this was documenteddepth25/40specificity22/30actionability20/3067 / 100
DeepSeekLLMAdapter supplies reasoning_content on assistant messages when tool calls are in the conversation, fixing requests in thinking mode. DeepSeekLLMService now defaults thinking to disabled; pass thinking=DeepSeekLLMService.ThinkingConfig(type='enabled') to enable it or thinking=None to use DeepSeek's own default.
— Names the adapter, fix, and default change but no example.v1.10.0
0807
LiveKit outgoing audio buffer controlNEW65how completely this was documenteddepth20/40specificity20/30actionability25/3065 / 100
LiveKitParams.audio_out_queue_size_ms configures the outgoing rtc.AudioSource buffer size, defaulting to LiveKit's 1000 ms.
Increase the LiveKit outgoing audio buffer to reduce underruns on high-jitter networks without changing any other pipeline settings.
— Named config field with default and a runnable example.v1.10.0
thinner coverage below
0900
MCP SDK 2.x compatibilityIMPROVED43how completely this was documenteddepth15/40specificity18/30actionability10/3043 / 100
The mcp dependency is widened to mcp[cli]>=1.24.0,<3 so MCPClient works with MCP SDK 2.x as well as 1.x.
— Bare dependency bound with no further mechanism or example.v1.10.0
1008
LmntTTSService removedDEPRECATED30how completely this was documenteddepth10/40specificity12/30actionability8/3030 / 100
LmntTTSService is removed because LMNT has shut down.
— One-line removal notice with no migration path given.v1.10.0
└──▷ BREAKING ON UPGRADE
!The openai dependency now resolves to openai 3 by default (>=1.74.0,<4), which uses httpx2 instead of httpx for HTTP and verifies TLS against the OS trust store rather than certifi. Container images without system CA certificates and TLS-inspecting proxy environments may need SSL_CERT_FILE or SSL_CERT_DIR set. A Timeout passed to OpenAITTSService or Whisper-based STT services must come from httpx2 on openai 3, or from httpx on older versions. Pin openai<3 to stay on the previous HTTP stack.
!SpeechmaticsSTTService now targets Speechmatics Agent STT (/v2/agent) via speechmatics-agent-stt (replaces speechmatics-voice[smart] in the speechmatics extra) and cannot connect to the legacy real-time endpoint.
!SpeechmaticsSTTService default turn_detection_mode is now TurnDetectionMode.VAD; pass turn_detection_mode=TurnDetectionMode.EXTERNAL to drive turns from Pipecat's own VAD as before.
!SpeechmaticsSTTService renames Settings.include_partials to enable_partials.
!SpeechmaticsSTTService removes SpeakerFocusMode, SpeakerFocusConfig, UpdateParams, update_params(), and the Settings/InputParams fields focus_speakers, ignore_speakers, focus_mode, speaker_passive_format, max_delay, end_of_utterance_silence_trigger, end_of_utterance_max_delay, split_sentences, include_results, and extra_params, as well as TurnDetectionMode.FIXED, TurnDetectionMode.ADAPTIVE, and TurnDetectionMode.SMART_TURN. OperatingPoint is replaced by Model.
!LmntTTSService is removed; LMNT has shut down.
!The anthropic dependency now resolves to anthropic 1 (>=0.49.0,<2). If you pass a Bedrock client, anthropic 1 requires an explicit region via AsyncAnthropicBedrock(aws_region=...) or the AWS_REGION environment variable, where it previously defaulted to us-east-1.
PydanticAI's biggest addition is capabilities, a composable extension system bundling tools, hooks, instructions, and model settings into reusable units, shipped alongside dozens of built-in Core and Harness capabilities spanning provider-native search/thinking, sandboxed execution, memory, guardrails, durable execution and more; clai also picked up a first-run session banner.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
PydanticAI is a framework that builds type-safe Python agents with dependency injection, model integrations, tools, and structured outputs.
PydanticAI's biggest addition is capabilities, a composable extension system bundling tools, hooks, instructions, and model settings into reusable units, shipped alongside dozens of built-in Core and Harness capabilities spanning provider-native search/thinking, sandboxed execution, memory, guardrails, durable execution and more; clai also picked up a first-run session banner.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
25 FEATURES24 OF 25 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Capabilities: composable agent extension systemNEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Adds the capabilities parameter to Agent (and AgentSpec) for composing reusable units of agent behavior — tools, lifecycle hooks, instructions, model settings, and model selection — in a single import.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The Capability class declaratively bundles instructions, function tools, and toolsets without subclassing, using decorators like @refunds.tool_plain to attach tools; defer_loading=True collapses a bundle to a catalog entry until the model loads it. AbstractCapability supports subclassing for behavior beyond instructions/tools/toolsets, CapabilityEvent (with a namespace argument and ctx.emit()) provides typed event publication, and the Toolset convenience class wraps an AbstractToolset as an authoring primitive.
Equip a research agent with deep thinking and web search in one capabilities list — useful when you want thorough, cited answers without threading model settings and tool registrations separately.
python
from pydantic_ai import Agent
from pydantic_ai.capabilities import Thinking, WebSearch
agent = Agent(
'anthropic:claude-fable-5',
instructions='You are a research assistant. Be thorough and cite sources.',
capabilities=[
Thinking(effort='high'),
WebSearch(local='duckduckgo'),
],
)
Bundle a refund skill — instructions plus a tool — into a named Capability so the same unit can be reused across multiple agents without duplication.
python
from pydantic_ai import Agent
from pydantic_ai.capabilities import Capability
refunds = Capability(
id='refunds',
description='Use for refund eligibility and refund status.',
instructions='Always confirm the order ID before issuing a refund.',
)
@refunds.tool_plain
def refund_status(order_id: str) -> str:
"""Look up the refund status for an order."""
return f'Order {order_id}: refund issued on 2026-05-01.'
agent = Agent('openai:gpt-5.6-sol', capabilities=[refunds])
Emit a typed CapabilityEvent from a capability-contributed tool so other capabilities and observability pipelines can react to file writes without polling.
python
from dataclasses import dataclass
from typing import Any
from pydantic_ai import CapabilityEvent, RunContext
from pydantic_ai.capabilities import AbstractCapability
from pydantic_ai.toolsets import AgentToolset, FunctionToolset
WORKSPACE = 'workspace'
@dataclass(kw_only=True)
class FileWriteEvent(CapabilityEvent, namespace=WORKSPACE):
path: str
bytes_written: int
workspace = FunctionToolset()
@workspace.tool
async def write_file(ctx: RunContext[Any], path: str, content: str) -> str:
await ctx.emit(FileWriteEvent(path=path, bytes_written=len(content)))
return f'Wrote {path}'
— Runnable code examples plus every named class and flagproduct docs
0202
StepPersistence for resumable and forkable runsNEW73how completely this was documenteddepth30/40specificity28/30actionability15/3073 / 100
StepPersistence saves, restores, resumes via continue_run, and forks via fork_run runs, with file, SQLite, and Mongo backends.
— Names two runnable functions and three storage backendsproduct docs
0303
Provider-native model capabilities: search, thinking, imagesNEW68how completely this was documenteddepth25/40specificity28/30actionability15/3068 / 100
Adds Thinking for provider-adaptive extended thinking at configurable effort; WebSearch for provider-native search with a local fallback (e.g. local='duckduckgo'); WebFetch for fetching and reading URLs, native or local; XSearch for searching X with a subagent fallback on non-xAI providers; MCP to connect any MCP server's tools with opt-in provider-native connectors; ImageGeneration for generating and editing images, provider-native where supported with a direct image-model fallback; and NativeTool to register any provider-native tool with the agent.
— Names each capability and its parameters, no runnable exampleproduct docs
0404
Tool definition and execution controlsNEW65how completely this was documenteddepth25/40specificity28/30actionability12/3065 / 100
Adds ToolSearch for loading tool definitions on demand instead of carrying all definitions in every prompt; ToolApproval for flagging tool calls that require human approval before execution; HandleDeferredToolCalls for programmatically resolving approval-deferred tool calls; PrepareTools / PrepareOutputTools for filtering or modifying tool definitions per step; PrefixTools to wrap another capability and prefix its tool names; IncludeToolReturnSchemas to include return type schemas in tool definitions sent to the model; SetToolMetadata to merge metadata key-value pairs onto selected tools; and ThreadExecutor for running sync tools on a shared thread pool.
— Eight named capabilities, mechanism per one but no exampleproduct docs
0505
Harness Compaction with model-agnostic strategiesNEW65how completely this was documenteddepth30/40specificity25/30actionability10/3065 / 100
Compaction (Harness) provides model-agnostic compaction strategies — tool-result clearing, sliding-window trimming, LLM summarization, and tiered — all window-relative with live usage reporting.
— Names four strategies with behaviour, no exampleproduct docs
0606
Sub-agent orchestration capabilitiesNEW64how completely this was documenteddepth26/40specificity26/30actionability12/3064 / 100
Adds Planning for model-owned task plans with a cache-safe live reminder; Subagents for delegating self-contained tasks to named child agents; DynamicWorkflow for model-orchestrated sub-agents with fan-out, chain, and vote patterns in a single tool call, enforced by hard max_agent_calls budgets; and Advisor for letting an executor consult a stronger model mid-run.
— Names the `max_agent_calls` budget and orchestration patternsproduct docs
0707
CodeMode capability for batched tool calls via sandboxed scriptNEW64how completely this was documenteddepth30/40specificity24/30actionability10/3064 / 100
CodeMode lets the model write one Python script calling many tools inside a Monty sandbox, reducing round-trips and keeping intermediate results out of the context window.
— Clear before/after mechanism, no runnable exampleproduct docs
0808
Agent memory and history search capabilitiesNEW64how completely this was documenteddepth28/40specificity26/30actionability10/3064 / 100
Adds Memory providing a persistent, namespaced notebook with bounded prompt injection, on-demand search, and in-memory, file, or Postgres stores; and ConversationSearch for BM25 search over stored history including turns compaction dropped.
— Names storage backends and search algorithm, no exampleproduct docs
0909
Model selection and lifecycle processing capabilitiesNEW62how completely this was documenteddepth24/40specificity26/30actionability12/3062 / 100
Adds SelectModel for static or per-step model selection via a callable; ResolveModelID for resolving custom application-specific model IDs via a callable; Hooks for decorator-based lifecycle hook registration; ProcessHistory to wrap a history processor; ProcessEventStream to forward agent stream events to a handler function; and RaiseContentFilterError to raise ContentFilterError whenever a model response has finish_reason='content_filter'.
— Six named capabilities with mechanism, no usage exampleproduct docs
1010
Observability and durable execution capabilitiesNEW60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
Adds Instrumentation for OpenTelemetry GenAI spans covering every model and tool call; Compaction for provider-native context compaction on OpenAI and Anthropic; and DurableExecution for runs that survive restarts and failures on Temporal, DBOS, Prefect, Restate, Kitaru, and Airflow.
— Names concrete platforms and telemetry standard, no exampleproduct docs
thinner coverage below
1111
Sandboxed environments and third-party integrationsNEW58how completely this was documenteddepth22/40specificity26/30actionability10/3058 / 100
Adds ModalSandbox for commands and files in an isolated Modal cloud sandbox; StackOne for acting on linked SaaS accounts (HRIS, ATS, CRM) via StackOne; LocalStack for an emulated AWS environment with AWS CLI tools; and Macroscope for running a local Macroscope code review and handing findings to the agent.
— Four named integrations, mechanism per one, no exampleproduct docs
1212
On-demand context loading capabilitiesNEW58how completely this was documenteddepth22/40specificity26/30actionability10/3058 / 100
Adds Skills for loading AgentSkill (SKILL.md) instructions on demand; RepoContext for starting runs oriented with AGENTS.md / CLAUDE.md plus repository structure; and PydanticAIDocs for on-demand Pydantic AI documentation lookup.
— Three named capabilities citing exact file conventionsproduct docs
1313
Guardrails capability for input and output validationNEW58how completely this was documenteddepth28/40specificity20/30actionability10/3058 / 100
Guardrails validates, blocks, or redacts user input, tool calls, tool results, and output, including secret masking and parallel async guards.
— Lists scope and mechanism, no example or config keyproduct docs
1414
FileSystem capability for sandboxed file accessNEW57how completely this was documenteddepth25/40specificity22/30actionability10/3057 / 100
FileSystem allows reading, writing, editing, and searching files under a root, with path-traversal and symlink safety and secrets read-only access.
— Names safety mechanisms but no runnable exampleproduct docs
1515
Shell capability for controlled command executionNEW57how completely this was documenteddepth25/40specificity22/30actionability10/3057 / 100
Shell executes commands with allowlists, denylists, timeouts, and credential-stripping.
— Names controls but no config keys or example shownproduct docs
1616
SpendLimits capability for cross-window cost budgetsNEW57how completely this was documenteddepth25/40specificity22/30actionability10/3057 / 100
SpendLimits enforces cross-window USD/token budgets and per-response cost tracking, per model and per tenant.
— Names budget dimensions but no config or exampleproduct docs
1717
Web research and browsing sub-agent capabilitiesNEW54how completely this was documenteddepth22/40specificity22/30actionability10/3054 / 100
Adds ExaSearch for web research via Exa with excerpted search, full-page reads, and opt-in cited deep search; ExaAgent for delegating open-ended research to the Exa Agent API; and BrowserUse for handing web tasks to an autonomous browser-use agent driving a real browser.
— Three named delegated-research capabilities, no exampleproduct docs
1818
Tool output and prompt-cache managementNEW54how completely this was documenteddepth22/40specificity22/30actionability10/3054 / 100
Adds ToolOutputLimits for truncating, spilling to a queryable file, or summarizing oversized tool returns at the source; and WarnOnCacheBusts for detecting prompt-cache prefix collapses between requests using provider-reported numbers.
— Two named capabilities with mechanism, no exampleproduct docs
1919
ManagedPrompt for Logfire-backed instructionsNEW54how completely this was documenteddepth24/40specificity20/30actionability10/3054 / 100
ManagedPrompt backs instructions with a Logfire-managed prompt, enabling versioning and rollout without redeployment.
— Names the mechanism and benefit, no config exampleproduct docs
2020
CapabilityCreation for agent-authored capabilitiesNEW50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
CapabilityCreation allows the agent to write, validate, and persist new capabilities during a run, loaded on the next run.
— Clear behaviour described, no example of the flowproduct docs
2121
CoderHarness complete coding-agent stackNEW46how completely this was documenteddepth20/40specificity18/30actionability8/3046 / 100
CoderHarness bundles a complete coding-agent stack including files, shell, repo context, planning, a read-only explorer sub-agent, and context controls.
— Lists components but no mechanism detail or exampleproduct docs
2222
ResearcherHarness complete web-research stackNEW46how completely this was documenteddepth20/40specificity18/30actionability8/3046 / 100
ResearcherHarness bundles a complete web-research stack including search, page fetching, a delegated sub-researcher, and bounded tool output.
— Lists components but no mechanism detail or exampleproduct docs
2323
ACP for serving agents over Agent Client ProtocolNEW46how completely this was documenteddepth18/40specificity20/30actionability8/3046 / 100
ACP (experimental) serves any agent to editors like Zed over the Agent Client Protocol.
— Names protocol and target editor, marked experimentalproduct docs
2424
SystemReminders capability for guidance re-injectionNEW35how completely this was documenteddepth18/40specificity12/30actionability5/3035 / 100
SystemReminders provides cache-safe re-injection of guidance mid-run to counter instruction fade.
— One-line description with no mechanism detailproduct docs
2500
First-run banner in clai sessionsIMPROVED30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
clai interactive sessions now open with a first-run banner that describes the current run.
— Bare description, no configuration or example givenv2.43.0
ⓘSourcesRelease notes →1 RELEASE · 2026-09-11NOTES ↗RankWhy this ranktop features scored 95/90/85, +15 breaking change, +6 runnable example — 111How ranking works →
DSPy builds language-model pipelines and optimizes their prompts and weights.
DSPy 3.4.0b1 introduces a pluggable native LM engine interface built on a new typed dspy.lm15 module, a local CPython interpreter for code-executing agents, async support in ReActV2, and a GEPA code proposer, alongside a set of breaking changes that remove the experimental typed-LM API and alter ReActV2 and multi-answer behavior.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
8 FEATURES8 OF 8 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Custom LM engine interface via dspy.lm15NEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Adds engine= parameter to dspy.LM(...) accepting 'auto', 'litellm', 'lm15', or a custom engine object implementing complete(Request) -> Response, plus async_engine= for async calls, enabling custom backends without subclassing BaseLM.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Also adds the dspy.lm15 module exporting Request, Response, Message, Config, and Usage types for constructing explicit typed LM calls, with response.text and response.message.parts for accessing results.
Plug in a custom LM backend — e.g. a local model server — without subclassing BaseLM, while letting DSPy handle caching, retries, and history.
python
from dspy.lm15 import Message, Response, Usage
import dspy
class MyEngine:
def complete(self, request):
# call your own backend here
text = my_model_server.generate(request.messages[-1].text)
return Response(
id=None,
model=request.model,
message=Message.assistant(text),
finish_reason='stop',
usage=Usage(),
)
lm = dspy.LM('custom/my-model', engine=MyEngine())
dspy.configure(lm=lm)
Send an explicit typed request to get a structured response with usage metadata, bypassing DSPy's signature machinery.
python
import dspy
from dspy.lm15 import Config, Message, Request
lm = dspy.LM('openai/gpt-4o-mini')
response = lm(Request(
model=lm.model,
system='Be concise.',
messages=(Message.user('Summarize zero-trust networking in one sentence.'),),
config=Config(max_tokens=100),
))
print(response.text)
— Names the exact params, types, and shows runnable code3.4.0b1
0202
Removal of experimental typed LM classesBREAKING90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
dspy.LMRequest, dspy.LMResponse, dspy.LMMessage, dspy.LMConfig, dspy.System, dspy.User, and dspy.Assistant are removed; importing dspy.core.types raises a migration error, and forward_contract='typed_lm' is rejected. The dspy.clients.openai_format module is also removed, and experimental=True no longer changes ordinary LM calls into typed responses. Migrate to dspy.lm15.Request, dspy.lm15.Response, dspy.lm15.Message, dspy.lm15.Config, Message.user(text), and Message.assistant(text); old pickles containing the removed 3.3 classes must be loaded and exported in their original environment before upgrading.
— Enumerates every removed surface and gives migration path3.4.0b1
0303
LocalInterpreter for RLM and Flex code executionNEW85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
Adds dspy.LocalInterpreter as an interpreter_factory= option for dspy.RLM and Flex, running generated Python in a persistent local CPython subprocess with execution_timeout support, without requiring Deno.
Run a code-executing RLM agent using the host Python environment instead of Deno, suitable for trusted internal tooling.
python
import dspy
rlm = dspy.RLM(
'question: str -> answer: int',
interpreter_factory=dspy.LocalInterpreter,
)
result = rlm(question='What is 17 * 42?')
print(result.answer)
— Named config option with runnable example, mechanism given3.4.0b1
0404
Async agent execution in ReActV2NEW75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
Adds await agent.acall(...) support to dspy.ReActV2, enabling async prediction, async tools, and async MCP tool execution with structured tool-call history preserving call IDs and tool results across turns.
— Names method and mechanism but no runnable example given3.4.0b1
0505
ReActV2 signature and async-tool restrictionsBREAKING75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
dspy.ReActV2 rejects signatures with output fields named history or termination_reason; rename those outputs before upgrading. Calling an async tool synchronously from a running event loop raises a ValueError even with allow_tool_async_sync_conversion enabled; use await tool.acall(...) instead.
— Names the rejected fields, flag, and required fix3.4.0b1
0606
Custom code proposer for GEPANEW70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds code_proposer= parameter to dspy.GEPA, complementing the existing instruction_proposer=, allowing custom Flex code-generation constraints and domain guidance without monkeypatching the built-in proposer.
— Names the parameter and its purpose, no usage example3.4.0b1
0707
Native n answers use sequential requestsBREAKING70how completely this was documenteddepth30/40specificity20/30actionability20/3070 / 100
Native n answers now use separate sequential requests instead of a single provider-native multi-answer request, which can increase latency and bill input tokens more than once; use engine='litellm' to retain the previous behavior.
— Explains before/after behavior and gives a workaround flag3.4.0b1
thinner coverage below
0808
Pydantic 2.11.0 minimum versionBREAKING20how completely this was documenteddepth5/40specificity10/30actionability5/3020 / 100
Pydantic 2.11.0 is now the minimum supported version.
!dspy.LMRequest, dspy.LMResponse, dspy.LMMessage, dspy.LMConfig, dspy.System, dspy.User, and dspy.Assistant are removed; importing dspy.core.types raises a migration error, and forward_contract='typed_lm' is rejected. Migrate to dspy.lm15.Request, dspy.lm15.Response, dspy.lm15.Message, dspy.lm15.Config, Message.user(text), and Message.assistant(text).
!Old pickles containing the removed experimental 3.3 classes are not automatically migrated; load and export them in their original environment before upgrading.
!experimental=True no longer changes ordinary LM calls into typed responses.
!Pydantic 2.11.0 is now the minimum supported version.
!dspy.ReActV2 rejects signatures with output fields named history or termination_reason; rename those outputs before upgrading.
!Calling an async tool synchronously from a running event loop raises a ValueError even with allow_tool_async_sync_conversion enabled; use await tool.acall(...) instead.
!The dspy.clients.openai_format module is removed; custom adapters must not depend on it.
!Native n answers now use separate sequential requests instead of a single provider-native multi-answer request, which can increase latency and bill input tokens more than once; use engine='litellm' to retain the previous behavior.
OpenBot's v0.0.9 release focuses on hardening setup and secrets handling — installing container engines automatically, moving credentials off .env into platform-native stores, and adding a script to sweep abandoned staged attachments — alongside new multi-file message attachments and support for keyless local model endpoints.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
OpenBot runs self-hosted AI coworkers that each get their own browser, files, and gated tools, with every action decided and recorded.
OpenBot's v0.0.9 release focuses on hardening setup and secrets handling — installing container engines automatically, moving credentials off .env into platform-native stores, and adding a script to sweep abandoned staged attachments — alongside new multi-file message attachments and support for keyless local model endpoints.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
8 FEATURES5 OF 8 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Attachment sweep script for staged uploadsNEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds bun scripts/cull-staged-attachments.ts (run from /app/server) to sweep unsent staged attachments older than one day, requiring only DATABASE_URL; accepts an optional retention-window argument to change the cutoff.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Run a one-pass attachment sweep from an external cron to prevent users hitting the 32-file staged limit — only DATABASE_URL is needed.
$ DATABASE_URL=postgres://user:pass@host:5432/openbot bun scripts/cull-staged-attachments.ts 86400
— Names exact script path, required env var, and gives a runnable commandv0.0.9
0202
Multi-file message attachmentsNEW70how completely this was documenteddepth30/40specificity30/30actionability10/3070 / 100
Messages can now include up to eight file attachments: images (PNG, JPEG, GIF, WebP) up to 8 MiB and text files (plain text, Markdown, CSV, JSON) up to 1 MiB. Files are uploaded at staging time so sends are immediate and failures preserve the attachments.
— Concrete limits and formats given but no config or command to invokev0.0.9
0303
Keyless local model endpoint supportNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Supports connecting to keyless endpoints — Ollama, vLLM, LM Studio, llama.cpp — by requiring only a base URL and model name when no API key applies.
— Names four supported backends and the two config fields neededv0.0.9
0400
Credentials moved to platform credential storeIMPROVED65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Credentials (model keys, plan tokens, inter-service tokens) are now stored in the platform credential store — macOS login Keychain, Windows DPAPI, or an owner-only file on Linux — rather than in .env.
— Names each platform mechanism and what it replacesv0.0.9
0504
Automatic container engine installation during setupNEW60how completely this was documenteddepth30/40specificity20/30actionability10/3060 / 100
Setup now automatically installs a container engine (Podman or Docker) and a Compose implementation when neither is present, pinned to a tested digest and verified before execution.
— Describes pinning and verification mechanism but is automatic, not user-drivenv0.0.9
thinner coverage below
0605
AGENT_BOT_MODEL env var for bundled BotNEW50how completely this was documenteddepth15/40specificity20/30actionability15/3050 / 100
The bundled Bot now reads AGENT_BOT_MODEL so a locally-chosen model name reaches the container.
— Names the env var but gives no further mechanismv0.0.9
0700
Setup verification step and clipboard paste supportIMPROVED45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Setup now ends with a live question-and-answer verification step to confirm the model key, plan, and Bot are functional before handover, and an Edit menu was added to the setup window so clipboard paste works on screens whose instruction is to paste a code.
— Two thin UX fixes to the same setup window, no deeper mechanism givenv0.0.9
0800
Subscription-based Bot vendor re-pointingIMPROVED45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
A subscription now re-points the Bot to the vendor that can spend it, and the model screen names the resulting Bot before the screen is dismissed.
— Explains behaviour but not the underlying routing mechanismv0.0.9
Hermes's biggest addition this window is a password-blind credential vault that lets the agent sign in, pay, and fill forms using 1Password, Bitwarden, or a local Hermes vault without exposing secrets to the model, alongside a free Nous inference tier activated via /login, a reworked plugin system, and a wide set of new configuration keys covering Fast Mode, budget warnings, SSH handling, config backups, and update checks.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
A terminal-native, self-improving AI agent for autonomous coding and tasks, with persistent memory, agent-created skills, and a multi-platform messaging gateway.
Hermes's biggest addition this window is a password-blind credential vault that lets the agent sign in, pay, and fill forms using 1Password, Bitwarden, or a local Hermes vault without exposing secrets to the model, alongside a free Nous inference tier activated via /login, a reworked plugin system, and a wide set of new configuration keys covering Fast Mode, budget warnings, SSH handling, config backups, and update checks.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
15 FEATURES15 OF 15 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Manual update checkNEW75how completely this was documenteddepth20/40specificity25/30actionability30/3075 / 100
Adds hermes update --check CLI command and 'Check for Updates…' / Settings → About → 'Check now' UI paths to bypass the 24-hour passive update-check cache.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Force Hermes to check for updates immediately without waiting for the 24-hour passive cache window.
$ hermes update --check
— Runnable command and exact UI navigation givenproduct docs
0202
Iteration budget warning checkpointNEW70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds agent.budget_warning_ratio config key to append a model-visible checkpoint notice after a configurable fraction of the iteration budget is consumed, with Kanban dispatcher workers defaulting to a 90% threshold.
— Names config key, default value, and affected componentproduct docs
0303
Config backups before setup and migrationNEW70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds automatic point-in-time config backups to backups/config/config.yaml.<reason>.<timestamp> before hermes setup, hermes migrate, or on parse failure, keeping at most the newest five per reason.
— Exact path pattern, triggers, and retention count givenproduct docs
0404
Docker Snap compatibility modeNEW70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds docker_snap_compat config key to drop --init and --security-opt no-new-privileges for snap-packaged Docker on Ubuntu/Azure hosts where AppArmor confinement would otherwise kill the container.
— Names key, flags removed, and the exact failure it avoidsproduct docs
0505
SSH environment passthrough for skill variablesNEW70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds terminal.env_passthrough config key to forward skill-declared variables to remote SSH sessions via OpenSSH SendEnv; provider credentials are never forwarded even if listed.
— Names key, mechanism, and the credential exclusion safeguardproduct docs
0606
Fast Mode slash commandNEW70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
Adds /fast normal|fast|auto|cold slash command to switch Fast Mode priority processing for the current session, with a --persist flag to save the choice.
— Exact command syntax and flag givenproduct docs
0707
Password-blind credential vaultNEW65how completely this was documenteddepth30/40specificity25/30actionability10/3065 / 100
The agent can now sign in, pay, and fill addresses using credentials from 1Password, Bitwarden, or the local Hermes vault without exposing secrets to the model itself; two-factor codes are supplied from a saved authenticator key or prompted in the user's UI. Private git plugins can also now install using stored vault credentials.
— Clear mechanism and named providers but no exact command shownv2026.9.11
0808
Context file read timeoutNEW65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
Adds context_file_read_timeout config key (default unspecified seconds) to skip slow network-backed context files such as iCloud Drive, OneDrive, or NFS rather than stalling the system prompt load.
— Names key and affected services, default value missingproduct docs
0909
Plugin system: curated catalog and desktop UINEW60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Adds a curated, SHA-pinned plugin catalog with CLI, admission CI, docs, and a dashboard view. Desktop now has a single Plugins page covering agent and desktop plugins, install, catalog, and per-commit pinning. Radio ships as an opt-in SDK plugin.
— Names catalog and UI surfaces but no exact commandsv2026.9.11
1010
Free Nous tier via /login commandNEW60how completely this was documenteddepth20/40specificity15/30actionability25/3060 / 100
Adds /login to sign in to a Nous account directly from a chat session, which activates free Nous inference and connectors out of the box with one sign-in command.
— Names exact command but activation detail is thinv2026.9.11
1111
Custom Git SSH command supportNEW60how completely this was documenteddepth20/40specificity20/30actionability20/3060 / 100
Adds GIT_SSH_COMMAND environment variable support for internal Git operations, taking precedence over Hermes's default ssh -o BatchMode=yes for custom identity or transport commands.
— Names env var and the default it overridesproduct docs
thinner coverage below
1212
Connector tool searchNEW55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Adds tool_search to make connector tools such as Gmail, Linear, Notion, and others discoverable without needing to know their exact names.
— Names the feature and examples but no usage syntaxv2026.9.11
1313
Verification evidence ledgerNEW55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Stores verification evidence in ~/.hermes/verification_evidence.db; the ledger is only written while verify_on_stop is enabled.
— Names storage path and enabling condition, no usage detailproduct docs
1414
Guided first-launch onboardingNEW50how completely this was documenteddepth15/40specificity15/30actionability20/3050 / 100
Adds HERMES_GUEST_ONBOARDING=1 environment variable to enable a guided first-launch experience for new users.
— Exact env var given but behaviour barely describedv2026.9.11
1515
Per-profile environment variable isolationNEW45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Introduces per-profile environment variable isolation under the multiplexed multi-platform messaging gateway: ${VAR} references in a profile resolve only against that profile's own secret scope, not the shared process environment.
— Explains the isolation mechanism but no config path shownproduct docs
└──▷ ALSO FROM THESE RELEASES
Work around a vLLM tool-call parser that leaks markup into plain text, causing delegated tasks to silently no-op.
The Vercel AI SDK provides TypeScript APIs for model generation, structured output, tool use, and streaming application interfaces.
Vercel AI SDK 7.0.98 extends embedding and reranking with runtime context attribution, adds batch image generation, and introduces a stable UI message type for tool output errors.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
3 FEATURES3 OF 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Runtime context attribution for embed and rerankNEW45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
Adds runtime context attribution support to the embed, embedMany, and rerank functions, allowing context to be tracked through these calls.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names three functions but no schema or usage shown[email protected]
0202
Batch image generation requestsNEW23how completely this was documenteddepth10/40specificity8/30actionability5/3023 / 100
Image generation now supports submitting requests in batches.
LangChain is an open-source framework that orchestrates applications powered by language models.
langchain-core 1.6.3 adds the ability for gateway responses to override model name and provider fields in tracing metadata, improving trace attribution when requests pass through a proxy.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE1 OF 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Gateway override of tracing model metadataIMPROVED45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
When a proxy or gateway sits in front of the underlying model, langchain-core can now use the gateway response's model name and provider values to override tracing metadata, giving accurate attribution in traces.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Explains mechanism and purpose but no config key or flag namedlangchain-core==1.6.3
Agent Framework .NET 1.21.0 ships several breaking changes—moving the line-numbering contract onto AgentFileStore, clarifying A2A run modes, and restricting MCPMCPModel Context Protocol, an open standard from Anthropic that lets an AI model call external tools and data sources through a uniform interface, so developers avoid writing custom integrations for every service. skill archives to ZIP—alongside hosted-response improvements, sandbox hardening for LocalCodeAct and HyperlightHyperlightA Microsoft-maintained Rust library for running small, sandboxed WebAssembly or native binaries inside lightweight micro-VMs, giving cyber tools fast, isolated execution without a full hypervisor stack., and dependency upgrades for Azure.AI.Projects and AWS Bedrock.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
The Microsoft Agent Framework builds, orchestrates, and deploys agents and multi-agent workflows in Python and .NET, consolidating AutoGen and Semantic Kernel.
Agent Framework .NET 1.21.0 ships several breaking changes—moving the line-numbering contract onto AgentFileStore, clarifying A2A run modes, and restricting MCPMCPModel Context Protocol, an open standard from Anthropic that lets an AI model call external tools and data sources through a uniform interface, so developers avoid writing custom integrations for every service. skill archives to ZIP—alongside hosted-response improvements, sandbox hardening for LocalCodeAct and HyperlightHyperlightA Microsoft-maintained Rust library for running small, sandboxed WebAssembly or native binaries inside lightweight micro-VMs, giving cyber tools fast, isolated execution without a full hypervisor stack., and dependency upgrades for Azure.AI.Projects and AWS Bedrock.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
6 FEATURES3 OF 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Line-numbering moved onto AgentFileStoreBREAKING70how completely this was documenteddepth25/40specificity20/30actionability25/3070 / 100
Adds file_access_read_lines to AgentFileStore, moving the line-numbering contract onto the store itself; callers that previously handled line numbering outside the store must migrate to the new contract.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names the exact method and breaking migration but no code sampledotnet-1.21.0
thinner coverage below
0200
Dependency upgrades for Azure and AWS integrationsIMPROVED55how completely this was documenteddepth15/40specificity25/30actionability15/3055 / 100
Upgrades the Azure.AI.Projects dependency to 3.0.0-beta.2, and switches the AWS Bedrock integration from the deprecated AWSSDK.Extensions.Bedrock.MEAI package to AWS.Bedrock.MEAI.
— Names exact package versions, a clear upgrade pathdotnet-1.21.0
0302
A2A task-state tracking and run-mode clarificationBREAKING50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Tracks and updates A2A task state across agent runs, and clarifies A2A agent run modes via a breaking API change — existing A2A agent configurations must be updated to match the new run-mode contract.
— Migration is flagged but no concrete config keys showndotnet-1.21.0
0400
Sandbox hardening for LocalCodeAct and HyperlightIMPROVED50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Isolates the LocalCodeAct subprocess environment for sandboxed code execution, hardens LocalCodeAct OS validation, and implements the same approval process for LocalCodeAct as used by Hyperlight; also canonicalizes Hyperlight sandbox fingerprints.
— Names both sandbox components but mechanism details are briefdotnet-1.21.0
0500
Hosted agent response handling improvementsIMPROVED45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Opts in to client function forwarding for Responses hosting, enabling hosted agents to invoke client-side functions; scopes OpenAI hosting storage by isolation key; and preserves streamed annotations in Foundry hosted responses.
— Describes three hosting behaviours but no config or API namesdotnet-1.21.0
0603
MCP skill archives restricted to ZIPBREAKING40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Limits MCP skill archives to the ZIP format only; any non-ZIP archive that was previously accepted will now be rejected.
— Clear before/after but no migration steps givendotnet-1.21.0
└──▷ BREAKING ON UPGRADE
!file_access_read_lines is added and the line-numbering contract is moved onto AgentFileStore — callers that previously handled line numbering outside the store must migrate.
!A2A agent run modes have been clarified with a breaking API change — existing A2A agent configurations must be updated to match the new run-mode contract.
!LocalCodeAct subprocess environment is now isolated — code that relied on inheriting the parent process environment will no longer receive those variables.
!MCP skill archives are now restricted to ZIP format only — any non-ZIP archive previously accepted will be rejected.
assistant-ui shipped an Assistant Cloud 0.2 telemetry stack — server-side trace export merged with client run reports, batched engagement events, custom scores and feedback APIs, presigned file downloads, structured API errors, and anonymous-thread claiming on sign-in.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Assistant-ui provides React components and state management for chat interfaces with streaming, tool calls, and attachments.
assistant-ui shipped an Assistant Cloud 0.2 telemetry stack — server-side trace export merged with client run reports, batched engagement events, custom scores and feedback APIs, presigned file downloads, structured API errors, and anonymous-thread claiming on sign-in.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
6 FEATURES6 OF 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Trace export and run reports for Assistant CloudNEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Adds createAssistantCloudTraceExporter, createAssistantCloudSpanProcessor, assistantCloudTraceMetadata, and withAssistantCloudTraceMetadata in assistant-cloud/telemetry to send AI SDK GenAI spans to POST /v1/traces and merge server spans with client run reports into a single trace.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Also adds a createRunReport builder in assistant-cloud to assemble run-report bodies carrying provider, outcome_type (aborted, disconnected, length, content_filter), error_code, error, message_id, first_token_ms, duration_ms, finish_reason, trace_id, environment, release, and tags from the telemetry config.
Ship server-side OpenTelemetry traces to Assistant Cloud so every LLM call is linked to its client-side run report.
javascript
import { createAssistantCloudTraceExporter, createAssistantCloudSpanProcessor } from 'assistant-cloud/telemetry';
const exporter = createAssistantCloudTraceExporter({ cloud });
const processor = createAssistantCloudSpanProcessor(exporter);
// register processor with your OpenTelemetry SDK provider
ⓘSourcesRelease notes →1 RELEASE · 2026-09-11NOTES ↗RankWhy this ranktop features scored 90/80/80, +15 breaking change, +6 runnable example — 104.33How ranking works →
Composio connects AI agents to external tools and services with managed authentication and integrations.
Composio's TypeScript SDK (@composio/[email protected]) picked up a wide set of new capabilities — webhook lifecycle management, log search, connected-account revocation and deferred-auth completion, OAuthOAuthAn open authorization protocol that lets a user grant a third-party application access to their account on another service without sharing their password, using scoped, revocable tokens instead. scope recommendations, custom toolkits, pluggable logging, and more — alongside two breaking behavior changes to webhook validation and connected-account refresh, while the platform API quietly deprecated an old tool-scopes endpoint.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
15 FEATURES15 OF 15 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Configurable SDK loggingNEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds logger and logLevel options to new Composio({...}): logger accepts any { error, warn, info, debug } sink (console, pino, winston, etc.) and logLevel accepts 'silent' | 'error' | 'warn' | 'info' | 'debug', overriding the COMPOSIO_LOG_LEVEL environment variable.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Route all Composio SDK logs through pino at debug level to capture per-request lifecycle events in production.
javascript
import pino from 'pino';
import { Composio } from '@composio/core';
const logger = pino();
const composio = new Composio({
apiKey: process.env.COMPOSIO_API_KEY,
logger,
logLevel: 'debug'
});
Full webhook lifecycle management via SDKNEW80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
Adds composio.webhooks.subscriptions with list, get, set, update, delete, rotateSecret, and listEventTypes methods, and composio.webhooks.endpoints with list, get, create, replace, and update methods for full webhook lifecycle management.
OAuth scope recommendations for toolkitsNEW80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Adds composio.toolkits.recommendScopes(toolkitSlug, { tools, ... }) and composio.toolkits.listGrantContexts(toolkitSlug) for OAuth scope recommendations (API-beta), letting callers request only the scopes a given tool set needs.
Get the OAuth scopes recommended for a set of tools before creating a connected account, so you request only what is needed.
Connected account revocation with typed errorsNEW70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds composio.connectedAccounts.revoke(), surfacing the API's 400/409 errors as ComposioConnectedAccountRevocationNotSupportedError and ComposioConnectedAccountNotRevokableError.
Exposed download size cap for URL uploadsNEW70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Exports readResponseBodyWithLimit and MAX_URL_UPLOAD_SIZE_BYTES so downstream packages can apply the SDK's 100 MiB cap when downloading from user-supplied URLs.
connectedAccounts.refresh() drops validateCredentials optionBREAKING60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
connectedAccounts.refresh() now ignores the validateCredentials option and logs a warning when it is set, because the upstream API removed validate_credentials from the connected-account refresh endpoint.
!Deprecated endpoint POST /api/v3.1/tools/scopes/required (still works)
!composio.triggers.setWebhookSubscription() now rejects malformed API responses with a ValidationError instead of reading them leniently.
!connectedAccounts.refresh() now ignores the validateCredentials option and logs a warning when it is set, because the upstream API removed validate_credentials from the connected-account refresh endpoint.
HyperFrames v0.8.35 tunes its audio-ducking defaults so narration stays clear over background music without abrupt dips at sentence breaks.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
HyperFrames is an open-source HTML-to-video renderer that runs in AI-agent workflows.
HyperFrames v0.8.35 tunes its audio-ducking defaults so narration stays clear over background music without abrupt dips at sentence breaks.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE1 OF 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Stronger default voiceover carve in carve.mjsIMPROVED75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
The default carve strength in carve.mjs was raised from 0.25 to 0.8, and the level-envelope release was extended from 1.6s to 2.4s, keeping narration clear over background music without the bed dropping out at every sentence break.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names exact file, old and new values, but no usage examplev0.8.35
ⓘSourcesRelease notes →1 RELEASE · 2026-09-11NOTES ↗RankWhy this ranktop features scored 85/85/75, +15 breaking change, +6 runnable example — 102.67How ranking works →
Transformer Engine v2.19 adds Rubin GPU support, experimental per-direction hybrid quantization, opt-in 2D MXFP8 block scaling, an experimental GatedDeltaNetAttention kernel, and expanded THD context parallelism, alongside expert-parallelism, attention and build-system improvements and two breaking API changes.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Transformer Engine provides optimized kernels and low-precision training support for Transformer models on NVIDIA GPUs.
Transformer Engine v2.19 adds Rubin GPU support, experimental per-direction hybrid quantization, opt-in 2D MXFP8 block scaling, an experimental GatedDeltaNetAttention kernel, and expanded THD context parallelism, alongside expert-parallelism, attention and build-system improvements and two breaking API changes.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
20 FEATURES16 OF 20 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
2D block scaling for MXFP8 weightsNEW85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
Adds opt-in 2D block scaling for MXFP8 weights via MXFP8BlockScaling(enable_2d_quantization=True), giving finer-grained quantization granularity during training.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Enable 2D block scaling for MXFP8 weights on Blackwell GPUs to get finer-grained quantization granularity during training.
python
import transformer_engine.pytorch as te
from transformer_engine.common.recipe import MXFP8BlockScaling
recipe = MXFP8BlockScaling(enable_2d_quantization=True)
model = te.Linear(1024, 4096)
with te.autocast(enabled=True, recipe=recipe):
out = model(inp)
NCCL-EP Python API signature changeBREAKING85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
The NCCL-EP Python API changed to support eager dispatch and drop-on-overflow: pass num_topk to ep_bootstrap, update positional ep_bootstrap and EpBuffer calls, and replace EpBuffer.token_counts with EpBuffer.tokens_per_expert.
parallel_cross_entropy memory and performanceIMPROVED75how completely this was documenteddepth25/40specificity20/30actionability30/3075 / 100
Adds an overwrite_input option to parallel_cross_entropy to reduce memory usage by reusing input storage in place, and further optimizes the function's performance and memory use.
Reduce parallel_cross_entropy peak memory by reusing the input tensor storage in-place, useful when input activations are not needed after the loss.
python
import transformer_engine.pytorch as te
loss = te.parallel_cross_entropy(logits, labels, overwrite_input=True)
MXFP8 quantization in NCCL-EP dispatch and combineNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds MXFP8 quantization support to NCCL-EP dispatch forward and combine backward, with GroupedLinear and fused grouped MLP support for prequantized grouped inputs.
NVFP4 precision extensionsNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Enables row-scaled NVFP4 weight-gradient computation in dense Linear and GroupedLinear layers, and adds NVFP4 stochastic-rounding and RHT split-quantization support on SM120 and SM121 GPUs.
Expanded THD context parallelismIMPROVED65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Expands THD context parallelism with hierarchical a2a+p2p, experimental no-load-balance AllGather, and FlashAttention 4 support on the p2p, all_gather, and a2a paths.
— Names concrete communication paths and mechanismsv2.19
0800
Build and packaging improvementsIMPROVED65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds CMake discovery of NCCL headers installed by nvidia-nccl-cu12 and nvidia-nccl-cu13, enables NVRTC to locate CUDA headers in Python site-packages at runtime for improved JIT compilation in relocated and build-isolated installations, and reduces library, wheel, and container sizes by compressing embedded CUDA binaries.
!mhc_fused_projection now always returns its H output as FP32 instead of matching the input dtype; cast explicitly where BF16 is required.
!The NCCL-EP Python API changed to support eager dispatch and drop-on-overflow: pass num_topk to ep_bootstrap, update positional ep_bootstrap and EpBuffer calls, and replace EpBuffer.token_counts with EpBuffer.tokens_per_expert.
Baseten deploys and serves machine learning models as autoscaling inference endpoints, with a model API catalog and dedicated GPU deployments.
Baseten added a Management API endpoint for tracking Model API spend and brought credential-free OIDCOIDCAn identity authentication layer built on top of OAuth 2.0, maintained by the OpenID Foundation, that lets a service verify who a user is via a standardised token from a trusted identity provider./AssumeRoleAssumeRoleAn AWS IAM API call that lets a principal request temporary credentials for a different IAM role, enabling cross-account access or privilege delegation without sharing long-term keys. authentication to training jobs.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
2 FEATURES2 OF 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Model API billing endpointNEW83how completely this was documenteddepth25/40specificity28/30actionability30/3083 / 100
New GET /v1/billing/model_apis endpoint on the Management API returns exact per-day spend subtotals for Model API usage, callable via API key auth for cost-allocation or budget-alerting pipelines.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Pull a daily breakdown of Model API costs programmatically to feed into cost-allocation or budget-alerting pipelines.
$ curl -X GET 'https://api.baseten.co/v1/billing/model_apis' \
-H 'Authorization: Api-Key <your_api_key>'
OIDC and AWS AssumeRole for training jobsNEW45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Training jobs now support OIDC and AWS AssumeRole authentication to pull private container images and download model weights or training data, without storing long-lived cloud credentials in Baseten.
Together AI substantially expanded its Fine-Tuning service with live metrics, expert-layer LoRALoRAA parameter-efficient fine-tuning method for large language models that injects small trainable rank-decomposition matrices into a frozen model, letting tools adapt LLMs cheaply without retraining all weights., early stopping, sample weighting, pre-flight dataset validation, and support for many new models, while removing two RL training-session API endpoints.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Run, train, and serve open-source AI models on Together AI.
Together AI substantially expanded its Fine-Tuning service with live metrics, expert-layer LoRALoRAA parameter-efficient fine-tuning method for large language models that injects small trainable rank-decomposition matrices into a frozen model, letting tools adapt LLMs cheaply without retraining all weights., early stopping, sample weighting, pre-flight dataset validation, and support for many new models, while removing two RL training-session API endpoints.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
10 FEATURES10 OF 10 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Expert-layer LoRA for MoE fine-tuningNEW86how completely this was documenteddepth30/40specificity28/30actionability28/3086 / 100
Adds lora_trainable_modules config to include expert layers in LoRA fine-tuning jobs on Mixture-of-Experts models, enabling up to 89% recall on newly learned facts vs.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ 15% with attention-only adapters.
Fine-tune a Mixture-of-Experts model with expert-layer LoRA to maximize retention of newly learned knowledge rather than just adapting attention.
Per-example sample weighting in training dataNEW75how completely this was documenteddepth25/40specificity22/30actionability28/3075 / 100
Adds a weight field to JSONL training examples for per-example sample weighting, controlling each data point's contribution to the loss across all supported formats and training methods.
Add per-example sample weights in a JSONL training file to up-weight high-quality human-annotated examples over synthetic ones.
Early stopping for fine-tuning jobsNEW70how completely this was documenteddepth32/40specificity20/30actionability18/3070 / 100
Adds early stopping for fine-tuning jobs: enable it with a validation set and the run halts when validation loss plateaus, retaining the best checkpoint and refunding unused training steps; patience, sensitivity, and warmup are tunable.
— Explains mechanism and tunables in depth but omits exact parameter names.launch-20260911-5550c113
0505
Dataset inspection before trainingNEW68how completely this was documenteddepth28/40specificity22/30actionability18/3068 / 100
Adds dataset inspection capability: preview tokenized rows (token IDs, token strings, per-token labels, loss spans, truncation status) before a job starts, and retrieve the fully prepared training dataset via the Python SDK or the Download link in the console.
Live per-step training metrics via API, CLI, SDK, UINEW62how completely this was documenteddepth25/40specificity22/30actionability15/3062 / 100
Exposes live per-step training metrics (loss, gradient norm, learning rate) and evaluation metrics through the Together API, CLI, Python SDK, and UI dashboard Metrics tab, with filtering by range and downsampling.
— Names surfaces and metric types but no exact command or endpoint given.launch-20260911-5550c113
thinner coverage below
0808
Sequence packing control in pre-tokenized formatNEW59how completely this was documenteddepth22/40specificity22/30actionability15/3059 / 100
Adds position_ids support in the pre-tokenized data format to control the degree of sequence packing, and a flag to disable packing entirely.
Multi-run comparison view in dashboardNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Adds a multi-run comparison view in the dashboard Metrics tab, allowing several jobs to be charted together on one set of axes while runs are still in flight.
OpenRouter is a routing gateway that exposes hundreds of models from many providers behind one OpenAI-compatible API with failover and unified billing.
OpenRouter introduced a hosted Linux shell tool and a companion Files API, letting any model on the platform execute commands and exchange files inside an isolated container.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
2 FEATURES2 OF 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Hosted shell tool for modelsNEW75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
The new shell server tool gives any model on OpenRouter a hosted Linux shell running in an isolated container, returning stdout, stderr, and exit codes back to the model.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It is available in beta on the Responses and Messages APIs.
— Names mechanism and APIs but marked beta, no full examplesnapshot-20260912
thinner coverage below
0202
Files API for shell containerNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
A new Files API moves files into and out of the shell container, enabling download of files written during a run.
— Describes function but no endpoint names or limits givensnapshot-20260912
ⓘSourcesRelease page →1 RELEASE · seen 2026-09-12NOTES ↗RankWhy this ranktop features scored 91/86/80, +15 breaking change, +6 runnable example — 106.67How ranking works →
Pinecone is a managed vector database that stores and queries embeddings for AI applications.
Pinecone shipped a local Docker emulator for offline development, launched Nexus—a new knowledge-curation and retrieval product with BYOC support—and introduced a schema-based Documents API alongside a full set of service-account management endpoints.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
4 FEATURES4 OF 4 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Pinecone Local Docker emulatorNEW91how completely this was documenteddepth35/40specificity28/30actionability28/3091 / 100
Pinecone Local is an in-memory Docker-based emulator for Pinecone Database that lets practitioners develop and test locally without a Pinecone account, API key authentication, or usage fees, supporting up to 100,000 records per index.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It ships two modes: an index emulator via the ghcr.io/pinecone-io/pinecone-index:latest image, configured with PORT, INDEX_TYPE, VECTOR_TYPE, DIMENSION, and METRIC env vars to spin up pre-configured dense or sparse serverless/pod indexes; and a full database emulator via ghcr.io/pinecone-io/pinecone-local:latest, configured with PORT and PINECONE_HOST, which emulates index lifecycle management. Requires Python SDK v6.x+, Node.js SDK v5.x+, Java SDK v4.x+, or Go SDK v3.x+.
Stand up a dense and a sparse index locally via Docker Compose for offline development without touching your Pinecone account.
Service account management APINEW86how completely this was documenteddepth30/40specificity28/30actionability28/3086 / 100
Adds a full set of service account management endpoints: list service accounts, create a service account with optional role bindings (client secret returned once), get service account details, update a service account's name, delete a service account (revokes minted tokens within seconds), and rotate the OAuth client secret via POST /service-accounts/{service_account_id}/rotate-secret (previous secret and tokens revoked within seconds).
Rotate a compromised service account OAuth secret; the previous secret and all tokens it minted are revoked within seconds.
$ curl -X POST 'https://api.pinecone.io/service-accounts/{service_account_id}/rotate-secret' \
-H 'Api-Key: YOUR_API_KEY'
— Enumerates every endpoint and gives a runnable rotate-secret command.snapshot-20260912
0303
Pinecone Nexus knowledge curation and retrieval systemNEW80how completely this was documenteddepth32/40specificity26/30actionability22/3080 / 100
Nexus is a new product that curates sources into chunks and artifacts via a manifest, then answers queries with grounded, cited responses over a retrieval SDK, introduced alongside a new 2026-07 API version with inference_2026-07.oas and admin_2026-07.oas specs. It adds Nexus BYOC (Bring Your Own Cloud) mode with defined data-residency boundaries, authentication, encryption, and cluster-footprint limits, plus context design tooling in the Nexus console letting practitioners define custom artifact and edge types in a manifest and trigger curation directly.
Fetch the new 2026-07 inference API spec to explore available endpoints before integrating.
Define custom artifact and edge types for a Nexus context manifest via the Pinecone console.
📍1. In the Pinecone console, navigate to Nexus › Contexts.
2. Select or create a context.
3. Open 'Context design' and choose 'Design your own manifest'.
4. Define custom artifact types and edge types.
5. Save and trigger curation to process your sources.
— Names API specs, BYOC scope and console workflow but no full endpoint list.product docs
0404
Documents API with schema-based indexesBREAKING65how completely this was documenteddepth28/40specificity22/30actionability15/3065 / 100
Introduces the Documents API (API version 2026-07) with schema-based indexes, replacing the previous unstructured record model. Adds a document patch endpoint to update individual fields on a document by ID, including record metadata, and a document retrieval endpoint to fetch Pinecone documents by ID or metadata filter. Existing code using the previous record model must be migrated per the 'Adopt the Documents API' guide.
— Names API version and two endpoints but no exact paths or example.snapshot-20260912
└──▷ BREAKING ON UPGRADE
!API version 2026-07 introduces schema-based indexes via the Documents API; existing code using the previous record model must be migrated — review the 'Adopt the Documents API' guide for affected endpoints and required changes.
OKF Agent Memory v0.2.0 adds scoped pre-edit discovery for AI coding agents via a new --for-path search flag, a 3-tier epistemic governance model, and code_refs bindings that tie architecture decisions to source globs, backed by new path-normalization, traversal-prevention, and workspace-confinement safeguards.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Git-native persistent memory for AI coding agents. 2 with sub-300µs in-memory BM25 search, embedded MCP server, and progressive disclosure.
OKF Agent Memory v0.2.0 adds scoped pre-edit discovery for AI coding agents via a new --for-path search flag, a 3-tier epistemic governance model, and code_refs bindings that tie architecture decisions to source globs, backed by new path-normalization, traversal-prevention, and workspace-confinement safeguards.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
6 FEATURES5 OF 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Scoped pre-edit discovery via --for-pathNEW93how completely this was documenteddepth35/40specificity28/30actionability30/3093 / 100
Adds --for-path <file> to okf search to retrieve only the governance rules (hold, constraint, context) governing a specific source file before it is edited, with results prioritized by authority (hold > constraint > context) and sub-300 µs latency.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The same capability is exposed to agent platforms via the native MCP tool as okf_search({ "for_path": "<file>" }) over the MCP stdio protocol, for use with Claude Code and Cursor.
Query all active constraints and holds governing an auth file before making changes — stop a coding agent from touching frozen code without human signoff.
— Exact CLI flag, MCP call shape, latency, and priority order given.v0.2.0
0202
Path traversal and workspace confinement safeguardsNEW88how completely this was documenteddepth35/40specificity28/30actionability25/3088 / 100
ValidateBundle now rejects code_refs values containing .. path traversal or absolute system paths (e.g. /etc/..., C:\...) as fatal GateFindings. The MCP server's resolveBundleDir confines the bundle argument to the server's canonical workspace root, preventing escape. okf validate --drift verifies that code_refs point to files that actually exist within the project root, while strictly confining all file checks inside that root to prevent side-channel probing.
Validate that all code_refs in the knowledge bundle point to files that actually exist, catching stale bindings after a codebase refactor.
$ okf validate knowledge --strict--drift
— Names exact validation mechanisms, a runnable flag, and failure modes.v0.2.0
0303
3-tier epistemic governance modelNEW83how completely this was documenteddepth35/40specificity28/30actionability20/3083 / 100
Introduces governance via the governance: frontmatter field, supporting constraint (mandatory guardrail), hold (execution freeze — no edits without human signoff), and context (advisory background). EffectiveGovernance() inference defaults files under knowledge/convention/ to constraint and domain/architecture files to context when no explicit governance: value is set.
Bind an architecture decision to the exact source globs it governs, so --for-path lookups surface it automatically for any file under those paths.
— Field values and default inference rules named precisely.v0.2.0
0404
code_refs binding of decisions to source globsNEW70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds a code_refs frontmatter attribute to OKF knowledge documents, letting teams bind architecture decisions directly to source file globs (e.g. services/auth/jwt/**) so agents can deterministically discover applicable constraints before touching code.
Bind an architecture decision to the exact source globs it governs, so --for-path lookups surface it automatically for any file under those paths.
— Names the frontmatter field and gives a glob example.v0.2.0
0505
Asset drift detection for embedded skill bundleNEW68how completely this was documenteddepth25/40specificity28/30actionability15/3068 / 100
Adds a make sync-assets command and a TestDogfoodingAssetDrift CI gate to detect drift between the live .agents/skills/okf-memory/ skill directory and the embedded bootstrap assets in pkg/okf/assets/skill/.
— Names exact paths and CI gate, no usage example given.v0.2.0
0600
Path normalization in matchCodeRef engineIMPROVED65how completely this was documenteddepth30/40specificity25/30actionability10/3065 / 100
Adds path normalization in the matchCodeRef engine, resolving relative paths, leading dot-slashes, leading slashes, Windows backslashes, and full absolute IDE system paths via suffix and subpath resolution so code_refs matches work across differing path formats.
— Detailed mechanism but no direct user command.v0.2.0
Weaviate is an open-source vector database that stores both objects and vectors, allowing for the combination of vector search with structured filtering with the fault tolerance and scalability of a cloud-native database.
Weaviate's latest releases removed the GET /mcp endpoint, changed response schemas for two search endpoints, and added node-level query admission control alongside a more flexible HFresh debug reassignment API.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
2 FEATURES1 OF 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Optional shard for HFresh debug reassignmentIMPROVED60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Makes shard optional for HFresh reassignment in the debug API, allowing cluster-wide orphaned-postings recovery without specifying a shard.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names debug API and behaviour change but no exact pathv1.39.4
thinner coverage below
0201
Node-level query admission controlNEW40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
Adds node-level query admission control (P1b) to shed load and protect individual nodes from query overload.
— Describes purpose but gives no config key or flagv1.39.4
engrim v1.4.2 adds native Codex CLI hook integration, letting sessions auto-load and save project memory without MCPMCPModel Context Protocol, an open standard from Anthropic that lets an AI model call external tools and data sources through a uniform interface, so developers avoid writing custom integrations for every service..︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
The Universal Cross-Model Episodic Memory Standard. Local-first, project-scoped SQLite memory engine for Google Antigravity, Claude Code, Cursor, Windsurf, and Codex.
engrim v1.4.2 adds native Codex CLI hook integration, letting sessions auto-load and save project memory without MCPMCPModel Context Protocol, an open standard from Anthropic that lets an AI model call external tools and data sources through a uniform interface, so developers avoid writing custom integrations for every service..︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE1 OF 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Codex CLI hook integrationNEW88how completely this was documenteddepth30/40specificity28/30actionability30/3088 / 100
engrim setup --codex wires SessionStart, SessionEnd, Stop, and UserPromptSubmit command hooks into ~/.codex/hooks.json, with deduplication and zero-dependency failure handling; engrim uninstall --codex removes it.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Wire engrim memory into Codex CLI so every session automatically loads and saves project context without requiring MCP.
$ engrim setup --codex
— Names exact hooks, config file path, and setup/uninstall commands.v1.4.2
Browser-based ontology workbench for OWL ontologies and SKOS vocabularies. Streamlit + rdflib, no Java, no Protégé.
OrionBelt tunes graph visualization performance with a new edge-curve rendering control and fixes overly persistent Find and Centre behavior.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
2 FEATURES1 OF 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Edge Curves display option for graph renderingNEW75how completely this was documenteddepth32/40specificity28/30actionability15/3075 / 100
A new Edge curves setting in the Visualization controls offers three modes — Auto, Curved, and Straight — to control how edges render at any graph size.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Auto curves graphs up to 300 edges and straightens above that threshold, counting edges rather than nodes; under 6x CPU throttle this saves a measured 4.7ms per redraw at 400 edges and 7.4ms at 800 edges when switching from curved to straight.
On a large ontology with hundreds of edges, force straight edges to eliminate per-frame curve overhead and keep the canvas responsive.
📍In the Visualization page, open display options, find 'Edge curves', and select 'Straight'.
— Names exact settings, threshold, and measured timing gainsv1.27.4
thinner coverage below
0200
Find and Centre no longer permanently seeds focusIMPROVED37how completely this was documenteddepth22/40specificity10/30actionability5/3037 / 100
Picking an entity via Find and Centre is now used as a render seed for one redraw only, instead of persisting as a permanent focus seed; clearing the picker forgets the prior pick.
— Describes before/after behavior but no config surface or stepsv1.27.4
PromptLayer is a platform for managing, evaluating, and observing prompts and LLM applications.
PromptLayer added support for Google's Gemini 3.8 Flash model across multiple providers with expanded context and multimodal input handling.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
1 FEATURE1 OF 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Gemini 3.8 Flash model supportNEW60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
PromptLayer now supports Google's Gemini 3.8 Flash model across Google AI Studio, Vertex AI, and OpenRouter providers, with configurable reasoning effort levels (low, medium, high) and 1M+ token context length.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The model also supports multimodal inputs — text, images, video, audio, and PDF files.
ⓘSourcesRelease page →1 RELEASE · 2026-08-20NOTES ↗RankWhy this ranktop features scored 95/86/78, +15 breaking change, +6 runnable example — 107.33How ranking works →
LangSmith provides tracing, evaluation, and deployment tools for LLM applications.
LangSmith's latest release adds CLI-driven LLM-as-judge evaluator creation, bulk and thread-aware annotation queue APIs, multi-turn evaluator testing, and a new public experiment comparison API that replaces legacy comparison helpers, alongside smaller permission, trace-limit, and dataset-split UI improvements.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
8 FEATURES6 OF 8 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0100
Bulk annotation queue item APIs for runs and threadsIMPROVED95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
POST /annotation-queues/<id>/items adds RUN items to a single annotation queue in bulk (up to 200 items per request), resolving runs via ClickHouse or SmithDB and returning a standards-shaped items envelope.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ The endpoint now also accepts item_type THREAD (with thread_id + session_id) so conversation threads can be added to annotation queues, and mixed RUN and THREAD batches are supported in a single request.
Add a batch of conversation threads to an annotation queue for human review, mixing thread and run items in one request.
— Full endpoint, limits, and mixed-batch behavior with runnable examplesnapshot-20260912
0201
Multi-turn evaluator testing before savingNEW86how completely this was documenteddepth30/40specificity28/30actionability28/3086 / 100
The /runs/rules/validate endpoint gains test_thread_id and session_id parameters to test a multi-turn (thread) evaluator against a real conversation before saving, and the UI adds a matching Multi-turn evaluator Test action that runs the evaluator against a sample thread before saving the rule.
Validate a multi-turn evaluator rule against a real conversation thread before committing it, to catch mapping or logic issues early.
— Names endpoint params and matching UI action, with examplesnapshot-20260912
0302
Public experiment comparison API replaces legacy helpersBREAKING78how completely this was documenteddepth30/40specificity28/30actionability20/3078 / 100
POST /v2/datasets/<id>/experiment-runs is now the public API for paginated experiment comparison. Legacy dataset comparison helpers are removed from the public OpenAPI spec and generated SDKs — existing HTTP routes still work for LangSmith UI clients, but SDK-generated clients using those helpers must migrate.
— Endpoint and removal named but no migration example givensnapshot-20260912
0403
CLI evaluator creation for LLM-as-judge rulesNEW70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
The langsmith evaluator create-llm CLI command defines structured LLM-as-judge evaluator rules from a prompt, schema, and model config file, and targets a specific project or dataset.
— Names CLI command and inputs but no full runnable examplesnapshot-20260912
0504
Legacy feedback formula endpoints deprecatedDEPRECATED70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
The legacy feedback formula endpoints (POST/GET /feedback/formulas and GET/PUT/DELETE /feedback/formulas/{feedback_formula_id}) are deprecated and scheduled for removal on 2026-08-20; existing feedback formulas must be migrated to composite evaluators before that date.
— Endpoints and removal date given, no migration walkthroughsnapshot-20260912
0600
In-place update for code evaluator uploadsIMPROVED65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
The LangSmith CLI evaluator upload --replace flag now updates existing code evaluator rules in place, avoiding a delete-before-create window if the replacement upload fails.
Split assignment column and inline editing in experiment viewsNEW60how 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 in a row's Splits cell in experiment results and comparison views is now interactive, with an Edit splits action that opens the single-example split picker.
— UI path described but no config or API name givensnapshot-20260912
thinner coverage below
0806
Separate download datasets permissionNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Introduces a separate download datasets permission, enforced in both the application and APIs, with a disabled download button shown for users lacking the permission.
— Permission named but no config or API surface givensnapshot-20260912
└──▷ BREAKING ON UPGRADE
!The legacy feedback formula endpoints (POST/GET /feedback/formulas and GET/PUT/DELETE /feedback/formulas/{feedback_formula_id}) are deprecated and scheduled for removal on 2026-08-20; migrate existing feedback formulas to composite evaluators before that date.
!Legacy dataset comparison helpers are removed from the public OpenAPI spec and generated SDKs; update any SDK-generated clients that used those helpers (existing HTTP routes continue to work for LangSmith UI clients).
This window's headline is Phoenix's expanding coding-agent ecosystem — a native MCP server plus Claude Code, Codex, and Cursor plugins, an AI skills library, and three new evaluators (retrieval relevance, completeness, session-level PII detection) — alongside GraphQL note-taking mutations and DSL-level cost and annotation filtering.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Arize Phoenix is an open-source platform that monitors LLM application traces and evaluates their outputs.
This window's headline is Phoenix's expanding coding-agent ecosystem — a native MCP server plus Claude Code, Codex, and Cursor plugins, an AI skills library, and three new evaluators (retrieval relevance, completeness, session-level PII detection) — alongside GraphQL note-taking mutations and DSL-level cost and annotation filtering.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
8 FEATURES7 OF 8 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
MCP server and coding agent plugin marketplaceNEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Phoenix 19.0.0+ ships a native MCP server mounted at <your-endpoint>/mcp, letting coding agents connect via Streamable HTTP.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ A new arize-phoenix plugin in the Codex plugin marketplace registers the Phoenix MCP server through a scripts/phoenix-mcp stdio bridge using mcp-remote; a Claude Code plugin with marketplace support connects Claude Code directly to the MCP server; and a Cursor plugin exposes the remote MCP server along with public skills and the Phoenix docs MCP. The Claude Code endpoint can be set non-interactively via --config endpoint=https://phoenix.example.com at install time or by editing pluginConfigs in ~/.claude/settings.json; headless/CI Codex setups use PHOENIX_ENDPOINT and PHOENIX_API_KEY env vars, with the launcher stripping trailing slashes and appending /mcp; and the Codex plugin can be disabled without uninstalling via enabled = false in ~/.codex/config.toml.
Install the Phoenix plugin into Claude Code for all projects so every session gets the MCP server and px/eval/instrument skills automatically.
$ # Inside a Claude Code session:
/plugin marketplace add Arize-ai/phoenix
/plugin install arize-phoenix@arize-phoenix --config endpoint=https://phoenix.example.com
# Or non-interactively from your shell:
claude plugin marketplace add Arize-ai/phoenix
claude plugin install arize-phoenix@arize-phoenix --config endpoint=https://phoenix.example.com
Connect Codex to a deployed Phoenix instance with auth enabled so the MCP bridge authenticates via bearer token without opening a browser.
— Full flags, env vars, config paths and runnable install commands given.arize-phoenix-v20.10.0
0202
New evaluators: retrieval relevance, completeness, session PIINEW60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Phoenix Evals adds a retrieval relevance evaluator for scoring how well retrieved documents match a query, a completeness evaluator for measuring whether a response fully addresses the input, and a session-level pii_detection evaluator that operates across an entire conversation session rather than individual spans.
AI skills for error analysis and Harbor evaluationNEW50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Adds a phoenix-error-analysis skill for reading sampled traces, writing free-form notes, and grouping them into a failure taxonomy to pick eval targets and fix priorities, and a phoenix-harbor skill for configuring Harbor agent evaluations and interpreting their Phoenix experiments, scores, and ATIF traces.
ⓘSourcesRelease page →1 RELEASE · 2026-09-01NOTES ↗RankWhy this ranktop features scored 90/90/85, +15 breaking change, +6 runnable example — 109.33How ranking works →
Braintrust provides evaluation, tracing, and improvement workflows for AI applications.
Braintrust's biggest additions this window are Loop automations with a managed server-side runtime, and Patterns for automated trace investigation, alongside a broad expansion of coding-agent tracing integrations (Claude Code, Codex, Grok, Google Antigravity, OpenCode, pi) and a wave of new bt CLI commands for environments, prompts, projects, and templates.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Two breaking changes affect trace plugin versions and bt sync pull history windows.
└──▷ WHAT SHIPPED ·
18 FEATURES17 OF 18 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Environment and prompt version management in bt CLINEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
bt CLI adds bt environments create <name> --slug to create an organization-level environment, bt prompts versions <prompt> to list all versions of a prompt, bt prompts assign <prompt> --version <version> --environment <env> to pin a version to an environment, and bt prompts unassign <prompt> --environment <env> to remove a prompt from an environment.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Create a Production environment and pin a tested prompt version to it as part of a deployment workflow.
$ bt environments create Production --slug production
bt prompts versions my-prompt
bt prompts assign my-prompt --version <version> --environment production
Roll back or retire a prompt from an environment without deleting the prompt itself.
$ bt prompts unassign my-prompt --environment production
— Four exact commands with a runnable deployment example.product docs
0202
bt sync pull default history window changeBREAKING90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
bt sync pull now includes all matching experiment and dataset history by default; pass --window or set BT_SYNC_WINDOW to restore the previous windowed behavior. Project logs retain the default three-day window.
Coding agent tracing integrationsNEW85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
Adds integrations that trace and connect coding-agent sessions to Braintrust: Claude Code (from the terminal or the Code tab in the Claude desktop app), Claude Cowork (connects to the Braintrust MCP server), Codex (traces sessions and accesses Braintrust data via MCP), Google Antigravity (traces sessions and accesses data via MCP, with bt trace enable antigravity and bt trace import antigravity (v0.19.1+) to activate the plugin and import existing conversations), Grok (traced via bt CLI v0.19.3+, capturing each session as a trace with Git repository metadata without interrupting the agent if tracing fails), OpenCode (traces via built-in tools or MCP), and pi (traces turns, model calls, tool executions, and compactions). Span metadata for Google Antigravity, Grok, OpenCode, and pi sessions now includes the local username.
— Exact commands for some agents, others only described in prose.snapshot-20260912
0404
Deployment configuration flags for bt CLINEW80how completely this was documenteddepth25/40specificity30/30actionability25/3080 / 100
Adds --app-public-url and BRAINTRUST_APP_PUBLIC_URL environment variable to the bt CLI (v0.19.3+) for deployments where the browser-facing app URL differs from the authentication endpoint, and BRAINTRUST_CUSTOM_CA_BUNDLE environment variable so Rust SDK tracing and data uploads can trust private or corporate certificate authorities by supplying PEM certificate contents directly.
— Two exact env vars and a flag named, no invocation example.snapshot-20260912
0505
bt projects create, view, delete commandsNEW80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Adds bt projects create, view, and delete commands with JSON output support for automation; view --json returns project details without opening a browser.
List all projects and get machine-readable JSON output to feed into a CI pipeline or audit script.
$ bt projects view --json
— Runnable command with a CI-oriented example provided.snapshot-20260912
0606
bt trace update, doctor, and disable commandsNEW80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
Adds bt trace update command (v0.19.3+) to update installed coding-agent integrations without rewriting their tracing settings; bt trace doctor warns about outdated plugins and mismatched package version ranges; bt trace disable attempts to remove tracing configuration even if uninstalling the plugin fails.
— Three commands named with exact behavior described.snapshot-20260912
0707
Loop automations and managed runtimeNEW80how completely this was documenteddepth35/40specificity30/30actionability15/3080 / 100
Adds Loop automations: scheduled Loop runs with their own instruction, model, and write permissions that leave a resumable read-only thread and can post results to a Slack channel or webhook. Loop now runs in a Braintrust-managed runtime (server-side) so it persists threads, works across logs, experiments, and datasets, and can create and edit prompts, scorers, datasets, facets, custom views, dashboards, and automations; writes pause for approval unless auto-accept is enabled. Loop runs on built-in GPT-5.6 Sol, GPT-5.6 Terra, and GPT-5.6 Luna models so threads work without configuring an AI provider.
— Rich mechanism and named models, but no config surface.snapshot-20260912
0808
Session tagging via bt CLINEW75how completely this was documenteddepth20/40specificity30/30actionability25/3075 / 100
Adds --tag flag and BRAINTRUST_TAGS environment variable to bt CLI (v0.19.3+) to attach session tags for Claude Code, Codex, Google Antigravity, OpenCode, and pi traces.
— Exact flag and env var, no example invocation shown.snapshot-20260912
0909
bt observability template commandsNEW70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds bt observability template commands (v0.19.0+) to export a project's facets and Loop automations as a portable JSON template and apply it to another project.
— Command named, exact subcommand syntax not shown.snapshot-20260912
1010
Patterns automated trace investigationNEW65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Adds Patterns, a scheduled Loop-powered investigation that searches traces for recurring problems and trends not covered by existing scorers, saving each finding with supporting traces and suggested fixes; findings can seed new scorers, classifiers, or Loop investigations.
— Mechanism explained but no config key or command given.snapshot-20260912
1111
GLM-5.3 Flash model in Braintrust GatewayNEW65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
Adds GLM-5.3 Flash, a multimodal reasoning model, as a built-in open-source model selectable under the Braintrust provider in playgrounds, prompts, and scorers, or requestable as glm-5.3-flash through the Braintrust Gateway.
Streaming log search in BrainstoreIMPROVED65how completely this was documenteddepth30/40specificity25/30actionability10/3065 / 100
Brainstore log search now streams results as segments finish scanning on an asynchronous execution engine, covering full-text, phrase, and multi-clause ANY_SPAN() trace searches including negated clauses.
— Mechanism explained but no command or config surface.snapshot-20260912
1312
OpenCode and pi tracing integrations upgraded to v2BREAKING65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
bt trace enable opencode and bt trace enable pi now install v2 of their respective tracing integrations; existing setups must follow the v0.19.3 migration instructions.
— Commands named, migration instructions referenced but not detailed.snapshot-20260912
thinner coverage below
1413
Metric columnstore for trace loadingNEW55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
Adds Metric columnstore, enabled in project settings alongside log search optimization, which writes columnar artifacts during compaction to speed up loading and sorting traces on high-volume projects.
MCP server integration for BraintrustNEW50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Adds a Braintrust MCP server integration letting Claude Code, Cowork, Cursor, Codex, and other MCP clients query logs, author scorers, configure Topics, and run evaluations directly.
— Capabilities named but no setup command or config given.product docs
1615
Blind human reviews project settingNEW50how completely this was documenteddepth25/40specificity10/30actionability15/3050 / 100
Adds Blind human reviews project setting that hides peer scores, comments, and aggregates for a row until a reviewer fills in their own scores, preserving reviewer independence throughout a review.
Dashboard sections for chart groupingNEW45how completely this was documenteddepth20/40specificity10/30actionability15/3045 / 100
Adds Dashboard sections to group charts into named, collapsible, reorderable, and duplicatable sections on a dashboard.
— UI feature described without exact navigation path.snapshot-20260912
1817
ElevenLabs SDK tracing integrationNEW30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Adds ElevenLabs SDK tracing integration to capture audio generation calls in Braintrust for debugging, evaluation, and production monitoring.
— Thin description with no setup detail.product docs
└──▷ BREAKING ON UPGRADE
!bt trace enable opencode and bt trace enable pi now install v2 of their respective tracing integrations — existing setups must follow the v0.19.3 migration instructions.
!bt sync pull now includes all matching experiment and dataset history by default; pass --window or set BT_SYNC_WINDOW to restore the previous windowed behavior. Project logs retain the default three-day window.
FailproofAI 1.0.4 introduces credential-exposure detection across agent transcripts with automated local audits, alerting, and native OpenClaw SQLite support, while stripping the audit's scoring and persona sections down to credential findings.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Observability and enforcement for AI agent harnesses. Capture every run and runtime reliability with policy enforcement. 40 built-in policies, a local dashboard, no account required with a generous free cloud plan
FailproofAI 1.0.4 introduces credential-exposure detection across agent transcripts with automated local audits, alerting, and native OpenClaw SQLite support, while stripping the audit's scoring and persona sections down to credential findings.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
7 FEATURES5 OF 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. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
OpenClaw SQLite transcript supportNEW73how completely this was documenteddepth30/40specificity28/30actionability15/3073 / 100
Supports OpenClaw 2026.9.2's per-agent SQLite databases for live transcript discovery and tailing, with deduplication of rewritten transcripts and continued legacy JSONL support; these sessions now appear in the local dashboard and can be downloaded as JSONL.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
— Names exact tool version, storage format, and dashboard download option1.0.4
0202
Credential-exposure detection in transcriptsNEW67how completely this was documenteddepth30/40specificity22/30actionability15/3067 / 100
Audits now detect credentials exposed in agent transcripts, grouping repeated sightings into a single finding that shows a masked value, source location, carrier agent, and rotation guidance in the audit dashboard.
— Clear mechanism and dashboard fields, but no command or endpoint given1.0.4
thinner coverage below
0303
Alerting for exposed credentialsNEW55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Linux and macOS desktop notifications alert you while a credential remains exposed, with macOS delivery via a per-user LaunchAgent; optional email alerts include the newest masked exposure and its source.
— Names delivery mechanisms (LaunchAgent, email) but no setup steps1.0.4
0400
Expanded redaction coverageIMPROVED55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
Extends redaction coverage to JSON, YAML, spaced assignments, camelCase credential names, terminal output, and exported reports.
— Lists concrete formats covered but no config or example1.0.4
0504
Audit report simplified to credential findingsBREAKING55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
The audit score, letter grade, projected score, persona report, and behavioral sections have been removed; the audit now shows only credential findings and scan statistics.
— Names exact removed sections but no migration guidance1.0.4
0605
Scheduled local audits every 7 daysNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Scheduled audits run automatically every seven days after setup, entirely locally without requiring an account.
— States cadence and no-account behavior but no config surface1.0.4
0700
Claude subagent and workflow transcript auditsIMPROVED35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
Claude audits now include nested subagent and workflow transcripts.
— Brief statement with no further mechanism detail1.0.4
└──▷ BREAKING ON UPGRADE
!The audit score, letter grade, projected score, persona report, and behavioral sections have been removed; the audit now shows only credential findings and scan statistics.
SAFE2 CLI 0.3.0 introduces a full safe2 feedback subcommand suite for capturing, verifying, and signing agent task evidence, backed by seven new versioned JSON contracts for automation.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Ai-Safe2-Framework provides governance, risk, and compliance controls for securing agentic AI systems and non-human identities.
SAFE2 CLI 0.3.0 introduces a full safe2 feedback subcommand suite for capturing, verifying, and signing agent task evidence, backed by seven new versioned JSON contracts for automation.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
8 FEATURES8 OF 8 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
safe2 feedback capture-pytest for test evidenceNEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
The safe2 feedback capture-pytest subcommand runs selected tests and captures fresh evidence, recording the observed exit code separately from test-pass status.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Supported options include --execute, --python, --cwd, --task-id, --revision, --environment, --call-id, and --output.
safe2 feedback receipt for task evidence receiptsNEW75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
The safe2 feedback receipt subcommand produces JSON or Markdown evidence receipts for agent-generated task claims, configurable via --artifact-root, --format, and --output options.
safe2 feedback report signing and verificationNEW65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
safe2 feedback sign-report creates a detached signature authenticating test/tool report bytes against an operator-trusted key, and safe2 feedback verify-report checks a detached signature against a supplied trusted key.
safe2 feedback capture-process for command observationNEW50how completely this was documenteddepth15/40specificity15/30actionability20/3050 / 100
The safe2 feedback capture-process subcommand explicitly runs and observes a local command, keeping process capture distinct from test-result assessment.
nono v0.77.0 prepares for a v1.0 API freeze by ripping out legacy profile, flag, and environment-variable aliases, and changes how network-notification sessions bootstrap.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
The nono runtime runs AI agents in isolated environments with policy-controlled filesystem, network, and credential access.
nono v0.77.0 prepares for a v1.0 API freeze by ripping out legacy profile, flag, and environment-variable aliases, and changes how network-notification sessions bootstrap.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
2 FEATURES1 OF 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Legacy profile, flag, env-var and CLI aliases removedBREAKING85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
Ahead of the v1.0.0 API freeze, nono removes all legacy profile-key aliases, the deprecated nono policy subcommand (including nono policy groups, nono policy profiles, nono policy show), legacy CLI flag aliases (e.g.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ --allow-net, --net-allow), and legacy environment variable aliases NONO_NET_BLOCK, NONO_NET_ALLOW, NONO_ALLOW_PROXY, NONO_PROXY_ALLOW, NONO_PROXY_CREDENTIAL, NONO_EXTERNAL_PROXY, and NONO_EXTERNAL_PROXY_BYPASS. Profile JSON using old flat-schema keys such as security.allowed_commands or policy.add_deny_commands will now fail to parse instead of warning; migrate to commands.allow / commands.deny and nono profile equivalents, since old env vars will now silently have no effect and old CLI flags cause parse errors.
— Names every removed key, flag, env var, and gives migration path.v0.77.0
thinner coverage below
0200
CLONE_FILES bootstrap for network-notification sessionsIMPROVED35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
Network-notification session startup now uses CLONE_FILES bootstrap, replacing the previous fork model.
— Names the mechanism but not behavioural impact or scope.v0.77.0
└──▷ BREAKING ON UPGRADE
!Legacy profile-key aliases and the deprecated nono policy subcommand now fail to parse instead of warning — any profile JSON still using the old flat-schema keys (e.g. security.allowed_commands, policy.add_deny_commands) or any script calling nono policy groups / nono policy profiles / nono policy show will break on upgrade. Migrate to commands.allow / commands.deny and nono profile equivalents.
!Legacy environment variable aliases NONO_NET_BLOCK, NONO_NET_ALLOW, NONO_ALLOW_PROXY, NONO_PROXY_ALLOW, NONO_PROXY_CREDENTIAL, NONO_EXTERNAL_PROXY, and NONO_EXTERNAL_PROXY_BYPASS are no longer recognized — scripts or CI pipelines that set these will silently have no effect.
!Legacy CLI flag aliases (e.g. --allow-net, --net-allow) are removed and will now cause a parse error instead of emitting a deprecation warning.
ⓘSourcesRelease notes →1 RELEASE · 2026-09-11NOTES ↗RankWhy this ranktop features scored 93/80/67, +15 breaking change, +6 runnable example — 101How ranking works →
ToolHive v0.49.0 replaces its vMCP dial-control hook with a workload-aware resolver, ships a generated Go client for its management API, tightens AWS STSAWS STSAWS Security Token Service, an Amazon Web service that issues short-lived credentials for IAM roles, letting tools authenticate to AWS APIs without storing long-term secrets. role-claim evaluation, and bumps its Go toolchain requirement to 1.27.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
ToolHive runs MCP servers in isolated containers and enforces identity and access policies for local and Kubernetes deployments.
ToolHive v0.49.0 replaces its vMCP dial-control hook with a workload-aware resolver, ships a generated Go client for its management API, tightens AWS STSAWS STSAWS Security Token Service, an Amazon Web service that issues short-lived credentials for IAM roles, letting tools authenticate to AWS APIs without storing long-term secrets. role-claim evaluation, and bumps its Go toolchain requirement to 1.27.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
5 FEATURES5 OF 5 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Workload-aware dial-control resolver in vMCP sessionBREAKING93how completely this was documenteddepth35/40specificity28/30actionability30/3093 / 100
pkg/vmcp/session adds session.WithDialControlResolver, replacing the removed session.WithDialControl.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ It lets embedders express a per-backend dial-control policy keyed by workload ID — the resolver is a func(workloadID string) func(network, address string, c syscall.RawConn) error, and returning nil leaves that backend on http.DefaultTransport. Callers using the old hook get a compile error and must wrap it in the new resolver shape.
Enforce per-backend SSRF/private-range dial policy in a vMCP embedder — deny private ranges for most backends, but allow private dialing for a trusted internal workload.
— Names the exact API, migration path, and includes a runnable code examplev0.49.0
0202
OAuth2 upstream token endpoint auth method revertedBREAKING80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
The default tokenEndpointAuthMethod for pre-registered oauth2 upstream providers is reverted: upgrading from v0.48.0 with a client secret and no explicit tokenEndpointAuthMethod switches back from client_secret_basic to POST-body credentials. IdPs requiring HTTP Basic must now set tokenEndpointAuthMethod: client_secret_basic explicitly in the upstreamProviders config.
Opt a pre-registered OAuth2 upstream into HTTP Basic auth at the token endpoint when your IdP requires it.
— Includes exact config key, values, and a working YAML examplev0.49.0
0303
AWS STS role-claim evaluation tightenedBREAKING67how completely this was documenteddepth30/40specificity22/30actionability15/3067 / 100
AWS STS role-claim evaluation now supports bare-string claims — a string exactly matching a configured claim selects its mapped role instead of fallbackRoleArn. As a breaking change, role claims that are an object, number, boolean, or null now fail closed with HTTP 403 (Failed to determine IAM role) instead of silently receiving the fallback role.
— States the exact fail-closed error and old-vs-new behaviourv0.49.0
0404
Go 1.27 toolchain requirement and builder image bumpBREAKING62how completely this was documenteddepth25/40specificity22/30actionability15/3062 / 100
The root Go module now requires Go 1.27.0 — builds using GOTOOLCHAIN=local pinned to Go 1.26 fail with go: go.mod requires go >= 1.27. The default builder image for go:// workloads is updated from golang:1.26-alpine to golang:1.27-alpine for workloads without an explicit image pin.
— Gives exact error message and image tags before/afterv0.49.0
thinner coverage below
0505
Generated Go client for management APINEW25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Ships a dependency-light generated Go client for the ToolHive management API.
— No package path, endpoints, or usage shown beyond one linev0.49.0
└──▷ BREAKING ON UPGRADE
!session.WithDialControl in pkg/vmcp/session is removed; callers get a compile error and must migrate to session.WithDialControlResolver wrapping their hook in a func(workloadID string) func(network, address string, c syscall.RawConn) error resolver.
!OAuth2 upstream tokenEndpointAuthMethod default is reverted: upgrading from v0.48.0 with a pre-registered oauth2 upstream that has a client secret and no explicit tokenEndpointAuthMethod switches back from client_secret_basic to POST-body credentials; IdPs requiring HTTP Basic must now set tokenEndpointAuthMethod: client_secret_basic explicitly.
!AWS STS role claims that are an object, number, boolean, or null now fail closed with HTTP 403 (Failed to determine IAM role) instead of silently receiving the fallback role.
!Root Go module now requires Go 1.27.0; builds using GOTOOLCHAIN=local pinned to Go 1.26 fail with go: go.mod requires go >= 1.27. go:// workloads without an explicit image pin now build against golang:1.27-alpine instead of golang:1.26-alpine.
Anthropic added live terminal control over Claude Managed Agents sessions and richer permission-policy telemetry for agent and MCP tool calls.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
Anthropic provides Claude AI models and APIs for building applications that generate, analyze, and automate work.
Anthropic added live terminal control over Claude Managed Agents sessions and richer permission-policy telemetry for agent and MCP tool calls.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄
└──▷ WHAT SHIPPED ·
2 FEATURES1 OF 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
0101
Live session control via ant beta:sessions connectNEW86how completely this was documenteddepth32/40specificity24/30actionability30/3086 / 100
The CLI gains ant beta:sessions connect to attach your terminal to a running Claude Managed Agents session, letting you send messages live and interactively approve or deny pending tool calls.︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄ Passing --web instead serves the Claude Console session viewer locally for graphical monitoring and approval.
Interactively supervise a running Managed Agents session from CI or a local terminal — approve or deny tool calls in real time without leaving the shell.
$ ant beta:sessions connect <session-id>
Open the graphical Claude Console session viewer locally to monitor and approve tool calls when a browser is available.
Permission policy evaluation fields for agent tool callsIMPROVED63how completely this was documenteddepth26/40specificity25/30actionability12/3063 / 100
Claude Managed Agents permission policies now support agent.tool_use and agent.mcp_tool_use event types, each carrying an evaluation field and an evaluated_permission field that report whether a given agent or MCP tool call was run, denied, or paused for approval.