The daily firehose — everything the toolchain shipped today, already filtered.
// HOW THIS ISSUE IS MADE
We read every release from the 184 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# 26 tools matched
Same issue, same prompt, two writers:
A read across the whole issue before you read any of it: what stands out in today's releases, grouped by what it lets you do. Every tool named links to its entry below.
Three unrelated things stand out. FailproofAI's daemon now blocks disallowed agent actions at the hook level across twelve agent CLIs instead of logging them after the fact. Mend SAST scans Azure DevOps and Bitbucket Cloud repos per branch, so a feature branch's findings stop drowning in main's. Beelzebub varies HTTP responses by method, denying scanners an easy honeypot fingerprint.
protect
Stop an agent's disallowed action instead of reading about it later
FailproofAI's background daemon fails closed and enforces at the live hook across twelve agent CLIs, with digest-verified policy packs and an observe mode so you can measure breakage before you enforce; a Recommended 15-policy setup removes the blank-page problem of authoring agent guardrails from scratch. Kiro Crew adds a secrets vault, which keeps API keys out of the environment a sub-agent inherits when it shells out.
Triage SAST findings on the branch that introduced them
Per-branch project scanning for Azure DevOps and Bitbucket Cloud means a scan of a feature branch reports as its own project rather than merging into the default-branch backlog, which is the usual reason developers ignore SASTSASTStatic Application Security Testing: automated analysis of source code or binaries without executing them, used to find vulnerabilities early in development before deployment. output — they cannot tell what they broke from what was already there. New JavaScript/TypeScript and Rust detections widen coverage, and finer risk triage data cuts the manual step of pulling context before deciding whether a finding ships.
Beelzebub v3.9.1 routes HTTP by method, so a GET and a POST to the same path no longer return the identical canned response. Commodity scanners fingerprint deception services precisely by that uniformity; varying on method costs an attacker a probe and buys the defender the session.
Set data retention and move traces between projects without a support ticket
Phoenix client 7.7.0 exposes project retention policies programmatically, so a retention rule becomes code that lives with the deployment rather than a console setting nobody remembers changing, and cross-project trace transfer lets you move prompt and completion data out of a shared project when it turns out to hold something it should not. LangSmith adds OpenTelemetryOpenTelemetryA CNCF-maintained open standard and SDK collection for capturing traces, metrics, and logs from applications in a vendor-neutral format, letting cyber tools ingest observability data without locking into a proprietary pipeline. resource attributes to trace metadata, giving traces the same service and environment tags as the rest of your telemetry.
Three unrelated things stand out today: FailproofAI can now enforce agent policy fail-closed across CLIs, Mend AI scans branches separately in Azure DevOps and Bitbucket Cloud, and beelzebub made its HTTP honeypot harder for scanners to fingerprint.
protect
Fail closed when an agent CLI violates policy
FailproofAI now runs a background daemon with live-hook enforcement across twelve agent CLIs, with digest-verified policy packs and observe mode. Teams can move from advisory checks to a guardrail that blocks unsafe agent actions instead of relying on developers to notice warnings after the fact.
Mend SAST now supports per-branch project scanning for Azure DevOps and Bitbucket Cloud, with more granular triage data and added JavaScript/TypeScript and Rust detections. That lets teams review risk on the branch where a change is being made, instead of flattening findings into the main project and sorting context manually.
Beelzebub added method-aware HTTP routing to its deception service. A scanner that fingerprints by trying different HTTP verbs now gets behavior closer to a real service, which makes low-effort detection of the trap harder and keeps noisy probes observable longer.
Attach retention and trace movement to observability projects in code
Phoenix added programmatic project retention policies and cross-project trace transfer, while LangSmith added OpenTelemetryOpenTelemetryA CNCF-maintained open standard and SDK collection for capturing traces, metrics, and logs from applications in a vendor-neutral format, letting cyber tools ingest observability data without locking into a proprietary pipeline. resource attributes for trace metadata. Teams can make trace ownership, lifespan, and routing part of automation instead of cleaning up or reclassifying observability data by hand.
Groq is a high-speed inference engine that runs large language models significantly faster than traditional GPUs.
└──▷ WHAT SHIPPED · 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
GPT-OSS reasoning models on chat completions APINEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Adds openai/gpt-oss-20b and openai/gpt-oss-120b via POST https://api.groq.com/openai/v1/chat/completions. Both are MoE reasoning models with 131K token context and 32K max output tokens, and both support built-in browser search, code execution, and structured output. The 20b model uses 32 experts at ~1000+ TPS; the larger 120b model uses 128 experts at ~500+ TPS for higher-accuracy tasks.
Run a reasoning task against the 20B model using your existing OpenAI-compatible API integration.
Official SpaceXAI API documentation. Build with Grok: chat, image and video generation, voice, tool calling, and structured outputs.
Grok's image API gains an adaptive auto quality mode that changes the default output quality and billing, alongside support for more reference images and wider aspect ratios in generation and editing.
└──▷ WHAT SHIPPED · 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Auto quality mode for image generation and editingBREAKING80how completely this was documenteddepth32/40specificity26/30actionability22/3080 / 100
Adds auto as an accepted value for the quality parameter on grok-imagine-image-2.0, which dynamically selects low for generation and medium for editing, with billing reflecting the quality actually served. The default value of quality when the parameter is omitted has changed from medium to auto, so existing requests that omit quality will now receive low-quality output for generation (previously medium) — pass low or medium explicitly to pin a specific quality.
— Names parameter, model, values, and mitigation clearlysnapshot-20260901
02
More reference images and wider aspect ratios for image APIIMPROVED70how completely this was documenteddepth22/40specificity24/30actionability24/3070 / 100
Increases the maximum number of source images accepted per image-editing request from 3 to 5 (via repeated image[] fields). Adds 21:9 (cinematic widescreen) and 5:2 (wide banners) as accepted aspect ratio values for both image generation and editing.
Use a cinematic 21:9 aspect ratio for a widescreen banner image in a single generation request.
— Concrete limit change and named ratio values with runnable examplessnapshot-20260901
└──▷ BREAKING ON UPGRADE
!The default value of the quality parameter on grok-imagine-image-2.0 has changed from medium to auto. Existing requests that omit quality will now receive low-quality output for image generation (previously medium), changing both visual output and billing cost.
OpenAI shipped GPT Live Transcribe, a new low-latency streaming transcription capability built on the Realtime API.
Docs and resources to help you build with, for, and on OpenAI.
OpenAI shipped GPT Live Transcribe, a new low-latency streaming transcription capability built on the Realtime API.
└──▷ WHAT SHIPPED · 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
GPT Live Transcribe streaming transcriptionNEW58how completely this was documenteddepth28/40specificity18/30actionability12/3058 / 100
Adds GPT Live Transcribe for low-latency streaming transcription via the Realtime API. It supports free-form transcription context and keyword hints to improve recognition accuracy, supports multiple expected input languages for both transcription models, and provides final transcripts of committed Realtime turns alongside the streaming output.
— Describes behavior and API surface but no concrete endpoint, flag, or examplesnapshot-20260901
HyperFrames v0.8.21 gives AI agents deeper control over Studio compositions via WebMCP and adds a new handwritten-style block to the Registry.
Write HTML. Render video.
HyperFrames v0.8.21 gives AI agents deeper control over Studio compositions via WebMCP and adds a new handwritten-style block to the Registry.
└──▷ WHAT SHIPPED · 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
WebMCP agent control surfaces in StudioNEW60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Adds the studio_frame WebMCP tool giving agents visibility into the current Studio frame for inspection and context, plus additional WebMCP support letting agents drive Studio's selection and playhead position, edit text and styles within compositions (guarded), and author motion within compositions.
— Names one WebMCP tool; three related capabilities described only in prosev0.8.21
02
Handwritten write-on block in RegistryNEW60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Adds the hw-write-title block and control surfaces for the handwritten family to the Registry, cataloged as the 'hw write-on wave' entry.
— Names the exact block and catalog entry, no usage detail givenv0.8.21
Triton v2.72.0 adds a log callback mechanism for embedding custom logging, introduces presets-file driven builds, and extends OpenVINOOpenVINOAn open-source toolkit from Intel for optimizing and deploying machine-learning inference on Intel hardware, giving cyber tools faster model execution without rewriting model code. backend support to aarch64aarch64The 64-bit execution state of the ARM architecture, maintained by Arm Ltd, used when compiling or running software on ARM-based hardware such as Apple Silicon or AWS Graviton servers., alongside packaging and API refinements.
The Triton Inference Server provides an optimized cloud and edge inferencing solution.
Triton v2.72.0 adds a log callback mechanism for embedding custom logging, introduces presets-file driven builds, and extends OpenVINOOpenVINOAn open-source toolkit from Intel for optimizing and deploying machine-learning inference on Intel hardware, giving cyber tools faster model execution without rewriting model code. backend support to aarch64aarch64The 64-bit execution state of the ARM architecture, maintained by Arm Ltd, used when compiling or running software on ARM-based hardware such as Apple Silicon or AWS Graviton servers., alongside packaging and API refinements.
└──▷ WHAT SHIPPED · 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Build presets via `--build-presets-file`NEW75how completely this was documenteddepth20/40specificity25/30actionability30/3075 / 100
Adds experimental build presets, allowing a build to be driven from a file via --build-presets-file instead of a long command line, e.g. python build.py --build-presets-file my_build_presets.json.
Drive a Triton build from a presets file instead of a long command line, useful in CI pipelines to keep build configuration version-controlled.
— Exact flag and runnable example command given.v2.72.0
02
Log callback APIs for embedding applicationsNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds a log callback option to the tritonserver C and Python APIs and to the common Logger, letting an embedding application route Triton log records into its own logging stack instead of a file or stream.
— Names the APIs affected but no exact function signature or example.v2.72.0
03
Improved model-readiness reportingIMPROVED65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Improves model-readiness reporting in TRITONSERVER_ServerModelIsReady — non-availability errors are now returned and unresolved models correctly report ready=false.
— Names the exact API and behaviour change, no example call.v2.72.0
thinner coverage below
04
ManyLinux early-access build assetsNEW55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
ManyLinux assets (early access) compiled against AlmaLinux 8.9 / manylinux_2_34, usable on RHEL 9 and later, with ensemble support.
— Names the build target and OS compatibility, no download steps.v2.72.0
05
OpenVINO model generation on aarch64NEW45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
Enables OpenVINO model generation on SBSA (aarch64) in the OpenVINO backend.
— States the capability but no usage detail or mechanism.v2.72.0
06
Unbounded grpcio requirement in Python clientIMPROVED45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
Removes the upper bound on the grpcio package requirement in the Python client, allowing installations to use current gRPC versions.
— Names the package but no version numbers or install steps.v2.72.0
RunPod Serverless introduces a tiered model caching system with locality-aware scheduling for Hugging Face models, alongside a new beta private Model Repository for version-pinned weight storage.
Explore our guides and examples to deploy your AI/ML application on Runpod. Review setup and usage guidance in the Runpod documentation.
RunPod Serverless introduces a tiered model caching system with locality-aware scheduling for Hugging Face models, alongside a new beta private Model Repository for version-pinned weight storage.
└──▷ WHAT SHIPPED · 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Tiered model caching with locality-aware scheduling in ServerlessNEW91how completely this was documenteddepth35/40specificity28/30actionability28/3091 / 100
Serverless endpoints can now select a Hugging Face model ID at configuration time, which triggers locality-aware scheduling that prefers hosts or network volumes already holding the model's bytes. Caching is tiered: host-local disk first, then a datacenter-scoped MooseFS network volume, then remote origin, with additional workers deferred until the shared cache copy is verified before scaling out. Explicit model version pinning via model@version makes which artifact version is serving traffic deterministic, and the cached files can be loaded offline from /runpod-volume/huggingface-cache/hub/ without a network download at startup.
Load a Hugging Face model in offline mode from the pre-cached path on a Serverless worker, avoiding any network download at startup.
python
import os
from pathlib import Path
from transformers import AutoModelForCausalLM, AutoTokenizer
org, name = "mistralai", "Mistral-7B-Instruct-v0.2"
cache_root = Path("/runpod-volume/huggingface-cache/hub")
snap_dir = sorted((cache_root / f"models--{org}--{name}" / "snapshots").iterdir())[-1]
tokenizer = AutoTokenizer.from_pretrained(str(snap_dir), local_files_only=True)
model = AutoModelForCausalLM.from_pretrained(str(snap_dir), local_files_only=True)
— Names cache path, tiering, pinning syntax, and includes runnable code.launch-20260828-94d3184f
thinner coverage below
02
Private Model Repository (beta)NEW32how completely this was documenteddepth15/40specificity12/30actionability5/3032 / 100
A private Model Repository, currently in beta and not yet publicly documented, adds version pinning and the ability to export model weights directly from a running pod into the repository.
Run, train, and serve open-source AI models on Together AI.
Together AI's most substantial window centered on a new tg batches CLI for batch inference and a beta billing usage API, alongside expanded fine-tuning tooling, a fully automatic node auto-repair policy, and new project and access-management controls.
└──▷ WHAT SHIPPED · 13 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Batch inference CLI (tg batches)NEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
New tg batches command group manages batch inference jobs: tg batches submit uploads a local JSONL file or existing file ID and creates a job against chat.completions, audio.transcriptions, or audio.translations; tg batches list, tg batches retrieve, and tg batches cancel (with ls and get aliases) manage the job lifecycle; tg batches download streams results to stdout or writes output and error files to disk with --output.
Fine-tuning CLI: model limits and tokenized dataset auditNEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
tg fine-tuning model-limits (alias tg ft model-limits) queries GET /fine-tunes/models/limits for a base model's capability flags and hyperparameter bounds, with --json for the full response body. tg ft download-tokenized-dataset <ft_id> downloads the tokenized dataset a job trained on for auditing; this is now surfaced in the tokenized_dataset_upload_complete event, visible in the console Events tab and via GET /fine-tunes/{id}/events.
Fully automatic node auto-repair policyNEW80how completely this was documenteddepth35/40specificity30/30actionability15/3080 / 100
A new fully automatic confirmation policy enables end-to-end unattended repair with per-fault scoping across fault groups (Migrate to new host, Reprovision, VM reboot) and job interruption controls (Wait for idle, Grace period, Maximum wait, Do not interrupt running jobs). Automatically approved repairs record Auto-Approved in the Reviewed by field.
Endpoint audit and lifecycle events in CLINEW75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
New tg beta endpoints events lists a dedicated endpoint's audit and lifecycle events — replica scaling, traffic shifts, status changes, and pauses — from the terminal.
File upload progress feedback in SDK and CLINEW70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
A new progress_callback parameter on client.files.upload() in the Python SDK receives upload progress events, and tg files upload and tg files check CLI commands now show a progress bar in interactive terminals.
Track fine-tune file upload progress in a script so long uploads don't appear to hang.
python
from together import Together
client = Together()
def on_progress(event):
print(f"Uploaded: {event}")
client.files.upload(file="dataset.jsonl", progress_callback=on_progress)
Model support: new fine-tuning models and expanded contextNEW55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
Fine-tuning support was added for Qwen/Qwen3.8-27B and zai-org/GLM-5.2, and zai-org/GLM-5.2 on serverless now accepts a 1,000,000-token context length, up from 512,000.
Vercel integration API key provisioningNEW55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Connecting a Vercel project from Integrations settings now creates a dedicated API key per linked Vercel project, set as the TOGETHER_API_KEY environment variable in that Vercel project.
Multi-project resource scopingNEW50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Multi-project resource scoping is now enabled for every organization: clusters, fine-tuned models, endpoints, evaluations, files, and API keys are fully scoped to projects.
ACH bank transfers for credit purchasesNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
ACH bank transfers are now available to all customers: link a U.S. bank account with instant verification from billing settings and purchase credits directly.
Legacy API key regenerationIMPROVED40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Legacy API keys can now be regenerated by any admin or editor of the default project; legacy keys appear in the API keys table with a Deprecated badge.
Bolt.new added prompt queuing that lets you line up to 20 build instructions while Bolt is still working, and replaced piecemeal teardown with one-step full project deletion.
Get help building with Bolt, an AI tool that turns your ideas into real websites and apps.
Bolt.new added prompt queuing that lets you line up to 20 build instructions while Bolt is still working, and replaced piecemeal teardown with one-step full project deletion.
└──▷ WHAT SHIPPED · 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
One-step project deletion with export and cleanup reportNEW81how completely this was documenteddepth32/40specificity24/30actionability25/3081 / 100
A unified one-step project deletion automatically disconnects custom domains, unpublishes the live site, deletes the Bolt database, and removes project files and chat history, removing the need for separate StackBlitz cleanup. It offers a pre-deletion export so you can keep a local copy, and reports any resources Bolt cannot clean up itself (such as an externally managed Supabase database or DNS records at another provider) for manual handling. In team projects, deletion is restricted to team Admins and the project Owner or Co-owners.
Fully tear down a project and reclaim all Bolt-managed resources in one action, with an export safety net before deletion.
📍In your Bolt project, open the project menu and choose Delete Project. When prompted, select Export to download a local copy, then confirm deletion. Bolt reports any external resources (e.g. a Supabase database or third-party DNS records) that you must remove manually.
— Lists exact steps, permissions, and edge cases; has a walkthrough example.snapshot-20260901
02
Prompt queue with up to 20 pending promptsNEW77how completely this was documenteddepth30/40specificity22/30actionability25/3077 / 100
Bolt now lets you queue up to 20 prompts while it is still building, with the ability to edit, reorder, or delete queued prompts and pause/resume the queue at any time. Each queued prompt preserves the agent it was submitted with, and in shared projects the queue shows per-prompt collaborator avatars so it's visible who submitted each pending prompt.
Queue your next build instructions before the current generation finishes, so Bolt works through them in order without manual waiting.
📍In your Bolt project chat, type your next prompt and press Send while Bolt is still building. The prompt appears in the queue below the active generation. To reorder, drag it above or below other queued prompts; to pause, click Pause in the queue panel.
— Names limit, UI actions and mechanism; has a runnable usage example.snapshot-20260901
Daytona 0.202.0 graduates sandbox forking and snapshot creation from experimental to stable API status.
Deploy Al code with confidence using Daytona
Daytona 0.202.0 graduates sandbox forking and snapshot creation from experimental to stable API status.
└──▷ WHAT SHIPPED · 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Stable API for sandbox fork and snapshot creationIMPROVED40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Promotes fork and create-snapshot operations to stable API, replacing the previous experimental aliases.
— Names the operations but no endpoint names or migration detail.snapshot-20260901
Command Code added a /learn CLI shortcut, visible warnings for invalid agent frontmatter, and DeepSeek V4 Flash Fast as a new model option.
The first AI coding agent that learns your coding taste. Powered by taste-1, a meta neuro-symbolic model.
Command Code added a /learn CLI shortcut, visible warnings for invalid agent frontmatter, and DeepSeek V4 Flash Fast as a new model option.
└──▷ WHAT SHIPPED · 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
`/learn` command in CLINEW65how completely this was documenteddepth15/40specificity20/30actionability30/3065 / 100
Adds a /learn command that opens the Command Code learn hub directly from the CLI, without leaving the terminal.
Jump straight to the Command Code learn hub without leaving your terminal.
$ /learn
— Named command with runnable example, but no further mechanismv1.38.2
thinner coverage below
02
Invalid agent frontmatter warnings in feedNEW35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Surfaces invalid agent frontmatter warnings on the feed so misconfigured agents are visible at a glance.
— Describes what changed but no config detail or stepsv1.38.2
03
DeepSeek V4 Flash Fast model supportNEW35how completely this was documenteddepth10/40specificity15/30actionability10/3035 / 100
Adds DeepSeek V4 Flash Fast as an available model option.
Lightweight coding agent that runs in your terminal
Codex CLI's two releases ship a breaking change that disables the planning tool by default, along with 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 cyber tools can expose capabilities directly to LLM-based agents. server controls (per-tool output limits, package-style server names), TUI upgrades (Vim-mode composer search, actionable rate-limit banners, credential-refresh progress), and expanded API/config surfaces for response usage metadata, paste-burst handling, and shell-command timeouts.
└──▷ WHAT SHIPPED · 7 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
`tui.disable_paste_burst` config keyIMPROVED75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
Adds tui.disable_paste_burst as the preferred configuration key under the [tui] section, with precedence over the legacy top-level disable_paste_burst key when both are present.
Move paste-burst suppression into the [tui] config block so it takes precedence over any legacy top-level setting.
toml
[tui]
disable_paste_burst = true
— Names both keys and precedence with a runnable config snippet.rust-v0.153.0-alpha.2
02
Planning tool disabled by defaultBREAKING70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
The planning tool (update_plan) is now disabled by default; existing setups relying on it must explicitly set tools.update_plan.enabled = true to restore the behavior.
Opt the planning tool back in after it is disabled by default in this release.
toml
tools.update_plan.enabled = true
— Exact config toggle given but tool's purpose left unexplained.rust-v0.152.0
03
Raw response usage metadata in notificationsIMPROVED65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Exposes the complete upstream response.usage object in ResponseUsageMetadata.metadata via rawResponse/completed notifications, alongside the existing amount field, with updated JSON and TypeScript schemas.
Vim-mode search in composer draftsNEW55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Adds Vim-mode / and ? search within composer drafts, with highlighted matches and repeat navigation via n and N.
— Keybindings given, a clear starting point for use.rust-v0.152.0
05
Configurable `thread/shellCommand` timeoutsIMPROVED50how completely this was documenteddepth15/40specificity20/30actionability15/3050 / 100
App-server clients can configure thread/shellCommand timeouts, including deadlines longer than one hour.
— Endpoint named but no config key or example given.rust-v0.152.0
06
Package-style MCP server namesIMPROVED45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
Supports package-style MCP server names containing :, @, /, and . throughout CLI commands and authentication.
— Character set named but no example command shown.rust-v0.152.0
07
Credential-refresh progress displayIMPROVED35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
Shows credential-refresh progress (including Amazon Bedrock reauthentication) in the terminal UI and codex exec.
— Describes the display but no interaction steps.rust-v0.152.0
└──▷ BREAKING ON UPGRADE
!The planning tool (update_plan) is disabled by default; existing setups relying on it must explicitly set tools.update_plan.enabled = true to restore the behavior.
Cline's desktop app picked up a redesigned Plugins/Marketplace hub, live model catalog refreshes spanning roughly 36 providers, and new session-management features letting agents hand off from local machines to Cline Cloud with SSH/Cloud environment selection.
Autonomous coding agent as an SDK, IDE extension, or CLI assistant.
Cline's desktop app picked up a redesigned Plugins/Marketplace hub, live model catalog refreshes spanning roughly 36 providers, and new session-management features letting agents hand off from local machines to Cline Cloud with SSH/Cloud environment selection.
└──▷ WHAT SHIPPED · 12 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Live model catalog and provider updatesBREAKING80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
The Cline provider model catalog now refreshes from the live feed so newly released models appear without waiting for an app update. This release adds new providers TokenGo and Volcengine Ark and updates model lists, pricing, and resolved default models for roughly 36 providers including Hugging Face, Mistral, OpenRouter, Together, NanoGPT, Requesty, Baseten, Cloudflare Workers AI, and DigitalOcean. If you use one of these providers without pinning a model, the resolved default model will change after upgrading.
— Names affected providers and the breaking default-model impact.desktop-v0.0.21
02
Provider auth error classificationIMPROVED65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Classifies provider HTTP 401/403 responses as authentication errors, making a bad or missing API key distinguishable from a provider outage.
— Names the status codes but no config toggle.desktop-v0.0.21
03
Streaming command output in desktop UIIMPROVED60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Streams run_commands output live to the desktop UI instead of buffering until completion.
— Names `run_commands` but no additional configuration.desktop-v0.0.21
thinner coverage below
04
Unified Plugins hub and two-pane MarketplaceNEW55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
Adds a two-pane Marketplace explorer: a browsable list on the left, full catalog metadata on the right, with collapsible category tag filters. Unifies Plugins, MCP, and Skills into a single Plugins hub with a dedicated Marketplace page.
— Describes new UI layout but no config keys.desktop-v0.0.21
05
Local-to-cloud session handoff and environment selectionNEW55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
Enables handing off local sessions to Cline Cloud, with recovery for interrupted transfers and preservation of the prompt, attachments, and session state. Adds environment selection between local, SSH remote, and Cloud from the desktop app.
Model tiers and web-search status in settingsNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Shows recommended and free model tiers in the composer model selector and in provider settings, with badges and descriptions, and displays provider web-search support status under the settings toggle.
— UI-only description with a clear settings location.desktop-v0.0.21
07
`code-onboarding-github` feature flagNEW50how completely this was documenteddepth15/40specificity20/30actionability15/3050 / 100
Adds the code-onboarding-github feature flag to gate the GitHub onboarding step, disabled by default.
!If you use one of the ~36 updated providers (including Hugging Face, Mistral, OpenRouter, Together, NanoGPT, Requesty, Baseten, Cloudflare Workers AI, or DigitalOcean) without pinning a model, the resolved default model will change after upgrading.
Crush v0.92.0 adds a configurable exit banner, letting users control how much is shown when the TUI closes.
└──▷ WHAT SHIPPED · 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Configurable exit banner verbosityNEW83how completely this was documenteddepth25/40specificity28/30actionability30/3083 / 100
Adds option ui exit-banner to .crushrc and options.tui.exit_banner to crush.json, supporting values compact, none, and default to control exit banner verbosity, useful for headless or low-context terminal workflows.
Reduce exit banner noise in headless or low-context terminal workflows by switching to compact mode in crush.json.
Herdr's single release in this window added per-mode visual theming and extended agent-state detection to the muse agent.
the runtime your coding agents live on
Herdr's single release in this window added per-mode visual theming and extended agent-state detection to the muse agent.
└──▷ WHAT SHIPPED · 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Per-mode theme overridesNEW35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Herdr now supports per-mode theme overrides, letting users configure distinct visual themes for each herdr mode via configuration.
DeepSeek Harness's alpha.3 release overhauls session navigation with a new turn rail and deep history paging, adds automatic issue start dates on PR open, extends image attachments, and removes SQLite-backed session persistence in a breaking change.
DeepSeek Harness: Everything is a Plugin.
DeepSeek Harness's alpha.3 release overhauls session navigation with a new turn rail and deep history paging, adds automatic issue start dates on PR open, extends image attachments, and removes SQLite-backed session persistence in a breaking change.
└──▷ WHAT SHIPPED · 4 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Session turn rail and deep history pagingNEW70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Adds a scrollable, fixed-pitch turn rail to the chat UI that lets practitioners jump to any turn in a long session and settles the view after paging completes. Adds loadThrough deep history paging to the session controller for navigating arbitrarily long session histories, whole-log turn outline projection with settled-response previews at card budgets for fast session scanning, and an identity-gated change feed to session projection for more precise incremental UI updates.
— Names mechanism and API but no exact user-facing commanddsh-v0.1.2-alpha.3
02
Extension-less image attachments via read_imageIMPROVED65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
read_image in tool-fs now accepts extension-less attachment paths, so image files without a file extension can be attached to agent turns.
SQLite persistence backend removedBREAKING65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
The SQLite persistence backend has been removed from dsh-session (refactor(session)!: remove SQLite persistence backend); any working setup relying on SQLite-backed session storage will break on upgrade.
!The SQLite persistence backend has been removed from dsh-session (refactor(session)!: remove SQLite persistence backend); any working setup relying on SQLite-backed session storage will break on upgrade.
Kiro is an agentic development environment that uses spec-driven workflows to plan, build, and maintain software.
Kiro Crew launched as an open-source, local-first agentic dev environment and shipped three fast follow-on releases that added Crew Mode's parallel sub-agents, a secrets vault, first-class Windows/Linux support, a diff-editing dashboard, and a rapidly growing App Store and messaging ecosystem (WhatsApp, iMessage, Feishu, and more).
└──▷ WHAT SHIPPED · 58 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Session management and navigation improvementsIMPROVED85how completely this was documenteddepth35/40specificity28/30actionability22/3085 / 100
Session search now spans every connected gateway, interleaving local and remote results — queries like 4411, /pull/4411, or owner/repo#4411 all find the same session — and sessions can be filtered by tag and assigned any custom hex color. A session summary side-panel tab explains what each thread was trying to do and where it landed, showing token cost before you enable it; the context window is visible as a percentage and token count as it fills; earlier chats resume in the background so the first message of a resumed session sends immediately. Session hand-off can send a session with its full context to another Kiro Crew instance, an interrupted turn can be resumed from any idle session, queued messages can be reordered before they send, and a live wait countdown lets you end a wait early.
Enable the session summary side panel and token-cost preview before turning on the feature, so you understand spend before committing.
📍In the dashboard, open the side-panel tab for a session › select 'Summary' › review the displayed token cost estimate › toggle the feature on.
MCP server management: aliasing, auth, and process sharingIMPROVED83how completely this was documenteddepth35/40specificity28/30actionability20/3083 / 100
MCP servers are discoverable, probeable, and enableable directly from the dashboard. A Measure action assesses whether a server can safely share a process by comparing tool sets, storing the verdict and displaying each server's evidence tier and run mode in MCP Management, replacing the old global sharing switch with per-server connection pooling probes. Registry aliases let tools from two servers that share the same name (e.g. Linear, Vercel, and GitHub) both remain usable without collision. Per-agent tool sets let you assign MCP servers to particular agents, authenticated custom MCP servers let you supply request headers when adding a remote server instead of hand-editing a config file, and a Reload action relaunches the agent process in place so newly added MCP servers and config take effect while the conversation survives.
Sandboxed execution and command policy controlsIMPROVED82how completely this was documenteddepth32/40specificity28/30actionability22/3082 / 100
An opt-in OS-level sandbox confines kiro-cli subprocesses on Linux and macOS, backed by 137 built-in denied-command patterns, credential redaction, and a two-level governance ceiling stored outside the agent's read/write scope. kirocrew policy show prints the built-in denied-command rules grouped by category, and custom deny notes let a refusal from a deny pattern carry an explanatory note.
Audit which commands the agent is blocked from running, before it discovers them by refusal.
Secrets vault with `secret://` referencesNEW80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
Kiro Crew introduces secret://NAME syntax for MCP server environment references, resolved from an encrypted vault at spawn time so secrets never sit in on-disk config. A new Settings > Secrets page keeps vault values masked, never sends them to the browser, and lets specific agents be denied access via a denylist.
Reference a stored vault secret in an MCP server's environment so the plaintext value is never written to disk config.
📍In Settings › Secrets, add a secret named MY_API_KEY, then reference it in your MCP server environment as:
MY_API_KEY: secret://MY_API_KEY
Messaging channel integrations: WhatsApp, iMessage, Feishu, and moreNEW78how completely this was documenteddepth32/40specificity28/30actionability18/3078 / 100
Bot integrations for Slack, Discord, Telegram, Microsoft Teams, Webex, WeCom, and WeChat all share the same agent memory and tool set. Three new channels are added: WhatsApp (link via QR code), iMessage (routed through Messages.app via a local macOS bridge, deny-by-default with an explicit allowlist), and Feishu (Lark); Teams, Telegram, and Webex reach feature parity with Slack, and Discord gains a nine-command slash menu with a model picker, runtime stats, and cron delivery. Telegram further gains a real command menu (type / for autocomplete, switch models with inline buttons, markdown tables render as tables) and attachment support for inbound images (vision), documents, and audio (transcribed on arrival).
App Store expands with new built-in appsNEW78how completely this was documenteddepth28/40specificity30/30actionability20/3078 / 100
An in-dashboard App Store launches with TypeScript and Python SDKs and six bundled apps including Auto Research, Code Review Sage, and Issue Radar, later joined by Personal Shopper (researches stores and recommends only when buying helps) and a Curated App Store Discover surface with editorial spotlights, themed collections, and category rails. Eight more opt-in apps follow: Spec Builder, Ops Mission Control, Auto-Improvement, Meetings (live transcription), Papyrus (LaTeX editor), Mochi, Crew Companion, and PPTX Maker (generates real .pptx files from chat descriptions); Code Review Sage separately gains support for GitHub Enterprise Server hosts.
Install and launch the PPTX Maker app to generate a PowerPoint deck from a chat description.
📍In the dashboard, open the App Store, locate PPTX Maker, click Install, then Enable. Open the command palette, search for 'PPTX Maker', and launch it. Describe your deck in the chat to receive a real .pptx file.
kirocrew CLI utility commands: tailnet, cloud logout, Slack setupNEW77how completely this was documenteddepth24/40specificity25/30actionability28/3077 / 100
kirocrew tailnet up publishes the dashboard on a Tailscale network; kirocrew cloud logout ends the current cloud sign-in session; and kirocrew setup --slack requests Slack credentials on demand so kirocrew setup can finish on the dashboard without requiring Slack tokens upfront.
Expose your local Kiro dashboard to teammates on a shared Tailscale network without any additional tunnel setup.
$ kirocrew tailnet up
Run Kiro Crew setup without being prompted for Slack — then add Slack credentials separately only when needed.
$ kirocrew setup
# Later, when you want Slack integration:
kirocrew setup --slack
Computer Use expands to WindowsIMPROVED76how completely this was documenteddepth32/40specificity22/30actionability22/3076 / 100
Computer Use via UI Automation is no longer macOS-only — Kiro Crew can now read and drive native Windows applications, with the Windows agent tree running under a Job-object process and memory ceiling mirroring the existing Linux control. Computer Use itself lets the agent operate native apps through the accessibility layer (press buttons, fill fields, scroll, drag), is off by default, writes every call to an audit log, and is enabled via Settings > Computer Use.
Enable Computer Use so the agent can operate native macOS apps via the accessibility layer.
📍In the Kiro Crew dashboard, go to Settings › Computer Use and toggle Computer Use on.
`kirocrew run` for long-running autonomous tasksNEW75how completely this was documenteddepth28/40specificity22/30actionability25/3075 / 100
kirocrew run TASK.md hands the agent a spec for autonomous decomposition, execution, testing, and retry over 10+ hour runs, with disk checkpoints for crash recovery.
Hand the agent a spec file for a long-running autonomous task that survives crashes via disk checkpoints.
Telegram becomes single-account, configured via `telegram.bot_token`BREAKING72how completely this was documenteddepth22/40specificity25/30actionability25/3072 / 100
Telegram is now single-account only; the bot token is configured via telegram.bot_token, only one bot token is served per install, and the existing multi-account map is no longer read.
Configure a Telegram bot token for the single-account Telegram integration after upgrading from a multi-account setup.
Crew Mode and steerable parallel sub-agentsIMPROVED70how completely this was documenteddepth28/40specificity22/30actionability20/3070 / 100
kirocrew spawn run splits work across parallel sub-agents for concurrent execution; Crew Mode lets the agent dispatch topics to parallel sub-sessions that return answers independently so multiple work threads advance simultaneously; and sub-agents are now steerable with queued follow-ups, scoped to task-specific context, with completions reported as cards in chat.
Fan out a large task across multiple parallel sub-agents to complete work faster.
Boot and startup performance improvementsIMPROVED70how completely this was documenteddepth30/40specificity30/30actionability10/3070 / 100
Boot uses approximately 875 MB less memory because the embedding model now loads on first real use instead of at startup; kirocrew CLI startup drops from 1.3 s / 112 MB to 0.5 s / 54 MB; and sandboxed spawns are approximately 1.45 seconds faster each.
Voice input and speech featuresIMPROVED70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Adds live streaming speech-to-text, voice memo transcription on arrival, and local Piper text-to-speech with no cloud round-trip; on-device Apple speech-to-text voice input follows with live streaming, microphone switching mid-recording, and dictation landing at the cursor; push-to-talk lets you hold a key to dictate or tap to latch it on, with key, mode, and a live test strip configurable in Settings; and a local Parakeet speech-to-text provider running on Apple Silicon (faster than Whisper) is added, with Escape now stopping the assistant from speaking.
Issue Radar autonomous issue triageIMPROVED70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Issue Radar assigns autonomous workers to claimed issues, each in its own worktree with a public claim ledger and a pull request; it now also covers Azure DevOps repositories and work items alongside GitHub and GitLab, adding dependency edges, an unblocked-dependency signal, and a Focus Tree graph.
Agent-driven browser automation in dashboardIMPROVED68how completely this was documenteddepth30/40specificity20/30actionability18/3068 / 100
Browser automation was introduced via Playwright for navigation, form filling, and screenshots, then exposed through a Persistent Browser Mode Settings toggle that streams a live view into the dashboard's Browser panel, and finally made agent-driven so the agent directly navigates, clicks, types, and screenshots inside the panel (with native desktop Computer Use also offered on macOS).
Enable the agent to control a real browser for form-filling, navigation, and web automation tasks.
📍In the dashboard, go to Settings and flip the Persistent Browser Mode toggle on. The Browser panel will appear in the dashboard showing a live view of the agent's browser session.
Expanded platform support: Windows, Linux ARM64, managed PythonNEW64how completely this was documenteddepth24/40specificity22/30actionability18/3064 / 100
Native Linux ARM64 build lands and Windows becomes a first-class target alongside macOS and Linux x86; a new --managed-python installer flag provisions a pinned interpreter on hosts whose system Python is too old.
Artifacts: versioned documents, code, and deployable webappsIMPROVED63how completely this was documenteddepth26/40specificity22/30actionability15/3063 / 100
Artifacts are versioned documents, code, and interactive widgets deployable as a webapp to an AWS account with a public HTTPS link and configurable TTL; screenshots and diagrams produced by the agent are also preserved as artifacts, with a gallery and detail page.
Knowledge search and graph view enhancementsIMPROVED62how completely this was documenteddepth25/40specificity22/30actionability15/3062 / 100
Knowledge search gains a source filter with source discovery, and the graph view adds a source dropdown, a physics-based layout, community clustering, and an adjustable depth control.
Code-editing dashboard with diff viewNEW61how completely this was documenteddepth26/40specificity20/30actionability15/3061 / 100
The dashboard transcript gains side-by-side diff rendering, per-file inline editing, and a project file tree in the side panel; file edits made by a tool now render as always-visible diff cards.
Terminal panel enhancementsIMPROVED60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
The terminal was promoted to an app-wide dock tab with a searchable, previewed font picker that detects local fonts; it then gained docking to bottom or right, opening in the session's own project directory with the preferred shell; and finally gained the ability to pop out into its own window, complete subcommands and flags (not just paths), and accept a configurable font.
`.kiroignore` support and document auto-ingestIMPROVED57how completely this was documenteddepth20/40specificity22/30actionability15/3057 / 100
The knowledge library now honors a .kiroignore file, automatically adds documents and dedupes them per document, and shows per-injection context cost on a new Skills budget screen.
Git panel and inline issue links in dashboardNEW57how completely this was documenteddepth22/40specificity20/30actionability15/3057 / 100
The dashboard gains a Git panel showing repository status and commit log, plus a dockable side panel (bottom or right); GitHub, GitLab, and Jira links now render inline as chips in the dashboard.
Cron-based job schedulingIMPROVED56how completely this was documenteddepth24/40specificity20/30actionability12/3056 / 100
Adds cron-based scheduling for recurring agent jobs; a later update adds a template gallery of 15 presets, groups cron jobs into collapsible folders, and lets monitoring loops accept a wall-clock runtime budget.
App permission scoping and trust grantsIMPROVED55how completely this was documenteddepth25/40specificity18/30actionability12/3055 / 100
Installed apps now receive only the event scopes their manifest declares and can no longer observe other apps' activity; per-app trust grants extend this so third-party apps run under scoped permissions, with denial messages that explain the required action.
Node.js 22 minimum requirementBREAKING55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Node.js 22 is now the minimum supported version (24 LTS recommended); a Node 20 install is refused up front rather than failing partway through a build.
Inline preview for video, audio, spreadsheets, and notebooksNEW55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
Adds inline preview support for video, audio, XLSX spreadsheets (with sheet tabs), and notebooks (embedded images, highlighted code, Mermaid diagrams).
Service install and remote SSH managementNEW55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Supports installation as a systemd or launchd service for always-on operation, with management of multiple remote instances over SSH from a single hub.
Distribution channels and release switchingIMPROVED54how completely this was documenteddepth20/40specificity22/30actionability12/3054 / 100
Available as a signed macOS DMG, Linux AppImage, multi-arch Docker image, or pip wheel, across stable, insider, and nightly release channels; you can switch release channels without reinstalling.
`kirocrew chat` terminal commandNEW53how completely this was documenteddepth18/40specificity15/30actionability20/3053 / 100
kirocrew chat lets you chat with the agent from a terminal CLI, sharing the same memory and tools as the web dashboard, desktop app, and messaging-platform bots.
Interface localization expands to twelve languagesIMPROVED53how completely this was documenteddepth20/40specificity25/30actionability8/3053 / 100
Supports ten interface languages at launch (English, German, Spanish, French, Italian, Portuguese, Russian, Hindi, Bengali, and Chinese); Korean and Japanese are added next, bringing the total to twelve, with correct rendering of bold, italic, and strikethrough in CJK prose.
Per-role model and reasoning effort configurationNEW50how completely this was documenteddepth20/40specificity18/30actionability12/3050 / 100
Adds a configurable per-role model and reasoning effort for background and sub-agent work via the model picker, which also shows each model's credit multiplier.
Skills workflows, now project-localIMPROVED49how completely this was documenteddepth22/40specificity15/30actionability12/3049 / 100
Skills are plain Markdown files that teach the agent a workflow with no code and no rebuild required; Kiro Crew can now also load a project's own skills, gated behind per-directory consent.
Terminal output no longer scanned for credentialsBREAKING45how completely this was documenteddepth22/40specificity15/30actionability8/3045 / 100
Terminal output now passes through untouched rather than being scanned for credentials; this fixes previous corruption of CJK text and emoji, but any credential-scanning logic that relied on the old scanning no longer runs.
!Node.js 22 is now the minimum (24 LTS recommended); a Node 20 install is refused up front rather than failing partway through a build.
!Telegram is single-account only; move the token you want to keep to telegram.bot_token — the existing account map is no longer read.
!kirocrew logout now revokes refresh tokens, ending the session everywhere rather than only locally.
!Terminal output is no longer scanned for credentials; output now passes through untouched (CJK text and emoji are no longer corrupted, but any credential-scanning logic that relied on this behaviour no longer runs).
!Knowledge auto-ingest is opt-in; a fresh install ingests nothing until explicitly enabled.
vMLX's biggest changes this window are native GLM-5.3 multimodal support and default-on GLM KDA decode fusions with a compact GLM MLA cache path for faster GLM inference, backed by a broader set of MTP/speculative-decoding safety controls and more reliable multi-turn tool-use sessions.
vMLX - Use MLX models easily - JANGQ (GGUF for MLX) - Not dependant on mlx_vlm
vMLX's biggest changes this window are native GLM-5.3 multimodal support and default-on GLM KDA decode fusions with a compact GLM MLA cache path for faster GLM inference, backed by a broader set of MTP/speculative-decoding safety controls and more reliable multi-turn tool-use sessions.
└──▷ WHAT SHIPPED · 8 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
MTP detection and speculative-decoding controlsNEW60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
Detects native MTP (Multi-Token Prediction) artifacts in supplemental weight shards, keeping speculative/cache settings explicit and model-safe. Adds separate adaptive MTP profiles for tool workloads, prototypes a proposal-only Qwen MTP head, adds sampled controls to the native MTP benchmark, defaults GLM native MTP to autoregressive with a measured-cost fallback of text MTP to AR, attributes MTP verifier acceleration per request, and gates GLM verifier slab fusions behind an opt-in flag.
— Describes behaviors but no named flags or commands to invoke.v1.6.49v1.6.51
02
Tool-use session reliability across turnsIMPROVED60how completely this was documenteddepth30/40specificity20/30actionability10/3060 / 100
Persists parsed tool turns before publishing terminals and reconstructs stable tool contracts across turns, improving reliability of tool-use sessions in multi-turn conversations. Drains terminalizing tool requests without aborting so in-flight tool calls complete cleanly on session teardown, holds tool terminals until cache persistence completes to keep native Qwen tool prompts stable across continuations, and adds a stable auto tool policy to agentic cache proof, modeling stable Responses instructions.
— Clear mechanism described but nothing a reader can directly invoke.v1.6.49v1.6.50
03
Compact GLM MLA cache pathIMPROVED60how completely this was documenteddepth30/40specificity20/30actionability10/3060 / 100
Adds an opt-in compact GLM MLA cache path, now advertised as the GLM family default, with amortized appends and active schema reported from runtime.
— Mechanism and default status given, but opt-in flag itself unnamed.v1.6.49
thinner coverage below
04
Default GLM KDA decode fusionsIMPROVED55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Enables qualified GLM KDA decode fusions by default, improving decode throughput for GLM-4/5 models without any configuration change.
— Names models and behavior change but no config surface to act on.v1.6.50
05
GLM-5.3 multimodal runtimeNEW55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Adds a native GLM-5.3 multimodal (VLM) runtime with support for GLM multimodal sessions in the panel.
— Names the model and UI surface but not exact steps.v1.6.49
06
Atomic mixed-layout Qwen4 MoE decodeIMPROVED50how completely this was documenteddepth25/40specificity20/30actionability5/3050 / 100
Keeps mixed-layout Qwen4 MoE decode atomic, preventing state corruption when decoding with heterogeneous expert layouts.
— Explains fix and cause but is an internal, non-actionable change.v1.6.50
07
BF16 support in routed decode fusionNEW25how completely this was documenteddepth10/40specificity15/30actionability0/3025 / 100
Supports BF16 affine metadata and BF16 activations in routed decode fusion.
— Bare one-line mention with no further mechanism or usage detail.v1.6.49
08
Subfolder-backed image model artifactsNEW25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Supports subfolder-backed image model artifacts.
— Single-line feature with no path, format, or usage detail given.v1.6.49
PydanticAI expanded its model support this window by adding the glm-5.3-flash model via the Z.AI integration.
How Python does AI. Agents, realtime voice, image generation, embeddings.
PydanticAI expanded its model support this window by adding the glm-5.3-flash model via the Z.AI integration.
└──▷ WHAT SHIPPED · 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
glm-5.3-flash model support via Z.AINEW45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
PydanticAI added glm-5.3-flash to the Z.AI model roster, expanding the set of supported models available for use.
— Names the model and integration but gives no usage example.v2.37.0
Hermes shipped a major release (v0.21.0) adding Bot Mode group chats, live subagent steering, memory-persistent cron jobs, an MCP command center, and in-app browser automation, alongside doc updates introducing a turn-liveness watchdog and async peer task execution with idempotency support.
└──▷ WHAT SHIPPED · 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.
01
Turn liveness watchdog for stuck conversation turnsNEW89how completely this was documenteddepth35/40specificity28/30actionability26/3089 / 100
Adds agent.turn_liveness configuration block with timeout_s (default 600.0) and poll_s (default 15.0) to bound how long a turn may show zero observable progress — streaming tokens, tool heartbeats, and approval waits all count as progress — before Hermes force-recovers it. Invalid values (NaN, Inf, non-positive poll_s) log a warning and fall back to defaults instead of crashing startup; setting timeout_s to a non-positive value explicitly disables the watchdog.
Tighten the wedge timeout to 5 minutes and increase poll frequency to catch stuck sessions faster in a high-throughput environment.
yaml
turn_liveness:
timeout_s: 300.0 # fire after 5 min of zero progress
poll_s: 10.0 # check every 10 seconds
— Names exact config keys, defaults, and fallback behavior with a runnable example.product docs
02
Async peer task execution and bot-to-bot messagingNEW88how completely this was documenteddepth32/40specificity28/30actionability28/3088 / 100
Adds hermes peer CLI subcommand for bot-to-bot direct messaging between agents across profiles and gateways, with replies landing in each agent's durable Bot Chat. Includes peer run <bot> --idempotency-key <key> to launch a long-running bot task asynchronously and return a run_id immediately instead of blocking, peer status <bot> <run_id> to poll an in-progress run, and peer stop <bot> <run_id> to interrupt a specific run without affecting other turns; the --idempotency-key flag makes retries return the original run rather than spawning duplicate work.
Launch a long-running task against the 'spark' bot in CI without blocking — use the idempotency key so a retry on failure returns the original run instead of starting duplicate work.
$ hermes peer run spark --idempotency-key ticket-123 /tmp/long-task.txt
Poll a running task to check whether it has finished before taking a downstream action.
$ hermes peer status spark run_abc123
Interrupt an in-progress run precisely by its run ID to avoid accidentally stopping a different active turn.
$ hermes peer stop spark run_abc123
Send a task from one agent to another by handle so findings from a research bot are handed off to a coding bot automatically.
$ hermes peer @coding-bot 'Here are the API surface findings from last night — please draft the integration sketch'
— Every subcommand and flag is named with runnable examples.v2026.8.31
03
Browser automation with Lightpanda engine supportNEW83how completely this was documenteddepth30/40specificity28/30actionability25/3083 / 100
Adds browser.engine: lightpanda support in Browser Use mode — _resolve_backend_cdp() now reads the setting and spawns Lightpanda automatically when no higher-precedence backend is active. Also adds in-app browser automation: the agent can navigate, click, and read the desktop's built-in browser directly, with pages poppable to the system browser.
Force the in-app browser to use Lightpanda instead of Chrome for all Browser Use sessions.
yaml
browser:
engine: lightpanda
— Names config key, internal function, and a runnable config example.v2026.8.31
04
delegate_task live steering, validation and higher limitsIMPROVED78how completely this was documenteddepth32/40specificity28/30actionability18/3078 / 100
Adds live steering to delegate_task: list running child agents, send mid-flight course corrections, or stop a child early and retain its partial result. Also adds optional JSON-schema validation on delegate_task child outputs, per-delegation cost reporting in results, and raises defaults to 250 iterations and 10 concurrent children.
— Names the function, new limits, and validation mechanism with no example.v2026.8.31
05
MCP command center: deep links, dashboard, health checksNEW74how completely this was documenteddepth28/40specificity28/30actionability18/3074 / 100
Adds a hermes:// deep-link scheme for installing MCP servers with explicit user confirmation, plus an MCP command-center dashboard with drag-in "paste anything" import, background health checks with re-auth nudges, and a fleet cost/usage overlay showing schema token estimates and 30-day usage per server.
— Names the scheme and dashboard capabilities but no example.v2026.8.31
06
Cron job continuity, memory, and Bot Chat routingIMPROVED72how completely this was documenteddepth30/40specificity24/30actionability18/3072 / 100
Adds a continuity=true flag for cron jobs so each run's output is carried into the next, enabling deduplication across scheduled agent runs. Cron agents now load and update persistent memory and receive a durable notepad scratchpad; monitor-mode jobs skip the LLM when nothing changed. Cron output can also be routed into a bot's canonical Bot Chat so the bot responds to scheduled job results.
— Names the flag and mechanism but no example of use.v2026.8.31
07
New model providers and catalog expansionNEW68how completely this was documenteddepth24/40specificity30/30actionability14/3068 / 100
Adds six new built-in providers: Meta Model API (Muse Spark), CommandCode (GOAT/Pro/Max plans), Tencent TokenPlan, Nebius Token Factory, Ramp Router, and Actual Computer. Also expands the model catalog with GLM-5.3-Flash, qwen3.8-max, qwen3.8-flash, Gemini 3.7 Flash, MiniMax M3 free, and Nemotron 3.5 Lightning.
— Every provider and model is named, but no usage steps given.v2026.8.31
08
Desktop CLI UX additions: status, model picker, palette, controlsNEW60how completely this was documenteddepth18/40specificity24/30actionability18/3060 / 100
Adds /status CLI command showing reasoning mode, pending approvals, and context usage; /model picker with live filtering as you type; a Ctrl+P fuzzy command palette; and global emergency stop plus session pin/unpin controls to the desktop CLI.
— Names each surface but no examples or navigation detail.v2026.8.31
thinner coverage below
09
model_overrides config keyNEW58how completely this was documenteddepth20/40specificity20/30actionability18/3058 / 100
Adds model_overrides config key to patch any model's context window, pricing, or capabilities without waiting on a release.
— Names the config key but gives no file path or example.v2026.8.31
10
Bot Mode group chats and cross-gateway linkingNEW55how completely this was documenteddepth25/40specificity18/30actionability12/3055 / 100
Adds Bot Mode as a bundled, default-on desktop feature: named agent profiles with deterministic avatar faces, a shared roster, Discord-style group chats, and @-mention support from the composer. Documents one-way NAT reachability constraints for cross-gateway Group Chat links: authority for a shared room must live on a host reachable by all participants (e.g. a public VPS), with Tailscale/VPN as a bridging option.
— Describes the feature and a networking caveat but no config surface.v2026.8.31
11
Pip-installed model provider discovery via entry pointsNEW54how completely this was documenteddepth22/40specificity18/30actionability14/3054 / 100
Adds pip-installed model provider discovery via Python entry points, allowing third parties to ship model providers as packages.
— Explains the mechanism but gives no package or entry-point name.v2026.8.31
12
Write-approval enforcement on standing-order filesNEW54how completely this was documenteddepth24/40specificity20/30actionability10/3054 / 100
Adds write-approval enforcement on AGENTS.md, skills, and memory stores so a prompt-injected agent cannot silently rewrite its own standing orders.
— Names the protected files and threat model but no config toggle.v2026.8.31
13
Verify subsystem for build/test claimsNEW50how completely this was documenteddepth24/40specificity16/30actionability10/3050 / 100
Adds Verify subsystem with run-recipe detection and environment manifest to back "it works" claims with detected build/test commands.
— Describes purpose and mechanism at a high level only.v2026.8.31
14
Prompt caching for LiteLLM Claude and Meta routingIMPROVED50how completely this was documenteddepth18/40specificity22/30actionability10/3050 / 100
Adds prompt caching for LiteLLM Claude on the OpenAI wire and routes api.meta.ai through the Responses API for caching.
— Names the routing target but no config or measurable effect.v2026.8.31
15
Context compression improvements and cache spilloverIMPROVED50how completely this was documenteddepth22/40specificity18/30actionability10/3050 / 100
Adds a lean tail compression mode plus a compaction recall eval harness to measure what context compression actually preserves. Oversized tool results now spill to cache instead of being truncated in sandbox-less sessions.
— Explains behavior change but no config key or example.v2026.8.31
16
Status bar live performance metricsNEW48how completely this was documenteddepth18/40specificity18/30actionability12/3048 / 100
Adds status bar display of live cache-hit %, latency, and tokens/sec with per-field toggles.
— Names the metrics shown but no config or navigation detail.v2026.8.31
17
Buzz adapter message editing and deletionNEW48how completely this was documenteddepth18/40specificity20/30actionability10/3048 / 100
Adds edit_message and delete_message capabilities to the Buzz adapter so replies can stream.
— Names the two capabilities but no usage example.v2026.8.31
18
Deep redaction sweep for secret leaksIMPROVED46how completely this was documenteddepth18/40specificity20/30actionability8/3046 / 100
Adds a deep redaction sweep closing secret-leak gaps across terminal errors, .env file reads, checkpoints, and ACP logs.
— Names the leak surfaces covered but no mechanism detail.v2026.8.31
19
clarify tool for multi-question promptsNEW43how completely this was documenteddepth18/40specificity15/30actionability10/3043 / 100
Adds clarify tool support for asking multiple independent questions in a single call instead of sequential round-trips.
— Names the tool but no example of its call shape.v2026.8.31
20
Data-training-tier warnings across model pickersNEW42how completely this was documenteddepth18/40specificity16/30actionability8/3042 / 100
Adds data-training-tier warnings via a unified selection-guard registry that alerts across every model-picker surface when a model trains on your data.
— Describes the mechanism briefly but no concrete surface to act on.v2026.8.31
Beelzebub v3.9.1 adds method-aware HTTP routing to its deception service, making the honeypot harder for scanners to fingerprint.
A secure low code deception runtime framework, leveraging AI for System Virtualization.
Beelzebub v3.9.1 adds method-aware HTTP routing to its deception service, making the honeypot harder for scanners to fingerprint.
└──▷ WHAT SHIPPED · 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Method-aware routing in HTTP honeypotIMPROVED35how completely this was documenteddepth20/40specificity10/30actionability5/3035 / 100
The HTTP deception service now routes and responds differently based on HTTP method, reducing the fingerprinting surface that attackers and scanners can use to detect the honeypot.
— Explains mechanism but no config keys or examples given.v3.9.1
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 shipped its v1.0 line with a fail-closed background daemon and live-hook enforcement across twelve agent CLIs, digest-verified and observe-mode policy packs with a Recommended 15-policy setup, a full failproofai audit command family with scheduling and email digests, Cloud enrolment and pause controls via failproofai config, and new lifecycle commands (update, migrate, uninstall, backfill, harness add-path), alongside breaking removals of older auth and email-upload commands.
└──▷ WHAT SHIPPED · 14 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Local and scheduled audit via `failproofai audit`NEW96how completely this was documenteddepth38/40specificity30/30actionability28/3096 / 100
failproofai audit inspects supported agent history locally and opens findings at http://localhost:8020/audit, keeping all analysis on-machine; failproofai audit --scheduled runs headless local scans with [audit] auto off by default because the scan reads transcript contents. failproofai audit --schedule [days] --email <address> puts the audit on a recurring timer (interval 1-90 days, default 7) and emails digests with counts and redacted examples only plus the machine name, entirely from the terminal; failproofai audit --no-schedule cancels the schedule without signing out, and failproofai audit --status reports scheduling state, report destination, daemon health and next scan time, now also surfacing collector-reported delivery failures such as revoked or expired keys. A /settings dashboard page, reached via the gear icon in the header, configures scheduled audits from the UI and is server-rendered from config; it shares the same updateConfig path and session file as the CLI so changes from either surface are immediately consistent. Audit files now reside under ~/.failproofai/audit/, migrated automatically on first run, with the session file kept at 0600 mode.
Set a headless CI runner or detached server to audit itself weekly and email findings without any browser interaction.
Check whether scheduled auditing is active, where reports are going, and when the next scan is due on a machine you have SSH'd into.
$ failproofai audit --status
Disable scheduled audits on a box without losing your signed-in session.
$ failproofai audit --no-schedule
— Full command surface with flags, paths and runnable examplesv1.0.2v1.0.1v1.0.0
02
Cloud enrolment and enforcement control via `failproofai config`NEW93how completely this was documenteddepth35/40specificity30/30actionability28/3093 / 100
failproofai config --connect <url> --token <key> enrols a machine in FailproofAI Cloud in one step, sharing one credential and URL for both policy pull and event ingest. failproofai config --disconnect fully severs Cloud enrolment: the daemon reads mode: "oss" and goes silent, clearing the active manifest so no deployment policy keeps enforcing. failproofai config --pause / --resume gives time-boxed suspension of enforcement for one session, with a hard 8-hour ceiling on any unbroken stretch. failproofai config --token <machine-key> supports non-interactive Cloud setup, and setting the FAILPROOFAI_CLOUD_TOKEN environment variable then running failproofai config keeps the key out of command history. On Windows, failproofai config now exits 1 with an explanatory message before writing anything, rather than completing setup with a weaker enforcement guarantee.
Connect to FailproofAI Cloud non-interactively in CI by passing the machine key as an environment variable so it never appears in command history.
— Every flag and env var named with a runnable examplev1.0.2v1.0.0
03
Machine lifecycle commands: update, migrate, uninstall, backfill, harness pathsNEW93how completely this was documenteddepth35/40specificity30/30actionability28/3093 / 100
failproofai update completes the upgrade npm cannot do: it runs pending home migrations, installs the matching failproofaid binary, and restarts the service — running npm install -g failproofai@latest alone is insufficient, since ~/.failproofai/ and the daemon binary are not updated without it. failproofai migrate [--dry-run] runs the home migration alone or previews the plan without making changes, recording applied steps in migrations/applied.json and backing up irreplaceable files to ~/.failproofai/migrations/backup-layout<n>/ first. failproofai uninstall [--purge] is the sanctioned removal path, removing hook entries in every CLI and the root-owned unit, and optionally ~/.failproofai. failproofai backfill [--since 30d] re-sends history the collector has already read past, useful after re-enrolment or a cleared dashboard. failproofai harness add-path registers extra capture paths per harness for homes and gateways that live off the default roots.
Preview a home migration before committing to it — useful before any major upgrade.
$ failproofai migrate --dry-run
Re-send the last 30 days of history after re-enrolling a machine whose dashboard was cleared.
$ failproofai backfill --since 30d
— Five commands with flags, files and runnable examplesv1.0.0
04
Recommended setup with named 15-policy setNEW73how completely this was documenteddepth28/40specificity27/30actionability18/3073 / 100
Adds a Recommended setup path in failproofai config that auto-detects installed CLIs and selects a named 15-policy set (including block-rm-rf, block-force-push, and block-secrets-write); it unions with existing enabled policies so it cannot reduce existing protection.
— Names policies and command, clear entry point via configv1.0.0
05
Fail-closed background enforcement daemonNEW72how completely this was documenteddepth32/40specificity28/30actionability12/3072 / 100
A background daemon (failproofaid) is installed as a systemd unit at /etc/systemd/system/failproofaid@<user>.service on Linux or a launchd LaunchDaemon on macOS; on a configured machine, if the daemon is unreachable, enforcement is denied rather than falling back to in-process evaluation.
— Names install paths and fail-closed rule but no user commandv1.0.0
06
Live-hook enforcement on twelve agent CLIsNEW72how completely this was documenteddepth30/40specificity30/30actionability12/3072 / 100
Adds live-hook enforcement on twelve agent CLIs: Claude Code, Codex, Copilot CLI, Cursor, OpenCode, Pi, Hermes, OpenClaw, Factory (droid), Devin, Antigravity (agy), and Goose, each verified live against that CLI's own hook contract and a named version. VS Code Copilot Chat agent mode gains enforcement for free by loading the same .github/hooks/*.json and ~/.claude/settings.json files already written by the copilot and claude installs, and documentation now covers enforcement differences across all twelve harnesses.
— Names every harness but integration is automatic, not a commandv1.0.2v1.0.0
07
`audit.auto` no longer implies upload consentBREAKING65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
Machines that had audit.auto: true set under v1.0.0 continue scanning locally on upgrade but will not send email digests until explicitly opted in again, because audit.auto no longer implies upload consent. Run failproofai audit --schedule <days> --email <address> to re-enable digests.
— Names the config key, impact, and the exact remediation commandv1.0.1
08
`policies` command for explicit pack selectionIMPROVED62how completely this was documenteddepth15/40specificity22/30actionability25/3062 / 100
Promotes policies as the main CLI noun; use failproofai policies add <pack> to explicitly choose which policy packs run.
— Runnable command named, but little else explainedv1.0.2
09
Publish verification and private-repo safeguardsIMPROVED61how completely this was documenteddepth26/40specificity20/30actionability15/3061 / 100
failproofai publish now verifies every bundled source against the named release commit, including imported helpers, ignored files, renamed files, and symlinked paths. Publishing to an existing private repository is refused by default, preventing installation of packs that cannot fetch private release assets.
— Clear mechanism for a named command, no example givenv1.0.2
10
Expanded `block-failproofai-commands` guardIMPROVED60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
The always-on block-failproofai-commands guard now catches shell globs, interpreters, variables, loops, pipes, and agent-native Write, Edit, and NotebookEdit operations targeting ~/.failproofai.
— Names guard and operations covered, but automatic not actionablev1.0.2
thinner coverage below
11
Digest-verified policy packsNEW58how completely this was documenteddepth28/40specificity22/30actionability8/3058 / 100
Policy packs are pinned to their artifact digest and source commit; if a pack cannot be verified, enforcement is denied only within that pack's declared scope instead of silently dropped. Cloud-managed policies are likewise content-addressed and digest-verified immediately before import.
— Clear mechanism, no user-facing command to invoke itv1.0.2v1.0.0
12
Observe mode for policy rolloutNEW58how completely this was documenteddepth28/40specificity18/30actionability12/3058 / 100
Introduces observe mode: policies can be evaluated and their verdicts recorded without blocking the agent, available for locally published packs and Cloud deployments, with results inspectable through policy activity or FailproofAI Cloud. Cloud-managed policies support an observe effect for this observe-before-enforce step of a rollout.
— Describes behavior and rollout use but no exact toggle shownv1.0.2v1.0.0
13
Cloud auth and audit upload commands removedBREAKING57how completely this was documenteddepth25/40specificity22/30actionability10/3057 / 100
failproofai auth login, failproofai auth logout, and failproofai auth whoami are removed; Cloud sign-in now goes through the local dashboard. config --email / --no-email and the counters-only upload POSTed by the scheduled scan are also removed; audit is now a local-only operation with no network call.
— Names removed commands and replacement path clearlyv1.0.0
14
Cloud decision attribution fieldsNEW46how completely this was documenteddepth18/40specificity20/30actionability8/3046 / 100
Every Cloud decision now carries policySource, cloudPolicyId, and deployment attribution so the dashboard can answer what a centrally-managed policy actually did.
— Named fields but no way to query them directly givenv1.0.0
└──▷ BREAKING ON UPGRADE
!Machines that had audit.auto: true set under v1.0.0 will continue scanning locally on upgrade but will not send email digests until you explicitly opt in again, because audit.auto no longer implies upload consent. Run failproofai audit --schedule <days> --email <address> to re-enable digests.
!failproofai auth login, failproofai auth logout, and failproofai auth whoami are removed; Cloud sign-in now goes through the local dashboard.
!config --email / --no-email and the counters-only upload POSTed by the scheduled scan are removed; audit is now a local-only operation with no network call.
!Upgrading from npm alone is insufficient: failproofai update must be run after npm install -g failproofai@latest to install the matching failproofaid binary and run home migrations, otherwise ~/.failproofai/ and the daemon binary are not updated.
LangSmith's July 6-10 2026 update switches cloud bulk export to zstandardzstandardA lossless compression algorithm and open format created by Facebook, offering better ratios than zlib at comparable speeds, which lets cyber tools shrink data streams or stored artifacts without sacrificing throughput. compression while giving self-hosted deployments a flag to keep gzipgzipA lossless data compression format and command-line utility maintained as a GNU project, widely used to shrink files or streams so cyber tools can reduce storage and transfer overhead., adds an API endpoint to test thread evaluators before saving, and introduces OpenTelemetryOpenTelemetryA CNCF-maintained open standard and SDK collection for capturing traces, metrics, and logs from applications in a vendor-neutral format, letting cyber tools ingest observability data without locking into a proprietary pipeline. resource attributes for trace metadata, alongside bulk split management for experiments and several tracing and sharing fixes; legacy dataset comparison helpers are removed from the public API and SDKs.
LangSmith is a platform for debugging, testing, and monitoring LLM applications built with LangChain.
LangSmith's July 6-10 2026 update switches cloud bulk export to zstandardzstandardA lossless compression algorithm and open format created by Facebook, offering better ratios than zlib at comparable speeds, which lets cyber tools shrink data streams or stored artifacts without sacrificing throughput. compression while giving self-hosted deployments a flag to keep gzipgzipA lossless data compression format and command-line utility maintained as a GNU project, widely used to shrink files or streams so cyber tools can reduce storage and transfer overhead., adds an API endpoint to test thread evaluators before saving, and introduces OpenTelemetryOpenTelemetryA CNCF-maintained open standard and SDK collection for capturing traces, metrics, and logs from applications in a vendor-neutral format, letting cyber tools ingest observability data without locking into a proprietary pipeline. resource attributes for trace metadata, alongside bulk split management for experiments and several tracing and sharing fixes; legacy dataset comparison helpers are removed from the public API and SDKs.
└──▷ WHAT SHIPPED · 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
API endpoint to test thread evaluators before savingNEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
A new endpoint, POST /runs/rules/validate, lets you test a multi-turn thread evaluator against a real conversation before saving it, by passing a test_thread_id, session_id, and an evaluator object with type: thread to confirm scoring logic works end-to-end.
Test a multi-turn thread evaluator against a real conversation before saving it, to confirm scoring logic works end-to-end.
— Named endpoint with runnable curl example and payload fieldssnapshot-20260901
02
Legacy dataset comparison helpers removed from API and SDKsBREAKING60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Legacy dataset comparison helpers are removed from the public OpenAPI spec and generated SDKs; existing HTTP routes continue to work only for LangSmith UI clients.
— Names affected surfaces but gives no migration pathsnapshot-20260901
thinner coverage below
03
Bulk split management for experiment rowsNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Users can select multiple experiment rows, or all rows matching current filters, and add, replace, or remove dataset splits in a single action, or copy the selected examples to another dataset.
— Describes the UI action but no exact navigation pathsnapshot-20260901
04
Custom code evaluator failures now surface as run errorsIMPROVED45how completely this was documenteddepth25/40specificity10/30actionability10/3045 / 100
Custom code evaluators that time out or fail now record an error on the affected run instead of silently omitting feedback, making partial evaluation failures visible in the experiment.
— Explains the behavior change but names no surfacesnapshot-20260901
05
Trace sharing now operates on the trace rootIMPROVED45how completely this was documenteddepth25/40specificity10/30actionability10/3045 / 100
Sharing, viewing, or unsharing any run in a trace now operates on the trace root, making every run in a shared trace publicly viewable and opening public run links within the shared trace context.
!Legacy dataset comparison helpers are removed from the public OpenAPI spec and generated SDKs; existing HTTP routes continue to work only for LangSmith UI clients.
Open-source observability tool that uses AI agents to self-heal your software
Superlog adds GCP disconnect, Cloudflare Workers selection, GCP log intake filters, Sentry webhook multiplexing, and MCPMCPModel Context Protocol, an open standard from Anthropic that lets an AI model call external tools and data sources through a uniform interface, so cyber tools can expose capabilities directly to LLM-based agents. write-scope authoring tools.
└──▷ GET THIS VERSION
$ git clone --branch commits-2026-08-02 https://github.com/superloglabs/superlog.git
# already have the repo? check out this version:$ git checkout commits-2026-08-02
└──▷ TRY IT
Disconnect a previously connected Google Cloud integration for a given authorization.
›Adds POST /api/gcp/authorizations/{authorizationId}/disconnect endpoint to disconnect a Google Cloud integration.
›Adds GCP log group intake filters to control which log groups are ingested from Google Cloud.
›Adds shared Sentry OAuth callback allowlist and webhook fan-out routing so a single Sentry App can serve multiple applications without open redirects or broken webhook signatures.
›Adds Cloudflare Workers selection, letting users choose specific Cloudflare Workers to monitor.
›Adds support for configured Portless web hosts.
+3 moreshow less
›Adds telemetry hostname support during web migration.
›Shows quota reset date in the billing usage view.
›Adds Responder to the public navigation, linking to the Responder product.
Phoenix client 7.7.0 adds programmatic control over project retention policies, cross-project trace transfer, and typed user lookup.
AI Observability & Evaluation
Phoenix client 7.7.0 adds programmatic control over project retention policies, cross-project trace transfer, and typed user lookup.
└──▷ WHAT SHIPPED · 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Project retention policy management via clientNEW70how completely this was documenteddepth25/40specificity20/30actionability25/3070 / 100
Adds setProjectRetentionPolicy to the @arizeai/phoenix-client/projects entry point, letting callers assign an existing retention policy to a project by GlobalID or reset a project back to the default policy.
Langfuse's two releases centered on strengthening the evals workflow — linking evaluator traces, adding dataset filtering and MCPMCPModel Context Protocol, an open standard from Anthropic that lets an AI model call external tools and data sources through a uniform interface, so cyber tools can expose capabilities directly to LLM-based agents. output definitions, and guiding evaluator setup — alongside smaller improvements to CSV import and PR review tooling.
Open source AI engineering platform: LLM evals, observability, metrics, prompt management, playground, datasets. Integrates with OpenTelemetry, LangChain, OpenAI SDK, LiteLLM, and more. YC W23
Langfuse's two releases centered on strengthening the evals workflow — linking evaluator traces, adding dataset filtering and MCPMCPModel Context Protocol, an open standard from Anthropic that lets an AI model call external tools and data sources through a uniform interface, so cyber tools can expose capabilities directly to LLM-based agents. output definitions, and guiding evaluator setup — alongside smaller improvements to CSV import and PR review tooling.
└──▷ WHAT SHIPPED · 4 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Evaluator workflow improvements across evals UINEW57how completely this was documenteddepth25/40specificity20/30actionability12/3057 / 100
Evaluator execution traces are now linked directly from the traces view, making it easier to inspect how an evaluator ran against a given trace. The evals workflow also gains filtering of evaluator samples by dataset name, MCP support for describing evaluator output definitions, and a next-step state line added to the evaluator setup footer to guide configuration.
— Named UI areas and MCP support but no exact flags or endpointsv4.26.0v4.25.0
02
API spec previews for pull requestsNEW40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Adds API spec previews for pull requests, surfacing diff-level API contract changes during review.
— Describes the feature but not where or how to view previewsv4.26.0
03
Improved CSV parsing for large and malformed filesIMPROVED38how completely this was documenteddepth15/40specificity15/30actionability8/3038 / 100
Enhances CSV parsing with error handling for large and malformed files in preview mode.
— States the change but no detail on error handling mechanismv4.25.0
04
Header visibility persistence in sessions viewIMPROVED33how completely this was documenteddepth10/40specificity15/30actionability8/3033 / 100
Persists header detail visibility across sessions in the sessions view.
— Minor UI persistence tweak with little further detailv4.25.0
Pinecone introduced Nexus, a console workspace for building curated knowledge contexts that agents can query for grounded, cited answers.
Pinecone is the vector database for AI agents and applications, built for semantic search, knowledge retrieval, and long-term memory at scale.
Pinecone introduced Nexus, a console workspace for building curated knowledge contexts that agents can query for grounded, cited answers.
└──▷ WHAT SHIPPED · 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Nexus knowledge context for cited answersNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
A new Nexus area in the Pinecone console lets users add data sources, organize them into a 'context', and then query that context to retrieve grounded, cited answers for use inside an agent pipeline.
Get grounded, cited answers from your curated knowledge context inside an agent pipeline.
📍In the Pinecone console, go to Nexus, add your data sources, organize them into a context, then query the context to retrieve cited answers.
— Describes the workflow and UI path but lacks API details or limits.snapshot-20260901