PAGES
Subscribe Get it delivered — five to ten releases we picked each morning from the tools you run, with every release in the issue on the web. Compare plans →

The Cyber Toolchain — issue 045, August 14, 2026

THE CYBER TOOLCHAIN NO. 045
Tail
THE DAILY RELEASE FIREHOSE
PUBLISHED AUGUST 14, 2026 · EVERY DAY
EDITIONS tail grep head ls diff uniq

The daily firehose — everything the toolchain shipped today, already filtered.

We read every release from the 1309 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 VIEW scroll
ISSUE WIDTH reading width
Do you prefer scroll?
ADDITIONAL FILTERS
$ tct list   # 34 tools matched
Offensive Security
◆  Exploitation & C2

Prescient Security Cait

Sources Release page → 1 release · seen 2026-08-14 Notes

Cait expanded its platform with Attack Surface Management and new asset testing capabilities in this release.

└──▷ WHAT SHIPPED · 2 FEATURES 0 OF 2 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Attack Surface Management added to Cait new 15

Cait's platform now includes Attack Surface Management, extending discovery and monitoring capabilities beyond what was previously supported.

— No mechanism, scope, or interface detail given snapshot-20260814
02 00
New asset testing capabilities new 5

Cait introduces new asset testing capabilities within its service.

— Bare mention with no detail on scope or mechanism snapshot-20260814
Was this useful?
Application Security
◆  Web Application Security

dirsearch

Sources Release notes → 1 release · 2026-08-14 Notes

Web path scanner

dirsearch's v0.5.0 release introduces a Rust-native scanning and wordlist backend, category-based wordlists with template placeholders, ffuf-style match/filter controls, multi-format reporting with direct MySQL/PostgreSQL output, and JSON-based resumable sessions, while accompanying config.ini documentation details new scan-calibration keys and native-backend proxy/redirect support.

└──▷ WHAT SHIPPED · 11 FEATURES 2 OF 11 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Native Rust backend for scanning and wordlists new 95

dirsearch adds a Rust-based native backend selectable via --request-backend native and --wordlist-backend native (also configurable as the request-backend, default python, and wordlist-backend, default auto, keys in config.ini), with --sync to fall back to the legacy threaded stack. The native backend now supports HTTP proxying, follows HTTP redirects during enumeration, bounds response body memory to prevent unbounded consumption on large scans, and ships with parity guardrails and CI integration to keep its behaviour aligned with the standard backend.

Run a scan using the Rust native backend for maximum throughput on a large wordlist.
$ dirsearch -u https://target -e php,html,js --request-backend native --wordlist-backend native -w /path/to/wordlist
— Names flags, config keys, defaults and native-backend mechanics. v0.5.0
02 00
Multi-format reporting with SQL database output new 90

output-formats in config.ini supports simple, plain, json, xml, md, csv, html, and sqlite, writable together in a single run; output-file accepts template variables {extension}, {format}, {host}, {scheme}, {port}, {date}, and {datetime} for dynamic naming. New mysql-url and postgres-url keys write scan results directly to MySQL or PostgreSQL, with the destination table controlled by output-sql-table (default {scheme}_{host}:{port}).

Write scan results to PostgreSQL and an HTML report simultaneously, using dynamic file naming based on host and date.
ini
# config.ini
output-formats = html
output-file = reports/{host}/{date}.{extension}
postgres-url = postgres://user:password@localhost/dirsearch
— Names every output key, format and default value. v0.5.0
03 00
Category wordlists and template placeholders new 85

--wordlist-categories selects category-based bundled wordlists (PHP, Python, Java, .NET, Node, ColdFusion, and infrastructure), matched by the wordlist-categories key in config.ini (e.g. common, conf, web). --wordlist-status and --wordlist-max-size (config key wordlist-max-size, default 500000) control size, and wordlist-backend (config default auto, values auto/python/native) selects the generation engine. Template wordlists support placeholders %SUBJECT%, %CRUD_OP%, %AUTH_OP%, %DATE%, %API_VERSION%, %CATEGORY:name%, and %EXT%.

Scan a target using category-based wordlists to focus on PHP and Node.js paths without maintaining a manual wordlist.
$ dirsearch -u https://target -e php,js --wordlist-categories php,node
— Lists flags, config keys, defaults and placeholder syntax. v0.5.0
04 00
ffuf-style match and filter controls new 85

config.ini and the CLI gain ffuf/wfuzz-style opt-in matching via matcher-mode and filter-mode (value or), plus match-status, filter-status, match-size, filter-size, match-words, filter-words, match-lines, filter-lines, match-regex, filter-regex, match-time, and filter-time keys for fine-grained response filtering. Additional keys filter-threshold, exclude-redirect, exclude-response, and exclude-texts (e.g. 'Not found', '404') filter by numeric threshold, redirect pattern, reference response file, or response body text.

Enable ffuf-style response matching to surface only responses with 100-2000 bytes and 10-100 words, filtering noise from large or empty replies.
ini
# config.ini
matcher-mode = or
match-size = 100-2000
match-words = 10-100
filter-size = 0
— Enumerates every match/filter key with example usage. v0.5.0
05 00
Scan control, calibration and logging options new 85

config.ini adds skip-on-status (default 429) to auto-skip rate-limited targets, target-max-time for a per-target time cap, and auto-calibration to force extra wildcard calibration up front. Recursive scans gain recursion-status (default 200-399,401,403) and max-recursion-depth (default 0); other new keys are network-interface (e.g. eth0) to bind scans to a NICNICA network interface card or adapter, the hardware that connects a computer to a network. It sends and receives packets over the link., replay-proxy to forward matches through a secondary proxy, and log-file/log-file-size for persistent capped logging. Release v0.5.0 adds the --disable-cli flag, Nmap XML target import, and --verbose output showing response elapsed time and content type.

Automatically skip rate-limited targets and cap total scan time per host to avoid stalling CI pipelines.
ini
# config.ini
skip-on-status = 429
target-max-time = 120
auto-calibration = True
— Names every scan-control key, flag and default value. v0.5.0
06 01
Database extras and installer changes breaking 70

Optional MySQL and PostgreSQL report dependencies are now explicit extras — dirsearch[mysql], dirsearch[postgresql], and dirsearch[db] — instead of mandatory runtime dependencies, so existing installs relying on auto-installed DB drivers must reinstall with the appropriate extra. The old dependency installer path was removed.

— Gives exact extras names and required reinstall action. v0.5.0
07 02
JSON-based resumable sessions breaking 65

Resumable scan sessions now store JSON controller state instead of pickle, with --list-sessions to enumerate saved sessions and resume by ID. Legacy pickle sessions are no longer loaded directly and produce a warning on upgrade.

— Names the flag and format change but not migration steps. v0.5.0
08 00
Python API for programmatic scanning new 65

Adds a Python API with FuzzerConfig, DirsearchFuzzer, structured results, wordlist helpers, and template wordlist support, plus a python -m dirsearch entrypoint for running scans without the standalone CLI.

— Names the API classes but gives no usage example. v0.5.0
09 00
Cross-platform builds and Docker images new 65

PyInstaller release builds now cover Windows x64, Linux x64, Linux ARM64ARM64The 64-bit instruction set architecture from ARM Holdings, used in modern mobile chips, Apple Silicon, and cloud server CPUs; tools target it to run natively on those platforms without emulation overhead., macOS Intel, and macOS Apple Silicon across async, threaded, and native-rust stack variants. Linux x64 Docker images are published to GitHub Container Registry for each release stack, and portable CPython archives with compiled dependencies are offered as an alternative for users hit by PyInstaller antivirus false positives.

— Names platforms and stacks but no pull command. v0.5.0
thinner coverage below
10 00
Expanded bundled discovery data improved 40

Bundled discovery wordlists are expanded with new framework paths, WordPress and WooCommerce entries, API/Ollama/OpenAI endpoints, and traversal-oriented entries.

— Names data categories added but no counts or files. v0.5.0
11 00
Safer XML parsing against malicious input improved 25

Hardens XML parsing with safe XML handling to protect against malicious input.

— Only states the hardening exists, no mechanism given. v0.5.0
└──▷ BREAKING ON UPGRADE
  • !
    Resumable sessions now use JSON controller state; legacy pickle sessions are no longer loaded directly and will produce a warning on upgrade.
  • !
    Optional DB dependencies (MySQL, PostgreSQL) are now explicit extras (dirsearch[mysql], dirsearch[postgresql], dirsearch[db]) rather than mandatory runtime dependencies — existing installs that relied on auto-installed DB drivers must reinstall with the appropriate extra.
  • !
    The old dependency installer path was removed.
Was this useful?

Dalfox

Sources Release notes →Source code → 1 release · 2026-08-13 Notes Code

Dalfox is a powerful open-source XSS scanner and utility focused on automation.

Dalfox hardened its server mode with cross-site and DNS-rebinding protections, host/origin allow-lists and memory caps, introduced a full dalfox payload subcommand with JSON output and a wide set of named payload-category selectors, and shipped scanning accuracy improvements including modern JS framework detection, wider rate limiting, better cookie injection and clearer panic reporting.

└──▷ WHAT SHIPPED · 7 FEATURES 1 OF 7 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 01
Server hardening against cross-site and DNS-rebinding attacks new 95

dalfox server now blocks browser-driven cross-site and DNS-rebinding requests by validating the Origin, Sec-Fetch-Site, and Host headers, rejecting Sec-Fetch-Site: cross-site or same-site requests with 403 while leaving non-browser clients (curl, CLI, CI) unaffected. The --allowed-hosts <names> flag lists extra hostnames accepted in the Host header beyond the bind host, localhost, and IP literals (for reverse-proxy setups), while --allowed-origins permits specific web UI origins through the cross-site gate without disabling CORSCORSA browser mechanism that lets a server declare which foreign origins may read its HTTP responses, enforced by the browser to block unauthorized cross-site requests from JavaScript. enforcement. The server also prints a startup warning when JSONP is enabled without an API key, since JSONP bypasses the cross-site gate and would let any site launch scans and read results, and --max-retained-scans caps how many finished scan results are retained to prevent unbounded memory growth.

Run Dalfox server behind a reverse proxy that forwards a public hostname, so the Host-header gate doesn't reject legitimate requests.
$ dalfox server --allowed-hosts "dalfox.internal,scan.corp.example"
Allow a specific internal web UI to call the Dalfox server API while keeping the cross-site gate active for all other origins.
$ dalfox server --allowed-origins "https://app.example.com"
Prevent unbounded memory growth in long-running server mode by capping how many finished scan results are retained.
$ dalfox server --max-retained-scans 200
— Named flags, headers and status codes with runnable commands v3.2.1
02 00
Payload subcommand with named category selectors new 85

dalfox payload gains selectors for payloadbox (fetches remote payloads from PayloadBox), all (prints every local selector under # name headers, remote excluded), event-handlers (DOMDOMThe browser's in-memory tree representation of a web page's structure, standardized by the W3C, giving cyber tools a programmable interface to read or manipulate page content at runtime. event handler attributes like onclick, onmouseover), useful-tags (tags like script, img, svg), uri-scheme (scheme-based payloads like javascript:, expanded from 5 to 11 entries), dom-clobbering, mxss (mutation-XSSXSSCross-site scripting, an attack that runs malicious script in another user's browser through a trusted site. It can steal data or perform actions using the user's session./sanitizer-bypass), blind (skeletons where {} is substituted with an OOB callback URL), a special-characters/encoded-variants selector (also expanded), a visibly-confirmable-sinks selector with filter-surviving variants, and a polished alert(document.domain) PoC selector for screenshots. The command also gained per-selector item counts in its summary output and closest-selector suggestions (Levenshtein distance ≤ 2) when an unknown selector name is given.

Quickly dump every local payload category in one shot to pipe into a fuzzer or review offline.
$ dalfox payload all
Generate blind-XSS skeletons pre-populated with your OOB callback to drop straight into a payload list.
$ dalfox payload blind
— Every selector named with commands demonstrating the pattern v3.2.1
03 00
INTERNAL_ERROR status for scanner panics improved 65

Introduces an INTERNAL_ERROR status code on target_summary entries so a scanner panic is reported as skipped rather than silently falling through to clean.

— Named field and status code with clear before/after behavior v3.2.1
thinner coverage below
04 00
JSON output for payload command new 55

The --json flag prints selected payloads as a JSON array instead of one item per line, giving machine-readable payload lists out of dalfox payload.

— Named flag but no usage example given v3.2.1
05 00
Rate limiting extended to discovery and mining phases improved 55

REST and MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. rate_limit now applies to the discovery and mining phases, not only scanning, so it throttles requests across the whole workflow.

— Names the config surface but gives no example v3.2.1
06 00
Cookie parameters injected as cookies improved 55

Cookie parameters are now injected as actual cookies rather than as same-named headers, raising cookie recall from 80.0% to 87.5%.

— Concrete before/after metric but no actionable flag v3.2.1
07 00
Modern JavaScript framework detection new 25

Dalfox now detects modern JavaScript frameworks during scanning.

— No mechanism, frameworks, or scope given v3.2.1
Was this useful?

Acunetix 360

Sources Blog / feed → 1 release · 2026-08-13 Blog

Acunetix 360 is a cloud-based web application security scanning platform that identifies vulnerabilities through automated dynamic and static analysis.

Acunetix 360's v26.8.0 release extends scan data retention and adds support for .NET 10.

└──▷ WHAT SHIPPED · 2 FEATURES 0 OF 2 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Extended scan data retention to 730 days improved 35

Scan data retention is now extended to 730 days.

— States new limit but no mechanism or config detail. v26.8.0 – 13 August 2026 (2026-08-13)
02 00
.NET 10 support added new 30

Acunetix 360 adds support for .NET 10.

— Names the version but no scope or usage detail. v26.8.0 – 13 August 2026 (2026-08-13)
Was this useful?
◆  SAST / SCA / Code Security

Wiz Code

Sources Blog / feed → 1 release · 2026-08-13 Blog

Wiz Code extends secret detection beyond organizational boundaries by inventorying developers' personal public GitHub repositories, validating credential exploitability with an AI-powered Red Agent, and mapping full attack pathsattack pathsA possible sequence of steps an attacker could take to reach a valuable target. It connects weaknesses, permissions and reachable systems rather than treating each finding separately. on the Security Graph.

└──▷ WHAT SHIPPED · 5 FEATURES 2 OF 5 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 01
Red Agent exploitability validation for exposed credentials new 60

Wiz Red Agent, described as an AI-powered attacker, actively tests whether an exposed credential found in a personal repo is live and what it can reach, going beyond traditional validity checks.

— Names the Red Agent and its behavior but no invocation shown 2026-08-13-8ecb9077
02 00
Identity-attached secret findings with commit and owner data new 60

Findings from personal repositories surface the exact commit, GitHub user, and email that pushed a secret, enabling immediate owner-assigned remediation without manual investigation.

— Names surfaced fields, giving a clear remediation starting point 2026-08-13-8ecb9077
thinner coverage below
03 00
Remediation workflow integration for personal-repo findings new 55

Personal-repo findings integrate into existing remediation workflows including Jira ticket creation, Slack developer notification, and tracked token rotation and revocation.

— Names Jira and Slack integrations but no config keys or endpoints 2026-08-13-8ecb9077
04 00
Security Graph attack path for personal-repo secrets new 50

Secrets found in personal repositories are enriched onto the Wiz Security Graph to show the full attack pathattack pathA possible sequence of steps an attacker could take to reach a valuable target. It connects weaknesses, permissions and reachable systems rather than treating each finding separately. and blast radius of a compromised credential, including downstream resource access.

— Names the Security Graph mechanism but no query or navigation given 2026-08-13-8ecb9077
05 02
Personal GitHub repo inventory and identity correlation new 45

Wiz Code adds automated inventory and correlation of developer identities to their personal public GitHub repositories outside org boundaries, closing the visibility gap where unmanaged secret exposure lives.

— Explains the gap it closes but no command or config to invoke it 2026-08-13-8ecb9077
Was this useful?

StepSecurity

Sources Blog / feed → 1 release · 2026-08-13 Blog

StepSecurity is a security platform that hardens GitHub Actions workflows and CI/CD pipelines by reducing attack surface and preventing supply chain compromises.

StepSecurity's Secure Registry adds Go module proxying (Beta), rounding out its policy-controlled proxy support alongside npm, PyPI, Maven, and NuGetNuGetMicrosoft's package manager for .NET, hosting a public registry of reusable libraries so tools can pull in dependencies without bundling or manually maintaining third-party code., with a full set of Go-specific security controls and checksum handling.

└──▷ WHAT SHIPPED · 4 FEATURES 2 OF 4 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 01
Go-specific policy controls: tags, cooldown, compromised packages, block list new 80

Released Tags Only rejects Go module resolutions at commit hashes, branch names, and pseudo-versions such as v0.0.0-20241114170450-2d3c2a9cc518, permitting only published release tags. Cooldown Period holds newly published Go module versions for a configurable window, with per-module exemptions scoped to the full module path. Compromised Packages blocks Go module versions flagged by StepSecurity's SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. or the wider security community. Custom Block List bans a Go module or version range org-wide using module@version form with glob support.

— Enumerates every control and its exact syntax Secure Registry Now Supports Go (2026-08-13)
02 00
Proxy Checksum Database for Go modules new 75

A new Proxy Checksum Database setting under Go Registry Settings relays sum.golang.org requests through Secure Registry, removing the need to disable GOSUMDB when runners cannot reach the default checksum database.

— Names exact setting and env var it replaces Secure Registry Now Supports Go (2026-08-13)
03 02
Go module proxy support in Secure Registry new 70

Secure Registry now proxies Go modules (Beta) at https://registry.stepsecurity.io/go, joining existing npm, PyPI, Maven, and NuGet proxying; every module request is evaluated against your Go policy before a response is returned. Integration paths for Go proxy support cover JFrog Artifactory, Sonatype Nexus Repository, and Direct.

— Names endpoint and integration paths but lacks setup steps Secure Registry Now Supports Go (2026-08-13)
thinner coverage below
04 00
Policy Evaluations logging for Go requests new 45

Every Go module request is logged in the Policy Evaluations log as Allowed, Modified, or Blocked, attributed to the developer machine or workflow run that made the request.

— Describes log categories but no navigation or query detail Secure Registry Now Supports Go (2026-08-13)
Was this useful?
Network Security
◆  Firewalls & Network Defense

Aviatrix CoPilot

Sources Release page → 1 release · seen 2026-08-14 Notes

Aviatrix CoPilot is an AI-powered assistant that helps operators manage, troubleshoot, and optimize cloud network infrastructure across multiple cloud providers.

Aviatrix CoPilot's biggest addition this window is a new Cloud Routes diagnostics module for multicloud routing and gateway troubleshooting, alongside an Egress Security Score dashboard, a VPNVPNA virtual private network, an encrypted tunnel between devices or networks. It carries traffic across another network as though the endpoints had a private connection. Client 3.0.2 refresh (Universal macOS binary, FIPS 140-3FIPS 140-3A US federal standard, maintained by NIST, that defines requirements for cryptographic modules used in government systems. Cyber tools target it to satisfy procurement mandates requiring validated crypto./SAMLSAMLA standard for passing signed identity assertions between a sign-in provider and an application. It lets a user sign in through their organization's identity provider. support, and a breaking CA key-length requirement), and a batch of smaller CoPilot 4.36.0 additions spanning gateway management, network segmentation, Kubernetes visibility, notifications, and serverless permission gaps.

└──▷ WHAT SHIPPED · 12 FEATURES 2 OF 12 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
FIPS build requires RSA 2048-bit UserVPN CA breaking 90

The FIPSFIPSA set of US federal standards published by NIST that define approved cryptographic algorithms and modules; cyber tools use it to meet compliance requirements in government and regulated environments. build of VPN Client 3.0.2 requires the VPN gateway's UserVPN CA to use an RSARSAThe oldest widely used public-key algorithm, for both encryption and signatures, with security resting on factoring large numbers. A large quantum computer would break it. key of at least 2048 bits. Gateways on Controller versions earlier than 8.2, or Controller 8.2 gateways whose UserVPN CA has not been rotated since upgrade, may still use a 1024-bit CA (common on Controllers originally initialized on Aviatrix 7.1 or earlier) and will fail client certificate verification; operators must rotate the UserVPN CA to RSA 2048-bit before upgrading.

— Exact migration action and affected controller versions given product docs
02 00
Cloud Routes diagnostics and multicloud routing view new 85

New Cloud Routes feature at CoPilot > Diagnostics > Cloud Routes gives a central view of routing across the Aviatrix transit network, multicloud and on-prem Site2Cloud connections, without logging into individual cloud consoles. It includes a Gateway Routes tab (tunnel info, route state up/down, routing tables, filterable by gateway name, subnet, or IP), a VPC/VNet Routes tab (routing tables per VPCVPCA logically isolated virtual network inside a public cloud provider's infrastructure, letting tools deploy resources with private addressing, controlled routing, and firewall rules without managing physical hardware./VNetVNetA private, isolated network hosted inside Microsoft Azure that lets virtual machines and services communicate with each other and with the internet under user-defined IP ranges and routing rules./VCN, filterable by route table name, subnet, or IP), an External Connections tab (data center tunnel status, connected gateway, remote IP, tunnel type, linked to Topology and FlowIQ), and a BGP Info tab (advertised/learned routes, connection map with ASNASNAutonomous System Number — a globally unique identifier assigned by regional internet registries to a network operator, letting routing protocols distinguish which organization controls a block of IP addresses. and IP). A gateway diagnostics panel adds PING, TRACEROUTE, TRACEPATH, TRACELOG (uploads directly to Aviatrix Support), Test Connectivity (TCPTCPA network protocol that delivers a reliable, ordered stream of bytes between two endpoints. It detects lost data and retransmits it./UDPUDPA network protocol that sends individual messages without guaranteeing delivery or order. Applications trade built-in reliability for less overhead and can add their own recovery. to a host and port), ACTIVE SESSIONS (filterable by port), INTERFACE STATS, PACKET CAPTURE (filter by host, port, time, address, protocol, flags; download as pcap for Wireshark), and SERVICE ACTIONS (check/restart gateway services).

— Exact UI path and every diagnostic tool named, but no runnable command product docs
03 00
Egress Security Score dashboard new 80

New Security > Egress > Overview tab (requires Controller 8.0 and DCF feature enabled) shows an Egress Security Score card with a score-calculation explainer dialog and a Manage VPC/VNets link to the Egress VPC/VNets tab, plus a Protected VPC/VNets card breaking cloud-account VPC/VNets into Unprotected, Monitored, Partially Protected, Protected, No Egress, and Unknown states.

— Exact UI path, prerequisites, and state categories named product docs
04 00
FIPS 140-3 encryption and SAML authentication in VPN Client new 60

FIPS 140-3 compliant encryption is now supported in the VPN Client 3.0.2, with SAML-based authentication (Okta, Duo, and other SAML identity providersidentity providersA service that authenticates users and supplies identity information to other applications. It is the sign-in authority behind many single sign-on systems.) available across Windows, macOS, and Ubuntu.

— Names providers and platforms but no configuration steps product docs
thinner coverage below
05 00
VPN Client 3.0.2 Universal macOS binary and Ubuntu 26.04 support new 55

The VPN Client 3.0.2 macOS installer is now a Universal binary running natively on both Intel and Apple Silicon (ARM64ARM64The 64-bit instruction set architecture from ARM Holdings, used in modern mobile chips, Apple Silicon, and cloud server CPUs; tools target it to run natively on those platforms without emulation overhead.), eliminating the Rosetta 2 dependency. Ubuntu 26.04 is now supported alongside existing Ubuntu 22.04 and 24.04.

— Names exact platforms and versions, no setup steps needed product docs
06 00
Missing permissions visibility for serverless functions new 40

New Missing Permissions Visibility for Serverless Functions surfaces IAMIAMIdentity and Access Management — a framework of policies and services for controlling who can authenticate to systems and what resources they are authorized to use, letting cyber tools enforce least-privilege and audit access./permission gaps for serverless workloads directly in CoPilot.

— Names the gap it surfaces but not the UI location New and Enhanced Features in 4.36.0
07 00
VRF support in Network Segmentation new 35

CoPilot 4.36.0 adds VRFVRFA Virtual Routing and Forwarding instance is a router feature that maintains multiple independent routing tables on one device, letting a cyber tool isolate traffic flows or simulate separate network segments without extra hardware. support in Network Segmentation, enabling VRF-aware policy across segmented networks.

— States capability but no configuration path or example New and Enhanced Features in 4.36.0
08 00
Kubernetes intra-cluster orchestration status view new 35

New Kubernetes Intra-Cluster Orchestration Status view surfaces the health and state of intra-cluster traffic orchestration.

— Describes purpose only, no UI path or detail New and Enhanced Features in 4.36.0
09 01
Gateway management controls for AZ affinity and sizing new 30

CoPilot 4.36.0 adds AZ Affinity, Symmetric Routing, and T-Shirt Instance Sizing controls for Gateway Management.

— Names three controls but no mechanism or location New and Enhanced Features in 4.36.0
10 00
FIPS 140-3 compliance indicators in CoPilot UI new 30

CoPilot 4.36.0 adds FIPS 140-3 compliance indicators in the CoPilot UI.

— Names the standard but not where indicators appear New and Enhanced Features in 4.36.0
11 02
Ubuntu 20.04 support deprecated in VPN Client deprecated 25

Ubuntu 20.04 support is deprecated as of VPN Client 3.0.2.

— Bare deprecation notice with no timeline or replacement product docs
12 00
Updated Controller bell notifications improved 25

Updated Controller Bell Notifications bring alerting improvements to the CoPilot notification center.

— Vague 'improvements' with no specifics given New and Enhanced Features in 4.36.0
└──▷ ALSO FROM THESE RELEASES
└──▷ BREAKING ON UPGRADE
  • !
    The FIPS build of VPN Client 3.0.2 requires the VPN gateway's UserVPN CA to use an RSA key of at least 2048 bits — gateways on Controller versions earlier than 8.2, or Controller 8.2 gateways whose UserVPN CA has not been rotated since upgrade, may use a 1024-bit CA (common on Controllers originally initialized on Aviatrix 7.1 or earlier) and will fail client certificate verification. Rotate the UserVPN CA to RSA 2048-bit before upgrading.
  • !
    Ubuntu 20.04 support is deprecated in VPN Client 3.0.2.
Was this useful?

Fastly

Sources Blog / feed → CLI v16.0.0 (2026-08-13) Blog

Fastly is a content delivery network and edge computing platform that accelerates website performance and provides security services globally.

Fastly CLI v16.0.0 now offers all available starter kits for each language during compute init.

Was this useful?
Detection & Response
◆  Endpoint Security (EDR/XDR)

Iru

Sources Release page → 1 release · seen 2026-08-14 Notes

Iru launched a Windows system tray app that lets end users install pending app updates themselves without IT involvement.

└──▷ WHAT SHIPPED · 1 FEATURE 0 OF 1 FEATURE most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Windows system tray update app new 55

A new Iru system tray app on Windows displays all pending Auto App and Custom App updates, letting end users install one at a time or trigger Update all without IT involvement. The update list automatically clears completed entries as installs succeed, and the app handles closing open apps when required to finish an install.

— Describes behaviour well but no config keys or flags named. Update Windows apps from the system tray
Was this useful?

Trend Vision One

Sources Blog / feed → 1 release · 2026-08-13 Blog

Trend Vision One is Trend Micro's unified cybersecurity platform providing threat intelligence, vulnerability management, and incident response across endpoints and networks.

Trend Vision One now lets administrators reset MFAMFAMulti-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone. for individual user accounts directly from the console, removing the need to file a support case.

└──▷ WHAT SHIPPED · 1 FEATURE 0 OF 1 FEATURE most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Admin-level MFA reset for user accounts new 72

Administrators can reset MFA for individual user accounts using the Admin-level MFA reset option on the User Accounts page, eliminating the need to open a support case when a user loses their MFA device or recovery code. After the reset, the user is prompted to set up MFA again at their next sign-in.

When a user is locked out after losing their MFA device, reset their MFA without a support case so they can re-enroll at next sign-in.
📍In the Trend Vision One console, go to Administration → User Accounts, locate the target account, click the options icon, then click Admin-level MFA reset. The user will be prompted to set up MFA at their next sign-in.
— Names exact UI option and console path but no scope/limits. Administrators can now reset MFA for user ac…
Was this useful?

Microsoft Sysinternals

Sources Blog / feed → 1 release · 2026-08-12 Blog

Microsoft Sysinternals is a suite of advanced system utilities for Windows diagnostics, monitoring, and troubleshooting at the kernel level.

Microsoft Sysinternals shipped Process Tree PID filtering in Process Monitor, Azure Virtual Desktop and Dev Box support in RDCMan, and a new DemoMirror feature in ZoomIt, alongside smaller CPUCPUThe main general-purpose processor in a computer. It runs application instructions and coordinates work with memory and other hardware.-detection updates to CoreInfo and Process Explorer and a full Rust rewrite of NotMyFault.

└──▷ WHAT SHIPPED · 6 FEATURES 0 OF 6 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Process Tree PID filtering in Process Monitor new 50

Process Monitor adds Process Tree PID filtering to match events based on any ancestor process ID in the process tree, useful for tracing all activity spawned by a parent process.

— Explains mechanism but no exact filter syntax given NotMyFault, RDCMan, ZoomIt, CoreInfo, Proces…
02 00
AVD and Dev Box support in RDCMan new 45

RDCMan v3.20 adds Azure Virtual Desktop workspace feed support and Microsoft Dev Box support.

— Names the two supported services, no setup steps NotMyFault, RDCMan, ZoomIt, CoreInfo, Proces…
03 00
DemoMirror in ZoomIt new 45

ZoomIt v12.2 introduces DemoMirror for mirroring the screen, a screen region, or a window onto a second monitor.

— Describes function, no configuration detail included NotMyFault, RDCMan, ZoomIt, CoreInfo, Proces…
04 00
Intel LP-E core support in CoreInfo improved 35

CoreInfo v4.02 adds Intel LP-E cores support and improves CPU vendor name detection.

— Names two changes, no further mechanism detail NotMyFault, RDCMan, ZoomIt, CoreInfo, Proces…
05 00
NotMyFault rewritten in Rust improved 35

NotMyFault v4.6 is rewritten in Rust and ships with a modern UI.

— States rewrite and UI change, no specifics on new behavior NotMyFault, RDCMan, ZoomIt, CoreInfo, Proces…
06 00
Intel core type info in Process Explorer new 30

Process Explorer v17.13 adds core type information for Intel CPUsCPUsThe main general-purpose processor in a computer. It runs application instructions and coordinates work with memory and other hardware..

— Bare mention of new CPU info field NotMyFault, RDCMan, ZoomIt, CoreInfo, Proces…
Was this useful?
◆  Security Data Pipeline

Cribl

Sources Blog / feed → 1 release · 2026-08-14 Blog

Cribl is a data processing and routing platform that collects, transforms, and delivers security and observability data from multiple sources.

Cribl launched an Apps platform that lets users access pre-built tools and build custom data experiences on top of existing Cribl infrastructure using an AI-driven conversational interface.

└──▷ WHAT SHIPPED · 1 FEATURE 0 OF 1 FEATURE most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Apps platform for custom data experiences new 60

A new Apps button appears in the upper-right corner of every Cribl screen, giving access to pre-built apps that add new views, processes, workflows, and capabilities built around existing Cribl data. Users can also build custom apps through an AI-driven conversational flow, while Cribl handles the underlying hosting, identity, RBACRBACRole-based access control, where permissions are assigned to roles such as reader or administrator and users receive those roles. It makes access easier to manage than individual permission lists., and data access/governance layers.

— Names UI entry point and AI flow but no config or API detail. Cribl Apps: Do the fun part of development (…
Was this useful?
◆  SOAR

Tines

Sources Blog / feed → 1 release · 2026-08-13 Blog

Tines is a no-code automation platform for security teams to build workflows that connect tools and respond to threats.

Tines published its first public REST APIREST APIA web API design style where clients interact with resources over HTTP using standard methods like GET, POST, and DELETE, giving cyber tools a predictable, language-agnostic way to integrate with external services. (369 endpoints across 71 areas) and rolled out a wave of platform additions: Tines 3B workflows as case actions, AI Agent skill extensions, a self-hosted LDAPLDAPA protocol for querying and modifying directory services, standardized under RFC 4511, commonly used to look up users, groups, and attributes in corporate identity stores like Active Directory. configuration UI, Workbench credential restrictions, customizable AI credit alerts, per-workflow savings estimation, and improved change-control reviews.

└──▷ WHAT SHIPPED · 8 FEATURES 1 OF 8 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 01
Public REST API across 71 areas new 85

Tines published a full REST API covering 369 endpoints across 71 areas, each supporting create, read, update and delete operations. The largest areas are Actions (22 endpoints), Stories > Notes (12), Stories (11), Teams (v1) (11), Admin > Users (10), Global Resources (v1) (10), Cases (v1) > Case Templates (9) — which specifically enables managing case templates programmatically — and Admin > Sync Destinations (8), plus 63 additional areas spanning Cases, Records, Admin, Scim, Audit Logs, Workbench, Reporting, Folders (v1), Run Script Environments and more.

— Full endpoint areas and counts given, but no example calls 0.0.1
02 00
Tines 3B workflows as case actions new 65

Cases can now trigger published Tines 3B workflows directly as case actions. After configuring a 3B service account connection, users can select a published 3B workflow when adding a case action.

— Clear setup steps and UI flow named Add Tines 3B workflows as case actions in Ca…
thinner coverage below
03 00
Self-hosted LDAP configuration UI new 45

Adds a Self-hosted LDAP configuration UI for self-hosted deployments, giving admins a dedicated interface to set up LDAP.

— UI location named, no field-level detail product docs
04 00
Workbench credential restrictions new 45

Adds an admin control to Control which credentials can be used in Workbench, restricting which credentials are available within the Workbench AI environment.

— Admin control named but no exact config path product docs
05 00
Customizable AI credit usage alerts new 45

Lets teams Customize AI credit usage alerts by setting thresholds for AI credit consumption notifications.

— Threshold concept named, no exact settings path product docs
06 00
AI Agent skill extensions new 40

Introduces Extend AI Agents with skills, a new skill extension surface for AI Agents accessible via Actions and Storyboard.

— Names the surface but not skill mechanics product docs
07 00
Per-workflow savings estimation new 35

Adds configuration for detailed savings estimates on a per-workflow basis, letting teams quantify the value delivered by each automated workflow.

— No config key or UI path named product docs
08 00
Improved group change reviews improved 30

Introduces Improved group change reviews under Change Control for reviewing group-level changes to stories.

— Bare mention, no mechanism or UI detail product docs
Was this useful?
◆  SIEM

Sumo Logic

Sources Blog / feed → 2 releases · 2026-08-13 Blog

Sumo Logic is a cloud-based monitoring and analytics platform for logs, metrics, and security data.

Sumo Logic shipped a new public API for managing AWS S3 archive destinations, a Mobot skill that builds dashboard panels from plain-language prompts, and a batch of schema and parameter updates across its otCollectors, plan, and sourceTemplate endpoints.

└──▷ WHAT SHIPPED · 3 FEATURES 1 OF 3 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
otCollectors, plan and sourceTemplate API updates improved 71

Response schemas changed for GET /v1/otCollectors/otCollectorsByName, GET /v1/otCollectors/{id}, GET /v1/plan/pendingUpdateRequest, and POST /v1/otCollectors. A new dryRun query parameter was added to POST /v1/sourceTemplate and POST /v1/sourceTemplates.

— Names exact endpoints and a new parameter, but not what the schema change is. 1.0.0
thinner coverage below
02 01
Archive Destinations API for AWS S3 new 55

A new public API enables creating and managing AWS S3 archive destinations for Installed Collectors programmatically, complementing the existing UI flow for at-scale automation.

— Describes purpose and scope but no endpoint path or method given. Create and Manage Archive Destinations via A…
03 00
Mobot dashboard panel creation from prompts new 55

A new Mobot skill lets practitioners describe a desired panel in plain language, after which Mobot drafts the query, selects a visualization, and adds the panel to a new or existing dashboard.

— Clear mechanism described but no exact UI path or command given. Create Dashboard Panels with Mobot (Dashboar…
Was this useful?
Exposure & Vulnerability Management
◆  Attack Surface & Exposure Management

Intruder

Sources Blog / feed → 1 release · 2026-08-13 Blog

Intruder is a cloud-based vulnerability scanner that automatically discovers and tests systems for security weaknesses.

Intruder redesigned its side navigation, adding pinnable favourites, activity indicators and single-click access to every page.

└──▷ WHAT SHIPPED · 1 FEATURE 0 OF 1 FEATURE most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Reorganised side navigation improved 55

The sidebar now groups pages into expandable theme sections, replacing the previous nested-tab structure, and every page is reachable in a single click. A pinnable Favourites shortcut bar lets users surface their most-visited pages at the top of the nav, and icon and pill indicators on nav items surface new data or activity at a glance.

— Describes UI changes and mechanism but no config/API names. Reorganised side navigation (2026-08-13)
Was this useful?

runZero

Sources Blog / feed → 1 release · 2026-08-13 Blog

runZero is an asset discovery and inventory platform that identifies and maps all connected devices across network infrastructure.

runZero's 5.1 release adds AWS Inspector vulnerability findings to its AWS integration and overhauls the reports page with pagination, search, and delete, while also refining how the AWS integration handles closed linked accounts.

└──▷ WHAT SHIPPED · 3 FEATURES 1 OF 3 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Paginated, searchable reports page improved 48

The reports page now displays a paginated list of all analysis task-based reports and supports searching and deleting reports directly from that page.

— Describes UI capabilities with a clear navigation starting point runZero 5.1.260813.0 (2026-08-13)
02 01
AWS Inspector findings for EC2 and Lambda new 43

The AWS integration now ingests AWS Inspector findings for EC2EC2Amazon's cloud virtual-machine service, letting tools run on-demand servers without managing physical hardware. and Lambda assets, surfacing vulnerability data from those services within runZero's asset inventory.

— Names the feature and asset types but no mechanism detail runZero 5.1.260813.0 (2026-08-13)
03 00
AWS integration skips closed linked accounts improved 27

The AWS integration now skips linked organizational accounts that are closed, avoiding scans against inactive accounts.

— States the behavior change but no further mechanism or config detail runZero 5.1.260813.0 (2026-08-13)
Was this useful?
Identity, Access & Data Protection
◆  Secure Access (VPN / SASE / ZTNA)

Twingate

Sources Release page → 1 release · seen 2026-08-14 Notes

Twingate is a zero-trust network access platform that securely connects remote users and devices to private resources without VPN.

Twingate rolled out granular role-based access controlrole-based access controlRole-based access control, where permissions are assigned to roles such as reader or administrator and users receive those roles. It makes access easier to manage than individual permission lists. for its Admin Console, introducing six scoped admin roles with visible role badges and enforced page-level restrictions.

└──▷ WHAT SHIPPED · 1 FEATURE 1 OF 1 FEATURE most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 01
Scoped admin roles in Admin Console new 79

Twingate introduces six admin roles — DevOps, Helpdesk, Support, Access Reviewer, Billing, and full admin — each scoped to specific Admin Console pages and actions. DevOps admins are limited to the Network tab (Resources, Connectors, Remote Networks, Group-to-Resource assignments, Access Requests); Support admins get all pages except Internet Security > Secure DNS and Internet Security > Client Configuration; Billing admins are restricted to the Settings > Billing page for plan changes and payment details. The Helpdesk role gives read-only access to selected areas plus targeted actions — resetting MFAMFAMulti-factor authentication, requiring proof from different categories, such as a password and a hardware key, to sign in. It reduces reliance on a password alone., verifying/unverifying devices, and managing trusted serial numbers — so support staff can troubleshoot without full admin rights. DevOps, Helpdesk, Support, Access Reviewer, and Billing admins see a role badge next to the Twingate logo (hover reveals access details), and any attempt to edit settings outside a role's scope is blocked with an inline error message.

— Names exact console pages and role behaviors but only UI navigation, no API/CLI. Helpdesk Admin Role
Was this useful?
◆  Identity & Access Management

Didit

Sources Release page → 1 release · seen 2026-08-14 Notes

Didit is a decentralized identity verification platform enabling secure, privacy-preserving credential management and verification across applications.

Didit's biggest changes this window are a new endpoint for skipping or re-requiring frozen KYBKYBKnow Your Business — a regulatory compliance process for verifying the legal identity, ownership, and legitimacy of a business entity, used by cyber tools to screen counterparties or customers against fraud and sanctions risk. Key People parties and dedicated 502 error codes for KYB registry and phone-verification outages, alongside workflow branching on marital status, richer session API responses (barcode data, liveness method), capture-flow, country-selection, React Native SDK, and prepaid-credit pricing updates.

└──▷ WHAT SHIPPED · 9 FEATURES 3 OF 9 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 01
Skip or re-require frozen KYB Key People parties new 93

New PATCH /v3/session/{sessionId}/kyb/parties/{partyUuid}/ endpoint lets operators set is_skipped: true to exempt a frozen KYB Key People party from verification — immediately recomputing KYBKeyPeopleCheck and the parent KYB session status — or is_skipped: false to restore it to scope; requires the write:businesses permission via API key or console user token. The endpoint also surfaces new party-level status signals kyc_session_deleted and kyb_sub_session_deleted to explain why a party is frozen.

Unblock a KYB session stalled in Awaiting User because a UBOUBOuBlock Origin, a browser extension maintained by Raymond Hill that blocks ads and trackers using filter lists; cyber tools embed or reference it to strip unwanted content from web traffic or scraped pages.'s individual KYCKYCKnow Your Customer — a regulatory requirement that financial services verify the identity of their users before granting access, used by cyber tools handling payments or financial data to stay compliant. session was deleted — skip that party so the business session can settle.
$ curl -X PATCH 'https://api.didit.me/v3/session/sess_abc123/kyb/parties/0a3f1e2c-7c2f-4a1b-9d55-2f8d2a5d6b41/' \
  -H 'Authorization: Bearer <api_key>' \
  -H 'Content-Type: application/json' \
  -d '{"is_skipped": true}'
Restore a previously skipped Key People party to scope after the individual re-submits their KYC session.
$ curl -X PATCH 'https://api.didit.me/v3/session/sess_abc123/kyb/parties/0a3f1e2c-7c2f-4a1b-9d55-2f8d2a5d6b41/' \
  -H 'Authorization: Bearer <api_key>' \
  -H 'Content-Type: application/json' \
  -d '{"is_skipped": false}'
— Full endpoint, fields, permission and runnable curl examples given 3.0.0
02 02
502 error codes for KYB registry and phone-provider outages new 83

New kyb_registry_provider_unavailable error code (with code, summary, and detail fields) is returned as HTTP 502 on POST /v3/kyb/search/ when the KYB registry provider is temporarily unavailable — the search is not billed, and Didit's hosted flow plus Web, iOS, and Android verification flows automatically offer manual company entry instead. A parallel phone_provider_unavailable error code is returned as HTTP 502 on POST /v3/phone/send/ and POST /v3/phone/check/ when Prelude is unavailable; nothing is billed on send and the attempt budget is only consumed by completed checks.

Handle a KYB registry outage gracefully by detecting the new error code and prompting the user to enter company details manually.
python
if response.status_code == 502 and response.json().get('code') == 'kyb_registry_provider_unavailable':
    prompt_manual_company_entry()
— Named endpoints, error codes and billing behaviour with a code sample 3.0.0snapshot-20260814
03 00
Barcode data and liveness method in session responses new 73

Retrieve-session responses now include id_verifications[].barcodes, with type, position, data, data_raw, and side fields per entry (empty array if the document has no barcode output), and face-step payloads now always include face_liveness_method, defaulting to PASSIVE when a workflow doesn't set it explicitly.

Inspect barcode data extracted from a scanned ID document after a verification session completes.
$ GET /sessions/{session_id}

// Response excerpt:
// {
//   "id_verifications": [{
//     "barcodes": [
//       { "type": "PDF417", "side": "back", "data": "...", "data_raw": "...", "position": {...} }
//     ]
//   }]
// }
— Names every response field with an example response payload snapshot-20260814
04 00
Marital-status branching in workflow builder new 60

kyc.marital_status is now a usable OCROCROptical character recognition, converting text in an image or scanned document into machine-readable characters. It lets software search or process text that was stored as pixels. field in conditional branches and custom status rules within the workflow builder; when the source document omits marital status the field is empty and the fallback branch applies.

Branch a workflow on marital status to apply different KYC rules for specific applicant profiles.
json
{
  "condition": "kyc.marital_status == 'married'",
  "then": "enhanced_due_diligence_step"
}
— Named field and fallback behaviour with a sample branch condition snapshot-20260814
thinner coverage below
05 00
Copilot-driven Database Validation step setup new 45

The workflow copilot can create and configure a Database Validation step in a single action, resolving the supported validation service per country from a list you specify and displaying the saved configuration on the canvas.

— Describes mechanism but no exact UI path or command snapshot-20260814
06 00
React Native SDK codegen and dSYM support improved 45

The React Native TurboModule specification now supports React Native 0.77 code generation, and the React Native SDK (4.5.4) adds iOS dSYM artifacts.

— Names versions and artifact type but no usage step snapshot-20260814
07 03
Prepaid credit discounts replace bonus credits breaking 40

Prepaid credits now use charge discounts instead of bonus credits: 4% off at $250 and 7% off at $1,000.

— Exact thresholds and percentages given, no action needed snapshot-20260814
08 00
Document capture improvements on Web, iOS, Android new 35

French 2021 ID cards can now be read and validated via the ANTS 2D-Doc Data Matrix on the back of the document across Web, iOS, and Android, and capture flows on all three platforms can now continue with a still photo when video recording is unavailable.

— Describes two capabilities but no exact trigger or config snapshot-20260814
09 00
Continent grouping for compliance country selection improved 25

Compliance country questions in the console now group countries by continent and support selecting or clearing an entire continent at once.

— Bare UI description with no navigation detail snapshot-20260814
Was this useful?

Nudge Security

Sources Release page → 2 releases · seen 2026-08-14 Notes

Nudge Security monitors SaaS application usage and security risks across organizations to reduce cloud infrastructure threats.

Nudge Security shipped browser-level protection against employees sharing sensitive data with AI tools, plus a new dashboard for tracking passkeypasskeyPhishing-resistant sign-in credentials built on FIDO2/WebAuthn: the device holds a private key and proves possession instead of the user typing a password. They sync across a user's devices. adoption and storage across the organization.

└──▷ WHAT SHIPPED · 2 FEATURES 0 OF 2 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Passkey usage dashboard new 83

A new Dashboards > Passkey usage dashboard shows org-wide passkey adoption rate, top apps used with passkeyspasskeysPhishing-resistant sign-in credentials built on FIDO2/WebAuthn: the device holds a private key and proves possession instead of the user typing a password. They sync across a user's devices., and a per-provider storage breakdown with a toggle between number of passkeys and number of users. It also surfaces device-loss survivability and login-verification status for each detected passkey, and adds per-employee passkey usage detail on each user's user details page.

Audit where your org's passkeys are stored and whether they survive device loss — useful before a hardware refresh or incident review.
📍In the Nudge Security console, go to Dashboards › Passkey usage. Use the provider breakdown toggle to switch between number of passkeys and number of users, then review the device-loss survivability and user-verification columns.
— Names exact dashboard path, toggle, and data fields shown Track passkey adoption and storage in the ne…
02 00
In-browser sensitive data nudges for AI conversations new 80

The browser extension now detects PIIPIIPersonally Identifiable Information — data that can identify a specific individual, such as names, email addresses, or SSNs. Cyber tools flag or redact it to limit exposure and meet privacy regulations., secrets, or financial info typed into AI conversations and prompts employees to redact in one click or justify sending, configurable at Settings > In-browser nudges. An optional enforcement mode, configured at the same settings path, makes redaction the only way to send, preventing unredacted sensitive data from leaving the browser.

Enable sensitive data nudges with mandatory redaction so employees can never paste unredacted PII or secrets into AI tools.
📍In the console, go to Settings › In-browser nudges, enable sensitive data nudges, then turn on enforcement so redaction is required before sending.
— Names exact settings path and both modes; missing detection scope limits Nudge employees in the browser before they s…
Was this useful?

BeyondTrust

Sources Blog / feed → 1 release · 2026-08-13 Blog

BeyondTrust provides privileged access management and endpoint security solutions for controlling and monitoring user access to critical systems.

BeyondTrust's Endpoint Credential Manager 1.6.2606 adds configuration self-heal and environment-variable support for ConfigCLI, alongside a cluster of security hardening changes — per-installation credential-store encryption, enforced certificate revocation checking, and fail-closed log appenders — several of which require action before upgrading.

└──▷ WHAT SHIPPED · 8 FEATURES 3 OF 8 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 01
Per-installation credential store encryption breaking 85

Switches the credential store to per-installation encryption entropy, replacing a previously shared value; a new ECSM.entropy file is created in the install directory and should be backed up alongside ECSM.settings.

— Names exact new file and backup requirement before upgrading Endpoint Credential Manager 1.6.2606 release…
02 00
Environment-variable resolution in ConfigCLI new 75

Adds env: prefix support in ConfigCLI arguments so sensitive values can be resolved from environment variables instead of the command line, keeping them out of process creation logs.

— Names exact `env:` prefix and mechanism; usable in ConfigCLI today Endpoint Credential Manager 1.6.2606 release…
03 02
Enforced certificate revocation checking on appliance connection breaking 75

Enables certificate revocation checking on the appliance connection and enforces size limits on protocol and HTTP reads; CRLCRLA Certificate Revocation List is a signed file, published by a certificate authority, listing certificates it has revoked before expiry so that clients can reject compromised or mis-issued credentials without contacting the CA live./OCSPOCSPA protocol for checking whether a TLS certificate has been revoked, defined in RFC 6960, letting clients query a CA's responder in real time instead of downloading full CRL lists. endpoints must be reachable from the ECM host before upgrading.

— Gives concrete pre-upgrade check but no specific limit values Endpoint Credential Manager 1.6.2606 release…
04 00
Configuration self-heal on startup and install new 70

The ECM service and Configurator automatically detect and repair a missing or stale configuration file at startup and during installation, preserving appSettings, proxy, and log configuration while refreshing only version-driven sections.

— Clear mechanism and scope, but behavior is automatic, not user-triggered Endpoint Credential Manager 1.6.2606 release…
05 03
Log appenders fail closed on credential values breaking 70

Log appenders now fail closed rather than falling back to an unprotected credential value; plaintext credential values in log appender configuration must be re-encrypted before upgrading.

— Clear before/after and required pre-upgrade migration step Endpoint Credential Manager 1.6.2606 release…
06 00
Plugin loading diagnostics and hardening improved 65

Plugin load diagnostics now log assembly load failures with full detail, replacing the opaque Found 0 plugins message seen when tools such as WDAC, AppLocker, or EDREDREndpoint detection and response, monitoring computers for suspicious behavior and providing investigation and response controls, such as isolating a device. solutions block plugin loading; plugin loading is also hardened to load from the install directory rather than the process working directory.

— Names affected tools and message change; no direct reader action Endpoint Credential Manager 1.6.2606 release…
thinner coverage below
07 00
log4net dependency upgrade improved 35

Upgrades the log4net dependency from 3.1.0 to 3.3.1.

— Exact version numbers given but no behavioral detail Endpoint Credential Manager 1.6.2606 release…
08 00
Restricted configuration deserialization improved 15

Restricts configuration deserializationdeserializationTurning stored or transmitted data back into objects a program can use. Unsafe handling of untrusted data can allow unexpected behavior or code execution. to known types.

— One-line hardening note with no named types or scope Endpoint Credential Manager 1.6.2606 release…
└──▷ BREAKING ON UPGRADE
  • !
    Certificate revocation checking is now enforced on the appliance connection — CRL/OCSP endpoints must be reachable from the ECM host before upgrading.
  • !
    Plaintext credential values in log appender configuration must be re-encrypted before upgrading, as log appenders now fail closed rather than falling back to an unprotected credential value.
  • !
    The credential store now uses per-installation encryption entropy; a new ECSM.entropy file is created in the install directory and must be backed up alongside ECSM.settings.
Was this useful?

Okta Identity Engine

Sources Blog / feed → 1 release · 2026-08-12 Blog

Okta Identity Engine is a cloud-based identity platform providing authentication, authorization, and user management for applications.

Okta Identity Engine's biggest addition this window is multi-resource refresh tokensrefresh tokensA credential used to obtain a new access token without signing in again. It is sent to the authorization service rather than used directly to call the protected API. for custom authorization servers, alongside new granular admin permissions for user behavior detection, expanded dynamic zone IP categories, and GA promotions for a list-endpoint field filter and an identity verification integration.

└──▷ WHAT SHIPPED · 5 FEATURES 1 OF 5 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 01
Multi-resource refresh tokens on custom authorization servers new 95

/authorize endpoints on custom authorization servers now accept multiple resource parameters, letting a single refresh tokenrefresh tokenA credential used to obtain a new access token without signing in again. It is sent to the authorization service rather than used directly to call the protected API. cover multiple resources; each grant_type=refresh_token exchange then mints a precisely scoped, single-aud access tokenaccess tokenA credential that authorizes a client to use a service or API. It usually has limited permissions and a lifetime; anyone holding it may be able to use those permissions. for one resource, eliminating the need for one refresh token per resource. This is GA in Preview and requires an Okta for AI Agents subscription with agent-to-agent connections enabled.

Request a refresh token scoped to multiple resources at authorization time, then exchange it for a precisely scoped access token for one resource — eliminating the need for one refresh token per resource.
$ # Step 1: Authorize with multiple resource parameters
GET /oauth2/{authorizationServerId}/v1/authorize?client_id=<client_id>&response_type=code&scope=openid offline_access&resource=https://api.example.com/service-a&resource=https://api.example.com/service-b&redirect_uri=<redirect_uri>

# Step 2: Exchange the refresh token for a single-audience access token
POST /oauth2/{authorizationServerId}/v1/token
  grant_type=refresh_token
  &refresh_token=<refresh_token>
  &resource=https://api.example.com/service-a
  &client_id=<client_id>
— Full mechanism, exact endpoints, params, and a runnable example. product docs
02 00
Granular user behavior admin permissions new 60

Adds okta.users.behaviors.manage, okta.users.behaviors.read, and okta.users.behaviors.reset custom admin permissions for fine-grained control over user behavior detection.

— Names all three permission strings but no usage example. product docs
thinner coverage below
03 00
`fields` query parameter for list endpoints improved 40

New fields query parameter for Groups, Realms, and Devices list endpoints is now GA in Production.

— Names endpoints and parameter but gives no usage example. product docs
04 00
New IP service categories for dynamic zones improved 30

Adds new IP service categories for enhanced dynamic zones, expanding the criteria and classification options available when building network-based policies and defining dynamic network zones.

— Repeated across three releases but never names the actual categories. Weekly release 2026.08.1 (2026-08-12)
05 00
Submit Identity Verification integration GA improved 23

Submit Identity Verification integration is now GA in Production.

— Only a bare GA announcement with no detail on mechanism. product docs
Was this useful?
Governance, Risk & Compliance
◆  Continuous Control Monitoring (CCM)

RegScale

Sources Blog / feed → 1 release · 2026-08-13 Blog

RegScale is a compliance and regulatory management platform that automates governance, risk, and compliance (GRC) workflows for organizations.

RegScale's CLI 6.40.0 release adds a configurable artifact output directory and an optional Wiz data-retention reconciliation feature that auto-closes stale issues.

└──▷ WHAT SHIPPED · 2 FEATURES 0 OF 2 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Wiz data-retention reconciliation new 69

Adds optional reconciliation that closes RegScale issues whose findings have aged out of Wiz's retention window, enabled via wizRetentionReconciliation and tuned with additional w… settings.

Enable Wiz retention reconciliation to automatically close RegScale issues whose Wiz findings have aged out of Wiz's retention window.
yaml
wizRetentionReconciliation: true
— Explains behavior and config key but additional tuning settings are unnamed. CLI (2026-08-13)
02 00
Configurable artifact output directory new 65

Adds the artifactsDir setting to configure the base directory where scanner and integration output files are written, replacing the default location.

Set a custom output directory so all scanner and integration artifacts land in a dedicated path instead of the default location.
yaml
artifactsDir: /var/regscale/artifacts
— Names exact config key and example value, no further mechanism given. CLI (2026-08-13)
Was this useful?
Build
◆  AI Coding Agents

Daytona

Sources Release page → 1 release · seen 2026-08-14 Notes

Daytona is a development environment platform that enables standardized, reproducible coding spaces for teams and AI agents.

Daytona expanded its API with organization-level SSOSSOSingle sign-on, using one identity provider to sign in to multiple applications. It reduces separate passwords and centralizes account and access management./identity-provider management, new audit and runner-snapshot endpoints, and force/filter query parameters, alongside a broad wave of schema refinements across sandbox, organization, admin, and API-key endpoints; a separate 0.200.0 release enforced TLS verification and made SDK/CLI security tighter.

└──▷ WHAT SHIPPED · 8 FEATURES 1 OF 8 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
SSO identity provider and pending-link management endpoints new 88

Adds organization-level SSO/identity-provider CRUDCRUDThe four basic database operations — Create, Read, Update, Delete — used as shorthand for any system that manages persistent data records, giving cyber tools a standard model for interacting with stored information. and testing via POST /organizations/{organizationId}/identity-providers, GET /organizations/{organizationId}/identity-providers, GET /organizations/{organizationId}/identity-providers/{id}, PATCH /organizations/{organizationId}/identity-providers/{id}, DELETE /organizations/{organizationId}/identity-providers/{id}, and POST /organizations/{organizationId}/identity-providers/test-connection, plus POST /organizations/{organizationId}/sso-enabled to toggle SSO. User-facing pending SSO link handling is added via GET /users/me/pending-sso-links, DELETE /users/me/pending-sso-links/{id}, and POST /users/me/pending-sso-links/{id}/confirm.

— Ten concrete endpoints named with clear CRUD purpose 1.0
02 00
Force-delete and snapshot source filtering query parameters new 80

Adds a force query parameter to DELETE /admin/runners/{id} and DELETE /runners/{id}, and a sourceSandboxId query parameter to GET /snapshots for filtering snapshots by their originating sandbox.

— Exact params and endpoints named, directly usable 1.0
thinner coverage below
03 00
Configurable HTTP timeout in Go SDK new 45

Makes the HTTP timeout configurable in the Go SDK to honor long execution timeouts.

— States purpose but no config key or method name given snapshot-20260814
04 00
Restricted permissions on CLI config files improved 45

Creates CLI config files with 0600 permissions for tighter access control.

— Concrete permission value named but no file path given snapshot-20260814
05 00
Audit scenarios endpoint new 41

New GET /audit/scenarios endpoint added to the API.

— Endpoint named but purpose and response undescribed 1.0
06 00
Runner-scoped snapshots listing endpoint new 41

New GET /runners/me/snapshots endpoint added to list snapshots for the calling runner.

— Endpoint named but response detail unspecified 1.0
07 00
Schema updates across sandbox, organization, admin, and API-key endpoints improved 34

Request or response schemas changed with no described content beyond the change itself for a large set of endpoints. Sandbox lifecycle: DELETE /sandbox/{sandboxIdOrName}, DELETE /sandbox/{sandboxIdOrName}/ssh-access, GET /sandbox, GET /sandbox/for-runner, GET /sandbox/paginated, GET /sandbox/{sandboxIdOrName}, GET /sandbox/{sandboxIdOrName}/ancestors, GET /sandbox/{sandboxIdOrName}/forks, GET /sandbox/{sandboxIdOrName}/parent, GET /sandbox/{sandboxId}/organization, GET /sandbox/{sandboxId}/region-quota, POST /sandbox (request body and response schema changed), POST /sandbox/{sandboxIdOrName}/archive, POST /sandbox/{sandboxIdOrName}/autoarchive/{interval}, POST /sandbox/{sandboxIdOrName}/autodelete/{interval}, POST /sandbox/{sandboxIdOrName}/autopause/{interval}, POST /sandbox/{sandboxIdOrName}/autostop/{interval}, POST /sandbox/{sandboxIdOrName}/backup, POST /sandbox/{sandboxIdOrName}/fork, POST /sandbox/{sandboxIdOrName}/network-settings, POST /sandbox/{sandboxIdOrName}/pause, POST /sandbox/{sandboxIdOrName}/public/{isPublic}, POST /sandbox/{sandboxIdOrName}/recover, POST /sandbox/{sandboxIdOrName}/resize, POST /sandbox/{sandboxIdOrName}/snapshot, POST /sandbox/{sandboxIdOrName}/start, POST /sandbox/{sandboxIdOrName}/stop, POST /sandbox/{sandboxIdOrName}/ttl/{ttlMinutes}, PUT /sandbox/{sandboxIdOrName}/secrets. Organization and admin: GET /admin/organizations/{organizationId}/quota/{regionId}/{sandboxClass}, GET /admin/users/{id}, PATCH /admin/organizations/{organizationId}/quota/{regionId} (request body changed), PATCH /admin/snapshots/{id}/general, POST /admin/organizations, POST /admin/organizations/{organizationId}/quota/{regionId} (request body and response schema changed), POST /admin/sandbox/{sandboxId}/recover, POST /admin/users (request body changed), GET /organizations, GET /organizations/invitations, GET /organizations/{organizationId}, GET /organizations/{organizationId}/invitations, GET /organizations/{organizationId}/roles, GET /organizations/{organizationId}/users, PATCH /organizations/{organizationId}/quota/{regionId} (request body changed), POST /organizations, POST /organizations/invitations/{invitationId}/accept, POST /organizations/{organizationId}/invitations, POST /organizations/{organizationId}/roles (request body changed), POST /organizations/{organizationId}/users/{userId}/access, PUT /organizations/{organizationId}/invitations/{invitationId}, PUT /organizations/{organizationId}/roles/{roleId} (request body changed). API keys and snapshots: GET /api-keys, GET /api-keys/current, GET /api-keys/{name}, POST /api-keys (request body changed), GET /config, GET /users/me, GET /snapshots/{id}, POST /snapshots, POST /snapshots/{id}/activate.

— Endpoints named but actual schema change content unknown 1.0
08 01
Enforced TLS certificate verification breaking 21

Daytona 0.200.0 enforces TLS verification, per the release summary; no further mechanism or affected surfaces are described.

— Only a one-line summary, no detail on scope or migration snapshot-20260814
Was this useful?

Kiro

Sources Release page → 1 release · seen 2026-08-14 Notes

Kiro's 1.0.309 release adds support for nested AGENTS.md files for directory-scoped instructions, alongside efficiency improvements for long sessions and background resource usage.

└──▷ WHAT SHIPPED · 3 FEATURES 0 OF 3 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Nested AGENTS.md files for directory-scoped instructions new 55

Kiro now supports nested AGENTS.md files placed throughout the workspace, giving Kiro instructions that are scoped to each directory tree rather than a single workspace-wide file.

— Names the exact file and scoping behavior, no example given Nested AGENTS.md and Long-Session Efficiency
02 00
Long-session context retention and idle efficiency improved 25

Kiro preserves more context during long sessions, reducing loss of earlier conversation state, and reduces idle resource usage for improved background efficiency.

— Describes benefit but no mechanism or metrics given Nested AGENTS.md and Long-Session Efficiency
03 00
Cloud configuration, chat, hooks and MCP improvements improved 15

Kiro improves Cloud configuration, chat, hooks, and MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. connections, though the source does not specify what changed in each area.

— Bare list of areas with no detail on what changed Nested AGENTS.md and Long-Session Efficiency
Was this useful?

Cursor

Sources Release page → 1 release · seen 2026-08-14 Notes

Cursor is an AI-powered code editor built on VS Code that helps developers write, edit, and debug code faster using artificial intelligence.

Cursor shipped shareable deeplinks for prompts, commands, and rules, brought Bugbot PR review to Azure DevOps, and gave Cloud Agents pre-built environments that boot up to 3x faster.

└──▷ WHAT SHIPPED · 3 FEATURES 0 OF 3 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Bugbot PR review for Azure DevOps new 95

Bugbot now reviews Azure DevOps Services pull requests, posting review comments, inline comments, and build statuses under the cursor-bugbot/review context. On-demand reviews can be triggered with cursor review or bugbot run comments, restricted to users whose Azure DevOps sign-in address matches a Cursor account on the team. Repository settings let you disable Run for All Authors and configure 'Only Review PRs by...' or 'Skip PRs by...' using sign-in addresses (e.g. taylor@contoso.com) found under Organization settings → Users. A Microsoft Entra service principal is provisioned per tenant for all Bugbot actions so reviews survive role changes; service hooks install automatically when a repo is enabled under Bugbot in Automations and are removed when disabled or disconnected. Cloud Agents can also clone, push, commit, and open PRs on Azure DevOps using the connected identity. The integration is limited to team-scope repositories (personal-scope unsupported), and Auto-Enable for New Repositories, Automatically Learn Rules, Personal Bugbot settings, and Autofix are not supported — repo-level settings apply to all authors instead.

Trigger an on-demand Bugbot review on an open Azure DevOps pull request by posting a comment.
$ bugbot run
Enable Bugbot on specific Azure DevOps repositories and restrict reviews to a subset of authors by sign-in address.
📍In Cursor, open Bugbot in Automations, find your Azure DevOps repository, turn Bugbot on, disable Run for All Authors, and add sign-in addresses like taylor@contoso.com under 'Only Review PRs by...'.
— Named endpoints, settings, identity mechanism, and exact steps. product docs
02 00
Deeplinks for prompts, commands, and rules new 85

Adds shareable deeplinks using the cursor://anysphere.cursor-deeplink/ protocol or the cursor.com/link/ web base URL: prompt deeplinks via cursor://anysphere.cursor-deeplink/prompt?text=... (also cursor.com/link/prompt?text=...) share pre-filled chat prompts the recipient must confirm before execution; command deeplinks save shared custom commands into the recipient's .cursor/commands/ directory pending review; rule deeplinks save shared custom rules into .cursor/rules/ pending review. All deeplink URLs support a maximum encoded length of 8,000 characters.

Share a reusable chat prompt with a teammate so they can open it pre-filled in Cursor and confirm before running.
$ cursor://anysphere.cursor-deeplink/prompt?text=Research%20and%20find%20one%20bug%20in%20this%20codebase
— Names exact protocols, paths, and the 8,000-char limit. product docs
03 00
Pre-built environments for Cloud Agents new 85

Cloud Agents can now boot into Builds — pre-baked copies of the dev environment (repos cloned, dependencies installed, install script run) — instead of setting up from scratch each session, delivering 10x faster internal environment boot and 3x faster time to first tokentime to first tokenTime to first token, the wait between submitting a request and receiving the first generated token. It includes delays such as queuing and processing the prompt. at no additional cost. A Builds tab in the Cloud Agents dashboard shows build status, logs, commit SHAs, and which build each agent run used; builds can be triggered manually, debugged with an agent, and automatically fall back to the last successful build when a bad commit or dependency update breaks the environment. A configurable threshold controls how stale builds get refreshed, and agents can inspect and manage builds using built-in tools.

Enable Builds on an existing Cloud Agents environment to get faster agent starts without reconfiguring from scratch.
📍In the Cloud Agents dashboard, open your environment › go to the Builds tab › click Enable Builds. Optionally click Run setup agent first to preview any proposed config changes before enabling.
— Gives UI steps and metrics but no named config key. Cloud Agents Start 3x Faster with Builds
Was this useful?

Cline

Sources Release notes →Source code → 2 releases · 2026-08-14 Notes Code

Autonomous coding agent as an SDK, IDE extension, or CLI assistant.

Cline's SDK and CLI releases in this window add a provider-executed web_search model tool with persisted search history, a dedicated Cline gateway provider, and safer Hub session handling around updates and build swaps, alongside a refreshed model catalog with Crusoe support and streaming markdown fixes.

└──▷ WHAT SHIPPED · 8 FEATURES 2 OF 8 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
`cline doctor fix` honest process reporting improved 85

cline doctor fix now reports honestly: processes that survived a kill are separated from ones that appeared during the fix, a live parent respawning a daemon is named, and a startup lock held by a running process is reported as held rather than leaked.

— Names the exact command and each corrected behavior sdk/sdk/v0.0.75
02 00
Provider-executed web search tool new 80

Adds a web_search model tool, off by default and enabled in settings, letting supported models search the web during a turn; search calls and their results are persisted in session history for replay on reload.

Enable provider-executed web search so a supported model can look up live information mid-turn during an agent session.
📍In the Cline settings panel, locate the model tools section and enable the web_search tool, then start or resume a session — search calls and their results will be saved in session history and replayed on reload.
— Names exact tool, settings path, and usage steps sdk/sdk/v0.0.75
03 00
Safer auto-update sequencing for Hub sessions improved 80

Auto-updates no longer install while a CLI is attached to the Hub; the update is recorded at startup and installed on exit, preventing a background update from killing a live session (previously surfacing as Hub connection closed with code=1006). cline update still installs immediately and now reports that the update applies on next start.

— Names command and exact error code it fixes cli-v3.0.55
04 01
Dedicated Cline gateway provider new 70

Adds a dedicated Cline provider for the Cline gateway, replacing the generic OpenAI-compatible path, so extended thinkingextended thinkingIntermediate reasoning a model writes out before its final answer. Reasoning models generate it automatically and it is often billed as extra output tokens. budgets and other gateway options now apply to both cline and cline-pass models.

— Names affected models and provider path change sdk/sdk/v0.0.75
thinner coverage below
05 00
Streaming markdown rendering stability improved 55

Streaming assistant markdown no longer flashes back to raw text — settled headings, links, and code stay rendered as new chunks arrive instead of the whole message being rebuilt on every chunk.

— Explains behavior change with no config surface cli-v3.0.55
06 00
Hub build handoff without disrupting live sessions improved 50

Newer builds no longer replace a Hub serving live sessions — they attach over the compatible wire protocol and the swap happens once the Hub is idle. Development builds now run their own Hub daemon per build ID instead of contending for a single record.

— Describes mechanism but has no user-facing command sdk/sdk/v0.0.75
07 02
Crusoe provider and model catalog refresh new 40

The model catalog now includes Crusoe as a provider, with model lists and per-provider default models updated across all providers.

— Names new provider but no config detail given sdk/sdk/v0.0.75cli-v3.0.55
08 00
Idle plugin sandbox process cleanup improved 30

Idle plugin sandbox processes are now reclaimed instead of lingering for the life of the session.

— Brief description with no mechanism or command sdk/sdk/v0.0.75cli-v3.0.55
Was this useful?

OpenAI Codex CLI

Sources Release notes →Source code → 2 releases · 2026-08-14 Notes Code

Lightweight coding agent that runs in your terminal

Across two alpha releases, Codex CLI added an Amazon Bedrock Runtime model provider, skill-level model delegation to Luna, and per-server MCP OAuthMCP OAuthAn authentication layer for the Model Context Protocol that lets MCP clients obtain delegated access tokens so cyber tools can call MCP servers on a user's behalf without handling raw credentials. callback ports, alongside session, Guardian, and telemetry improvements.

└──▷ WHAT SHIPPED · 0 FEATURES9 FEATURES 1 OF 9 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Per-server MCP OAuth callback port new 90

Adds oauth.callback_port to MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. server configuration so each server can use its own OAuth callback port instead of the global mcp_oauth_callback_port; also accepts oauth.callbackPort from plugin MCP declarations and skill dependency metadata.

Configure a per-server OAuth callback port so that an MCP server uses port 9005 instead of the global default during codex mcp login.
yaml
oauth:
  callback_port: 9005
— Named config key plus runnable YAML example rust-v0.148.0-alpha.14
02 00
Skill-level model delegation to Luna new 80

Skill frontmatter now supports an optional model field (e.g. model: luna) letting a skill declare a preferred model; unrecognized values are ignored without blocking the skill. A new SkillModelDelegationInstruction routes skills requesting Luna while running on Sol or Terra to Luna when available in the current provider namespace, with bounded and validated model identifiers and instruction size limits.

— Concrete frontmatter example and named mechanism, but no full config path rust-v0.148.0-alpha.15
03 01
Amazon Bedrock Runtime model provider new 75

Adds the built-in amazon-bedrock-runtime provider for regional bedrock-runtime OpenAI-compatible endpoints, with SigV4SigV4AWS's request-signing protocol that authenticates HTTP calls by hashing the request body, headers, and credentials into a signature; cyber tools use it to talk to AWS APIs without embedding long-lived secrets. auth, per-provider AWS profile, region, and transport overrides, global and US cross-region GPT-5.6 model variants; web search is disabled since it is unsupported on Bedrock.

— Names provider id and auth/config options but no exact config key shown rust-v0.148.0-alpha.15
04 00
Preserved developer messages across compaction improved 65

Client-authored developer messages are now preserved across context compactioncontext compactionCondensing an AI conversation or working history to free space in the model's context window. A summary preserves useful information, but details can be lost. when retain_client_developer_messages is enabled.

— Named flag but no file location or default given rust-v0.148.0-alpha.14
thinner coverage below
05 00
Guardian review evidence and context improvements improved 57

Guardian V2 now receives full tool action context — the original ToolPayload including tool name and arguments plus a bounded conversation transcript — for richer risk classification, and Guardian review evidence now includes node_repl images.

— Names payload and evidence types but no config surface to invoke rust-v0.148.0-alpha.14
06 00
Running-task exit choices on Ctrl-C new 55

Pressing Ctrl-C while a task is running in local daemon sessions now shows a menu to cancel the task and stay in Codex, exit Codex while leaving the task running, or stop the task and exit Codex.

— Describes UI behavior with a clear trigger but no flag/command rust-v0.148.0-alpha.14
07 00
Current-time reminder handling in model context improved 50

Injected current-time reminders are now wrapped in <current_time_reminder> tags in model context, and full-history subagents get a refreshed reminder by excluding parent reminders and injecting a single fresh reminder into the child request.

— Named tag format but no user-facing control rust-v0.148.0-alpha.14
08 00
Experimental thread queue APIs new 23

Adds experimental thread queue APIs to the app server.

— Bare mention with no endpoint names or usage detail rust-v0.148.0-alpha.14
09 00
Structured telemetry for response retries new 16

Adds structured telemetry for response retries.

— One-line mention with no schema or access point rust-v0.148.0-alpha.14
Was this useful?

Claude Code

Sources Release notes →Source code → 1 release · 2026-08-13 Notes Code

Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.

Claude Code v2.1.232 introduces cross-session @-mentions and per-session messaging controls, turns on subagent forking by default, adds GitLab secret redaction and full GitLab plugin marketplace support, and tightens gateway and sandbox settings with new boot-time validation.

└──▷ WHAT SHIPPED · 13 FEATURES 3 OF 13 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
GitLab support and settings aliases for plugin marketplaces new 85

Bare gitlab.com repo URLs (including nested subgroups) now clone like github.com URLs for plugin marketplaces. Settings now accept additionalMarketplaces and allowedMarketplaces as friendlier aliases for extraKnownMarketplaces and strictKnownMarketplaces. An enterprise-policy url-typed blockedMarketplaces entry for a bare repo URL continues blocking that URL even when the CLI classifies it as a git clone.

Block a private GitLab plugin marketplace from being used, even when the CLI identifies the URL as a git clone.
json
{
  "blockedMarketplaces": [
    { "type": "url", "value": "gitlab.com/my-org/internal-plugins" }
  ]
}
Use the friendlier allowedMarketplaces alias in settings instead of the legacy strictKnownMarketplaces key to restrict which marketplaces Claude Code may use.
json
{
  "allowedMarketplaces": [
    "gitlab.com/my-org/approved-plugins"
  ]
}
— Config keys and behavior both named with runnable examples. v2.1.232
02 00
Cross-session @-mentions and messaging controls new 83

Typing @ in the prompt now mentions another Claude session by name, using SendMessage to reach that session directly; SendMessage also delivers to a bare name that exactly matches one live session without a confirmation step. New /config rows for Dialog expiry and Messages from your other sessions let you set per-session inbound messaging to accept, hold, or refuse. Interactive sessions on one machine now keep unique names — renaming to a name already in use generates a name-word-word variant and notifies the user.

Configure cross-session messaging policy so inbound messages from your other sessions are held for review rather than accepted automatically.
📍/config
— Names exact commands and config rows, mechanism explained. v2.1.232
03 01
Gateway config validation at boot breaking 80

The desktop: overlay now accepts every released Desktop setting (previously limited to 11 hand-listed keys), validated at boot against Desktop's own schema, with unknown or invalid keys now failing boot. Empty managed.policies[].match.groups / admin.admin_groups entries and malformed email_domain values (empty, or containing @, whitespace, or commas) now fail at boot instead of silently matching no one or granting admin access.

— Names exact config keys and boot-failure conditions. v2.1.232
04 02
GitLab token redaction new 75

Adds secret redaction for GitLab token families glrt-, gloas-, glptt-, glagent-, glimt-, glsoat-, glcbt-, glft-, and glffct-; fully redacts routable glpat- and gldt- tokens; extends the same sandbox and credential-path protection to the glab CLI config store.

— Every token prefix named but no user action required. v2.1.232
05 00
Managed settings approval dialog improvements improved 65

The managed settings approval dialog now shows endpoint URLs, uses clearer wording for telemetry-only changes, skips routine OpenTelemetryOpenTelemetryAn open standard and set of tools for collecting traces, metrics and logs from applications. It lets services export observability data without tying instrumentation to one monitoring vendor. options, and requires explicit approval for server-managed sandbox binary overrides (sandbox.bwrapPath, sandbox.socatPath, sandbox.ripgrep).

— Names the specific override keys the dialog now gates. v2.1.232
06 03
Sandbox ripgrep binary setting restricted to trusted scopes breaking 60

sandbox.ripgrep is now honored only from user, managed, and --settings settings; project settings can no longer override the sandbox's ripgrep binary.

— Names the exact key and scopes but no example given. v2.1.232
07 00
Fable 5 advisor restored improved 60

Fable 5 is offered again as an advisor in /advisor for organizations with Fable access, with usage-credits consent set up through /model fable.

— Gives exact commands to access the restored advisor. v2.1.232
08 00
Marketplace auto-refresh on plugin install improved 60

/plugin install plugin@marketplace now refreshes the marketplace first, so newly published plugins install without a manual marketplace update.

— Names the exact command whose behavior changed. v2.1.232
thinner coverage below
09 00
Subagent forking enabled by default improved 55

A subagent_type: "fork" subagent now inherits the full conversation and prompt cache by default, and non-teammate agent spawns in interactive sessions now run in the background by default.

— Explains new default behavior, no config surface given. v2.1.232
10 00
/feedback and /bug open immediately improved 45

/feedback and /bug now open immediately when invoked while Claude is responding, instead of waiting for the turn to finish.

— Names exact commands but change is minor UX timing. v2.1.232
11 00
/code-review high-effort runs as background agent improved 45

/code-review at high, xhigh, and max effort now runs in a background agent, consistent with other effort levels.

— Names the command and effort levels affected. v2.1.232
12 00
Permission checks for bash input redirection improved 40

Bash input redirections (< file) are now permission-checked like their argument spellings, on all platforms.

— Brief statement of behavior change, no further detail. v2.1.232
13 00
Remote Control reconnection reliability improved 40

Remote Control now reconnects for approximately 30 minutes after a network blip and no longer drops after a few blips spread across an hour.

— Gives a concrete duration but no config or command. v2.1.232
└──▷ BREAKING ON UPGRADE
  • !
    sandbox.ripgrep set in project settings is no longer honored; it must now be placed in user, managed, or --settings settings.
  • !
    Gateway: unknown or invalid keys under the desktop: overlay now fail boot (previously accepted silently).
  • !
    Gateway: empty managed.policies[].match.groups / admin.admin_groups entries and malformed email_domain values now fail at boot instead of silently matching no one or granting admin access.
Was this useful?
Agent
◆  AI Agent Frameworks

CrewAI

Sources Release notes → 1 release · 2026-08-14 Notes

Framework for orchestrating role-playing, autonomous AI agents. By fostering collaborative intelligence, CrewAI empowers agents to work together seamlessly, tackling complex tasks.

CrewAI 1.15.16 focuses on execution observability, adding UUIDUUIDA universally unique identifier, usually a 128-bit value used to identify an object across systems. It is designed to make independently generated identifiers unlikely to collide.-based tracking for flow and agent runs plus richer AMP deployment telemetry.

└──▷ WHAT SHIPPED · 2 FEATURES 0 OF 2 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Flow execution tracking and exception recording new 38

Adds execution context management with UUID support for tracking individual flow and agent executions, and records the type of exception that ended a flow so observability pipelines get structured failure context.

— Describes what changed but no concrete API or field names given. 1.15.16
02 00
AMP deployment telemetry improved 35

Records when a trace batch is shared with AMP for auditable telemetry handoff visibility, and counts deployments from any origin while recording where they started, supporting multi-origin deployment tracking in AMP.

— Explains behaviour but lacks specific endpoints or config to act on. 1.15.16
Was this useful?

Hermes

Sources Release notes →Source code → 1 release · 2026-08-13 Notes Code

The agent that grows with you

Hermes shipped a full community plugin management CLI (install, search, doctor, and pack commands) alongside new desktop ws RPCs for profiles and image generation, an inline MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. setup consent tool, a concise messaging mode, an installer flag to skip bundling cua-driver, and a relaxed approval-gated policy for editing ~/.ssh/config.

└──▷ WHAT SHIPPED · 11 FEATURES 0 OF 11 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Plugin management CLI for community plugins new 100

New CLI surface for installing and vetting community plugins: install <identifier> [--force] [--ref COMMIT_SHA] installs from a Git URL or bare community index name, with --ref accepting a full 40-character commit SHA to pin an exact immutable revision; search [term] [--json] [--capability CAP] [--refresh] fuzzy-searches the community index (fetched from plugins.index_url, cached under ~/.hermes/cache/ for 24 hours with offline fallback); doctor [path-or-id] [--ci] validates a plugin through the real manifest parser, loader, and registration path, with --ci exiting code 1 on errors for CI pipelines; pack install <path-or-url> [--force] installs a hermes-pack.yaml plugin pack whose plugins are each pinned to an exact 40-character commit SHA, behind a mandatory review screen and per-plugin capability consent, exiting non-zero on any plugin failure; pack export [--enabled-only] [--name NAME] emits a hermes-pack.yaml to stdout recording repo and exact SHA per git-installed plugin while stripping secrets, capability grants, and allow_* gates; and pack show <path-or-url> dry-runs a pack without installing. Git installs record source, revision, and pin status in the plugins/.install-metadata.json sidecar (never secrets or grants); unpinned plugins update via pull, while pinned plugins require --force --ref <new-commit> to move revision.

Pin a community plugin to an exact immutable commit SHA so your environment never drifts on upgrade.
$ hermes install my-plugin --ref a3f1c2e4b5d6789012345678901234567890abcd
Find plugins that expose a specific capability before committing to an install.
$ hermes search --capability network_access --json
Validate a plugin in CI and fail the build immediately if the manifest or loader registration has errors.
$ hermes doctor ./my-plugin --ci
— Every subcommand, flag, and file path is named with runnable examples. product docs
02 00
profiles.list and profiles.create ws RPCs new 95

profiles.list and profiles.create ws JSON-RPCRPCRemote Procedure Call, a protocol that lets a program execute a function on another machine as if it were local, giving cyber tools a structured way to communicate across processes or hosts without managing raw sockets. methods, implemented in tui_gateway/methods_profiles.py, let desktop plugins enumerate profiles (name, path, model/provider, description, skill_count, and an optional last_session preview via include_sessions) and create new profiles without going through the dashboard REST router.

List all profiles from a desktop plugin to build a roster UI, including a last-session preview per profile.
$ { "method": "profiles.list", "params": { "include_sessions": true } }
— Named RPC methods, fields, and file, with a runnable example. v2026.8.13
03 00
Approval gating for `~/.ssh/config` edits improved 83

~/.ssh/config is promoted from hard-blocked to approval-gated: edits to SSH client config such as host aliases, ProxyJump, and VS Code Remote-SSH targets now go through the same approve-once/session/always prompt used for other ~/.ssh writes instead of a flat refusal. Non-interactive callers (the ACP file bridge, background jobs with no human channel) still fail closed on ~/.ssh/config writes, and private keys, authorized_keys, and all other material under ~/.ssh remain hard-blocked regardless of approval state.

— Names exact paths and exceptions; behavioral not a runnable command. product docs
04 00
Installer skip-Computer-Use flag new 80

The installer adds a --skip-computer-use flag to opt out of pre-installing cua-driver; without it, cua-driver is bundled automatically so the Computer Use toolset is ready as soon as it's enabled.

— Exact flag and default behavior given, mechanism is minimal. product docs
05 00
Concise messaging verbosity mode new 65

Adds a concise messaging mode (the new default) that surfaces a one-line status message on completion, with a short output tail appended on failure, joining the existing all, result, error, and off modes.

— Names all mode values but not the setting used to switch modes. product docs
thinner coverage below
06 00
Inline MCP setup consent tool new 55

Adds a setup_mcp tool that renders an inline MCP consent card in the desktop transcript using a clarify-style blocking bridge, with composer draft suggestions surfaced as brand pills.

— Mechanism described but no command or config to invoke it. v2026.8.13
07 00
Desktop composer suggestion improvements improved 55

Labels the agent's recommended choice on clarify surfaces across the desktop UI; adds skill-match, connection-repair, and recurrence-to-cron suggestion providers to the desktop composer; and suppresses composer suggestions the user has repeatedly ignored.

— Names three suggestion providers but no config surface to tune them. v2026.8.13
08 00
image.generate ws RPC new 35

Adds an image.generate ws RPC for plugin surfaces.

— Bare method name with no parameters or usage shown. v2026.8.13
09 00
Cron and blueprint recipes in sidebar nav new 30

Adds cron and blueprint recipes to the sidebar nav rail.

— Names the UI location but no further detail on the recipes. v2026.8.13
10 00
Per-route webhook toolset overrides new 25

Adds per-route toolset overrides for webhook agent runs.

— No config key, route, or example given. v2026.8.13
11 00
Model drift indicator in Desktop cron view new 25

Surfaces model drift impact in the Desktop cron view.

— One-line description with no mechanism or metric detail. v2026.8.13
Was this useful?
Deploy
◆  Local LLM Runtimes

vMLX

Sources Release notes → 1 release · 2026-08-14 Notes

vMLX - JANGTQ Uber Compressed MLX Models - L2 Disk Cache (survives restart) + L1 Paged (super fast ttft) + Hybrid SSM Scheduler + Cont Batching + etc!

vMLX added native support for the Qwen3.6-27B model bundle with automatic multi-token prediction, measuring a 33% throughput gain with no configuration required.

└──▷ WHAT SHIPPED · 1 FEATURE 1 OF 1 FEATURE most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 01
Qwen3.6-27B bundle support with auto multi-token prediction new 76

vMLX now supports the Qwen3.6-27B bundle line (and the upcoming Qwen 3.8 line): the qwen3_coder tool-parser name resolves to the XML-function parser, capability-only stamps route through the stock loader instead of the JANG codec, and the bundled multi-token prediction (MTP) head is automatically constructed, quantizedquantizedStoring a model's weights at lower numeric precision, such as 8 or 4 bits instead of 16, so it needs less memory and runs faster. It trades a small amount of accuracy for fitting on smaller hardware. per the stamp's per-module overrides, and engaged at the stamp's trained speculative depth — no flags required. Measured throughput on the 4-bit Qwen3.6-27B bundle went from 23.3 to 31 tokens/sec (+33%), with greedy output byte-identical whether the MTP head is on or off, and image/video probes answering correctly through both API and app.

— Names parser, loader routing, quantization mechanism and exact benchmark numbers. v1.6.28
Was this useful?
◆  Agentic Infrastructure

Ollama

Sources Release notes →Source code → 1 release · 2026-08-14 Notes Code

Get up and running with Kimi-K2.6, GLM-5.2, MiniMax, DeepSeek, gpt-oss, Qwen, Gemma and other models.

Ollama v0.32.11 adds one-command launchers for two external agent tools, extends prompt template support to Nemotron 3.5, and brings web search to the OpenAI Responses API.

└──▷ WHAT SHIPPED · 3 FEATURES 0 OF 3 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Agent harness launchers for DeepSeek and Meta tools new 70

Adds ollama launch dsh to integrate DeepSeek Harness, DeepSeek's open-source agent harnessagent harnessThe software around an AI agent that manages its tools, execution loop, state and limits. It determines how the model's proposed actions are run and checked., and ollama launch muse to integrate Muse Code, Meta's agentic coding CLI, letting either be run locally backed by an Ollama model.

Launch DeepSeek's open-source agent harness locally through Ollama.
$ ollama launch dsh
Launch Meta's Muse Code agentic coding CLI backed by a local Ollama model.
$ ollama launch muse
— Names exact commands but no further mechanism detail v0.32.11
thinner coverage below
02 00
Nemotron 3.5 prompt layout support new 35

Adds support for the Nemotron 3.5 prompt layout, selecting the correct parser and renderer from its checkpoint template.

— Explains mechanism but no usage example given v0.32.11
03 00
Web search in OpenAI Responses API new 25

Brings web search to the OpenAI Responses API.

— Only mentioned in summary, no mechanism or config detail v0.32.11
Was this useful?

emisar

Sources Release notes → 1 release · 2026-08-13 Notes

An MCP that lets AI tools securely connect to your infrastructure, write IaaS code, debug issues, and assist during incidents - without risking production stability. Built for security teams to approve and infrastructure teams to experience like magic.

emisar v0.40.0 adds self-updating runners with verified binary swaps, pagination for large MCPMCPModel Context Protocol, a standard for connecting AI applications to external tools and data sources. A compatible server exposes capabilities an assistant can use through a common interface. runbook results, and expands its integration catalog to 100 packs while tightening scope enforcement across discovery surfaces.

└──▷ WHAT SHIPPED · 5 FEATURES 0 OF 5 FEATURES most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Self-updating runners via `emisar update` new 88

The new emisar update subcommand lets installer-managed runners update themselves, performing automatic release-checksum and GitHub build-attestation verification before executing stop, swap, restart, and rollback steps.

Update an installer-managed runner in place — the runner verifies checksum and attestation before swapping binaries.
$ emisar update
— Runnable command with clear verification and rollback mechanism described. v0.40.0
02 00
JSON output for pack updates improved 77

The --json flag on emisar pack update now emits its partial report before returning a post-update validation error, preserving machine-readable output for automation pipelines even on failure.

Capture machine-readable pack-update output even when post-update validation fails, so CI pipelines can parse the partial report.
$ emisar pack update --json
— Exact flag and behavior on failure named, runnable example given. v0.40.0
03 00
Paginated results for wait_for_run improved 60

wait_for_run now returns paginated 64 KiB continuation pages when a terminal runbook result exceeds one MCP response, keeping the summary in the first response.

— Mechanism and size limit named but no direct usage example. v0.40.0
thinner coverage below
04 00
Catalog expands to 100 packs, 1,682 actions new 54

The catalog now covers 100 packs and 1,682 actions, adding JFrog Artifactory, Databricks, Sentry, Symbolicator, and NTPsec, along with larger Cassandra and Cloudflare coverage.

— Concrete counts and integrations named, but no usage detail given. v0.40.0
05 00
Scope enforcement for discovery across console and MCP improved 46

Runner, pack, action, approval, and audit discovery now enforces the member's current runner and pack scope consistently across both the console and MCP.

— States what changed but no mechanism or configuration path given. v0.40.0
Was this useful?
Govern
◆  AI/LLM Security

NVIDIA OpenShell

Sources Release notes → 1 release · 2026-08-13 Notes

OpenShell is the safe, private runtime for autonomous AI agents.

OpenShell added lifecycle control for sandboxes, letting users stop and start them via the CLI.

└──▷ WHAT SHIPPED · 1 FEATURE 0 OF 1 FEATURE most completely described first
what'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–40 what it does and how it works or what changed
  • specificity0–30 names real surfaces — APIs, flags, formats, limits, numbers
  • actionability0–30 enough 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 00
Stop and start operations for sandboxes new 60

The openshell sandbox subcommand gains stop and start operations, enabling lifecycle control of running sandboxes.

— Names exact subcommand and operations but no further mechanism. v0.0.105
Was this useful?
browse all tools → score card for your toolchain →