The daily firehose — everything the toolchain shipped today, already filtered.
// HOW THIS ISSUE IS MADE
We read every release from the 174 tools on our watchlist at the source — GitHub and GitLab release notes, vendor release pages and changelogs, project blogs and feeds, vendor press releases, and the source code behind the tag. Bug-fix-only releases and non-product newsroom noise are dropped; what's left is summarized down to the new capability, how to try it, and any screenshots or videos the release itself published. Every entry links to the sources it was built from.
Autonomous AI pentesting agents — real-time reconnaissance, vulnerability detection, and exploitation orchestration. Go + TypeScript.
Xalgorix v4.6.5 adds opt-in Discord and Telegram notifications when a scan completes.
└──▷ WHAT SHIPPED · 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Scan-completion notifications via environment variableNEW70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
A new XALGORIX_NOTIFY_SCAN_COMPLETE environment variable (default false) opts in to Discord and Telegram notifications when a scan completes, separate from the existing per-vulnerability alerts.
— Names exact env var and default but no further mechanism detail.v4.6.5
Run, train, and serve open-source AI models on Together AI.
Together AI added a new tg batches CLI command group for managing batch jobs, plus console improvements for API key expiration, Vercel integration key provisioning, and project collaborator management.
└──▷ WHAT SHIPPED · 4 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Batch job management via `tg batches` CLINEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
New tg batches command group added to the Together CLI, including tg batches submit (upload a local JSONL file or pass an existing file ID to create a batch job), tg batches list, tg batches get (alias ls), tg batches cancel, and tg batches download (streams results to stdout or writes output/error files to disk with --output).
Per-project API keys for Vercel integrationNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Connecting a Vercel project via Integrations settings now creates a dedicated API key per linked Vercel project, automatically set as the TOGETHER_API_KEY environment variable in that Vercel project.
Configurable API key expirationNEW60how completely this was documenteddepth20/40specificity20/30actionability20/3060 / 100
API key expiration is now configurable at creation time in the console, with options for 1 hour, 1 day, 7 days, 30 days, or a custom date via Set an expiration date.
Create a project API key with a 7-day expiration to issue short-lived credentials for a contractor or CI pipeline.
📍In the console, go to Settings › API Keys, click 'Create API key', select 'Set an expiration date', choose '7 days', and save.
Project collaborators can leave projectsNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Project collaborators can now leave a project themselves from Settings > Project > Collaborators or the Projects list; organization members cannot leave the default project, and the last admin must promote another before leaving.
Groq is a high-speed AI inference platform that runs large language models extremely fast with minimal latency.
└──▷ TRY IT
Invoke the new 20B reasoning model via the Groq chat completions API — useful for agentic workflows requiring fast inference with built-in tool use.
$ curl https://api.groq.com/openai/v1/chat/completions \
-H "Authorization: Bearer $GROQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "openai/gpt-oss-20b", "messages": [{"role": "user", "content": "Explain why fast inference is critical for reasoning models"}]}'
Switch to the 120B variant for higher-accuracy tasks such as health or multilingual reasoning, targeting the same endpoint with a model swap.
$ curl https://api.groq.com/openai/v1/chat/completions \
-H "Authorization: Bearer $GROQ_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model": "openai/gpt-oss-120b", "messages": [{"role": "user", "content": "Summarize this patient case and flag any clinical risks"}]}'
›Both models support structured outputs and multilingual reasoning, with the 20B variant scoring 98.7% on AIME 2025 (math with tools) and 60.7% on SWE-Bench Verified, and the 120B variant scoring 90.0% MMLU and 62.4% SWE-Bench Verified.
OpenAI provides APIs and tools for accessing advanced language models like GPT for building AI-powered applications.
OpenAI added hard monthly spend limits for organizations and projects, cutting off API access once a configured cap is reached.
└──▷ WHAT SHIPPED · 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
thinner coverage below
01
Hard monthly spend limits for orgs and projectsNEW58how completely this was documenteddepth25/40specificity18/30actionability15/3058 / 100
Organizations and projects can now set hard monthly spend limits; once tracked spend reaches the configured cap, API requests return a 429 error.
— Names mechanism and error code but no config path or API detail.snapshot-20260831
Graph-Native Infrastructure for Context and Accountable AI Systems
Semantica's v0.6.5–v0.6.7 releases lock down the Explorer API with mandatory SEMANTICA_API_KEY authentication and close SSRF, injection, XXE and DoS gaps across ingestors and graph-store backends, while adding a public SHACL validation API, LangChain and SAP OData integrations, an embedded Oxigraph triplet store, and full PROV-O provenance trust with hash-chained integrity and new CLI verification commands.
└──▷ WHAT SHIPPED · 21 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Explorer API authentication enforcementBREAKING90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
Adds SEMANTICA_API_KEY enforcement via Depends(require_auth) on X-API-Key across all 11 Explorer API routers; the API now fails closed with HTTP 503 when the key is unset. SEMANTICA_ALLOW_ANONYMOUS=true is an explicit opt-out for local/dev use, replacing the previous silent anonymous-allow behavior.
Lock down the Explorer API in a production deployment by requiring an API key, while keeping anonymous access available in a local dev environment.
$ # production
export SEMANTICA_API_KEY=your-secret-key
# local dev only — explicit opt-out of auth
export SEMANTICA_ALLOW_ANONYMOUS=true
— Complete before/after with exact env vars and example.v0.6.5
02
PROV-O provenance trust and integrityNEW90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
Adds full PROV-O completeness to ProvenanceManager: invalidation-instead-of-delete tombstoning, hash-chained integrity via verify_chain(), typed Agent/Activity records, downstream lineage traversal, W3C PROV-O qualified relations, bitemporal and Bundle support, and a configurable namespace. New CLI commands semantica provenance invalidate, semantica provenance verify-chain, and semantica provenance descendants expose these operations, and every ingestion module now persists to a global default SQLite-backed audit trail instead of silently falling back to in-memory storage.
— Names CLI commands and mechanisms; missing usage example.v0.6.5
03
Embedded Oxigraph TripletStore backendNEW85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
Adds an embedded Oxigraph backend for TripletStore via pip install 'semantica[tripletstore-oxigraph]' — runs in-process with pyoxigraph, requires no external SPARQL server, and persists to a local directory or runs in memory.
Use the embedded Oxigraph backend to run a SPARQL 1.1 store in-process without standing up Blazegraph, Jena, or RDF4J.
$ pip install 'semantica[tripletstore-oxigraph]'
— Install command and mechanism given, complete.v0.6.5
04
SSRF protection for ingestorsNEW70how completely this was documenteddepth25/40specificity30/30actionability15/3070 / 100
Adds a shared validate_url_for_request() SSRF guard wired into WebIngestor, SitemapCrawler, and RESTIngestor; an allow_private_ips opt-in remains available on seed ingestion for trusted internal API sources that need to bypass the default guard.
— Names guard function, ingestors, and opt-in flag.v0.6.6v0.6.5
05
Injection hardening across graph store backendsNEW70how completely this was documenteddepth30/40specificity30/30actionability10/3070 / 100
Adds shared semantica/graph_store/query_sanitize.py to validate every Cypher label, relationship-type, and property-key interpolation site across the Neptune, Neo4j, and FalkorDB backends, and adds sparql_escaping.validate_uri() at every IRI interpolation site across the Blazegraph, RDF4J, and Jena backends to block SPARQL injection.
— Names exact modules and backends but no user-facing action.v0.6.5
06
SPARQL route DoS hardeningNEW70how completely this was documenteddepth30/40specificity30/30actionability10/3070 / 100
Adds a 50,000 node/edge cap on SPARQL graph materialization to prevent unbounded DoS, plus a 10,000-character defense-in-depth query length cap on the SPARQL route alongside a rewritten _PREFIX_DECL regex to close a polynomial-time ReDoS path.
— Concrete limits named but no configuration control given.v0.6.5
07
VectorStore JSON serialization replaces pickleBREAKING65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Replaces pickle.load() in VectorStore.save()/load() with JSON serialization; legacy .pkl files are now refused rather than deserialized, so old pickle files must be regenerated.
— Clear migration note but no exact regeneration command.v0.6.5
08
Public SHACL validation APINEW60how completely this was documenteddepth15/40specificity20/30actionability25/3060 / 100
Adds run_shacl_validation as a public API for programmatic SHACL constraint validation against a graph, letting violations be surfaced before an audit export.
Validate a populated knowledge graph against SHACL constraints to surface policy violations before an audit export.
python
from semantica.ontology import run_shacl_validation
results = run_shacl_validation(graph)
for violation in results:
print(violation)
— Runnable example given but no mechanism beyond the call.v0.6.7
09
Altair Anzo triplet store backendNEW60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
Adds Altair Anzo as a fourth triplet store backend — a peer to Blazegraph, RDF4J, and Jena — speaking plain SPARQL 1.1 over HTTP with no new dependency required.
— Named backend and protocol but no setup instructions.v0.6.5
thinner coverage below
10
LangChain integration extrasNEW55how completely this was documenteddepth10/40specificity20/30actionability25/3055 / 100
Adds semantica[langchain] extras install for first-class LangChain integration, wiring agent pipelines into graph-native context and provenance.
Install Semantica with LangChain integration to wire agent pipelines into graph-native context and provenance.
$ pip install 'semantica[langchain]'
— Install command given, no further integration detail.v0.6.7
11
SAP OData ingestor extrasNEW55how completely this was documenteddepth10/40specificity20/30actionability25/3055 / 100
Adds semantica[ingest-sap] extras install for a new SAP OData ingestor, pulling enterprise data directly into a knowledge graph.
Install Semantica with SAP OData ingestion support to pull enterprise data directly into a knowledge graph.
$ pip install 'semantica[ingest-sap]'
— Install command given, no ingestion mechanics described.v0.6.7
12
Reasoning Action layerNEW55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
Adds a reasoning Action layer supporting rule-driven Assert, Retract, Call, and EmitEvent actions with optional provenance tracking.
Origin validation on graph-updates WebSocketNEW55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
Adds Origin validation on the /ws/graph-updates WebSocket handshake, checked against the same allowlist already enforced by CORSMiddleware for HTTP.
— Names endpoint and mechanism but no config example given.v0.6.5
15
Markdown round-trip export for AgentMemoryNEW55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Adds Markdown round-trip export/import for AgentMemory — a human-editable, diff-friendly alternative to JSON serialization, with atomic upsert-by-ID import.
— Explains mechanism but no example command.v0.6.5
16
Supply chain hardening for releasesNEW55how completely this was documenteddepth25/40specificity25/30actionability5/3055 / 100
Adds SLSA build provenance attestation and a protected pypi GitHub Environment; all third-party GitHub Actions across 8 workflows are now pinned to full commit SHAs, with a CI check that fails closed on any non-SHA uses: reference.
— Internal CI hardening, no direct reader action.v0.6.5
17
XXE prevention in RDF/XML parserNEW50how completely this was documenteddepth20/40specificity25/30actionability5/3050 / 100
Adds defusedxml as a declared dependency and uses _safe_parse_rdf() to prevent XXE in the RDF/XML parser; fails closed if defusedxml is not importable.
— Names function and dependency but no user action needed.v0.6.5
18
ContextGraph persistence and fact managementNEW45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
ContextGraph gains Markdown round-trip persistence — graphs can now be serialized to and loaded from Markdown — plus new retraction and purge methods for removing facts from the graph.
— Named methods but no usage example or signature.v0.6.7v0.6.6
19
Declared Semantica RDF vocabularyNEW35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
Introduces a declared Semantica RDF vocabulary with deterministic entity/relationship IRIs.
— No example of vocabulary use or IRIs given.v0.6.6
20
Markdown content viewer in Explorer UINEW30how completely this was documenteddepth10/40specificity10/30actionability10/3030 / 100
Adds a read-only Markdown content viewer and source view to the Explorer UI.
— Thin UI description, no navigation path given.v0.6.7
21
Timezone-aware timestamps in export and provenanceIMPROVED30how completely this was documenteddepth10/40specificity15/30actionability5/3030 / 100
Adds timezone-aware timestamps across export/ and provenance/ modules.
— Names modules affected but no further detail.v0.6.6
└──▷ BREAKING ON UPGRADE
!The Explorer API now fails closed with HTTP 503 on all 11 routers when SEMANTICA_API_KEY is unset — previously all routes were reachable with no credential. Deployments that relied on anonymous access must set SEMANTICA_ALLOW_ANONYMOUS=true explicitly.
!Legacy .pkl files produced by VectorStore.save() are now refused on load; the format has changed to JSON and old pickle files must be regenerated.
Local UI to run and train LLMs and diffusion models. Supports GGUF, MLX, Qwen3.8, Kimi K3, MiniMax-H3, Gemma 4, FLUX and more.
Unsloth shipped a native cross-platform Desktop app with Cloudflare/LAN remote access, OpenAI-compatible local serving, and agent CLI integrations, alongside a wave of new local model support (Qwen3.8-27B/2.4T, Qwen3.8-Flash-Next, GLM-5.3-Flash, DeepSeek V4 Flash 0731, Kimi K3, Muse Glimmer 30B, MiniMax-H3) plus Deep Research, RAG, Auto Compaction, Projects, and numerous training/chat reliability fixes across twelve releases.
└──▷ WHAT SHIPPED · 33 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Remote & LAN access for local modelsIMPROVED95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Adds unsloth studio --secure to expose Studio via a free Cloudflare HTTPS link, unsloth studio -H 0.0.0.0 -p <port> to bind to a custom host/port, unsloth studio reset-password, the UNSLOTH_STUDIO_PASSWORD environment variable for headless starts, and --disable-tools to block server-side tool execution when exposed publicly; also adds LAN access via Settings > API keys > LAN access. Later replaced/extended by a dedicated Settings > Remote & LAN Access (Preview) section that can be toggled without restarting, shows connection addresses and QR codes, supports optional auto-start (disabled by default), requires changing the generated admin password, and supports keyless/password-less LAN API access.
Enable LAN access so teammates on the same network can reach your local model without Cloudflare.
📍Settings › Remote & LAN Access › Enable LAN access, then change the generated admin password and optionally enable auto-start.
Enable LAN access so teammates on the same network can reach your local model instance — no Cloudflare tunnel needed.
📍In the Unsloth Desktop or Studio UI, go to Settings › Remote Access and enable LAN access, then share the displayed connection address or QR code.
Agent integrations via `unsloth start`NEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds unsloth start claude --model <model>, unsloth start codex, unsloth start hermes, unsloth start openclaw, and unsloth start opencode subcommands to connect Claude Code, OpenAI Codex, and other agents to local models with a single command; later extended with OpenCode V2 support via unsloth start opencode and a --reasoning-effort flag documented on the Agents tab for controlling reasoning in Studio.
DeepSeek V4 Flash and Kimi K3 Dynamic GGUF supportNEW85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
Adds DeepSeek V4 Flash 0731 Dynamic GGUF support with quantization tiers UD-IQ1_S (83 GB), UD-IQ3_XXS (104 GB), UD-Q4_K_XL (155 GB), and UD-Q8_K_XL (162 GB); enables DSpark inference by default for DeepSeek V4 Flash, delivering 2x faster inference. Adds Kimi K3 Dynamic GGUF support for Moonshot AI's 2.8T-parameter MoE model (104B active parameters, native vision, 1M context window) with tiers UD-IQ1_S (595 GB), UD-Q4_K_XL (1.51 TB), and UD-Q8_K_XL (1.56 TB), with low/high/max reasoning effort levels for this thinking-only model; both models are also listed among the local models runnable in Unsloth Desktop alongside Muse Glimmer 30B, Qwen3.8, and Gemma 4.
Qwen3.8-Flash-Next and GLM-5.3-Flash local inferenceNEW80how completely this was documenteddepth35/40specificity30/30actionability15/3080 / 100
Supports Qwen3.8-Flash-Next (125B) locally on 75 GB RAM via 1-bit Unsloth Dynamic GGUF, with up to 262K context and switchable reasoning levels (None, Low, Medium, Extra High), plus 'Preserved Thinking' to keep reasoning consistent across longer conversations; supports GLM-5.3-Flash (320B, 18B active) locally on 102 GB combined RAM + VRAM via 1-bit GGUF, with up to 1M context and Low/High/Max reasoning modes.
— Precise sizes and context limits but no run commandv0.1.804-beta
05
Auto Compaction for long chatsNEW80how completely this was documenteddepth35/40specificity25/30actionability20/3080 / 100
New Auto Compaction (Experimental) feature lets long local chats continue past a model's context limit by rolling older turns out of active context, indexing evicted turns into a per-thread searchable archive via search_conversation, using the existing RAG pipeline (store, chunker, embedder, retrieval) without summarization.
Training pipeline reliability and diagnosticsIMPROVED80how completely this was documenteddepth35/40specificity30/30actionability15/3080 / 100
Training now checks whether a model requires a newer Transformers version and prompts before installing it, and warns when a model must use 16-bit instead of 4-bit. On Kaggle, large saves can use the bigger temporary drive when the working folder is too small. Bounds dataset_num_proc by available memory and treats a value of 1 as genuine single-process mode rather than no multiprocessing. Fetches sentence-transformers model subfolder weights directly instead of pruning them. Answers GGUF variant requests from the specific named cache snapshot and skips unreadable entries. Settles deferred compile-mode switches between training steps rather than mid-step. Auto-falls back to HTTP download if XET is stuck, improving reliability on Colab, low-memory, and high-memory/CPU systems. Revamped training page in Unsloth Studio, with the Train page now linked across to image training.
Model export to NVFP4, GGUF, and FP8IMPROVED75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
Adds export of trained models to NVFP4, GGUF, and FP8 formats after no-code training. GGUF exports now check available disk space before starting a long merge and show how much space is needed, and Unsloth now reports the real cause when a model save or GGUF export fails instead of a generic error.
Qwen3.8-27B and Qwen3.8-2.4T local supportNEW75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
Adds support for running and fine-tuning Qwen3.8-27B and Qwen3.8-2.4T locally, including Dynamic GGUF quantizations runnable in 17 GB RAM and NVFP4 quants.
Run Qwen3.8-27B locally via Claude Code agent, pointing it at the GGUF quantization that fits in ~17 GB RAM.
$ unsloth start claude --model unsloth/Qwen3.8-27B-GGUF:UD-Q4_K_XL
— Gives RAM requirement and a runnable start commandv0.1.800-beta
09
Extra Arguments box for llama-server flagsNEW75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
Model settings now expose an 'Extra Arguments' box for custom llama-server flags, validated against the installed build and saved per model for normal, startup, and API load modes; invalid or security-breaking flags are rejected with a clear message.
— Names the exact settings box and validation behaviorv0.1.800-beta
10
Multi-GPU and hardware backend supportIMPROVED70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Supports multi-GPU inference and training across NVIDIA, AMD, Intel, and Mac hardware, plus CPU-only operation; adds Intel XPU support for inference and hardware acceleration; adds improved support for AMD RDNA 3, RDNA 4, and Strix Halo systems with safer multi-GPU ROCm device matching; automatically detects multi-GPU setups and offloads model layers to system memory for DeepSeek V4 Flash and Kimi K3.
Projects workspace for chats, files, and sourcesNEW70how completely this was documenteddepth30/40specificity20/30actionability20/3070 / 100
Projects feature lets chats, files, and workspaces be organized together, with attached files shared across a project; chats remember composer settings, system prompts, and model sampling options. Adds drag-and-drop support for files (including .ods) onto project sources and knowledge bases, plus an attachment preview modal for all attachment types. A full chat or individual reply can be saved into a project's sources, preserving reasoning, tool calls, and citations.
Custom llama.cpp build supportNEW70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds support for custom llama.cpp builds with toggles for Cache RAM, Mmap, Mlock, Checkpoints, Speculative Decoding KV Cache, and Vision On/Off.
— Names each toggle but not their exact settings locationv0.1.803-beta
13
Desktop update managementIMPROVED70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Desktop update controls moved to Settings > General; adds Check for Updates and Update Now options to Settings, plus the app version shown in Settings > About; Desktop warns before quitting during an in-progress update and skips the installer fallback when the user cancels; Desktop draft publishing is enabled without a full rebuild.
MiniMax-H3 video generation with FP8 inferenceIMPROVED65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Adds MiniMax-H3 for local video generation. Adds Fast FP8 MiniMax-H3 inference, delivering approximately 10x faster throughput (approximately 3 minutes vs. 30); MiniMax-H3 now splits large model parts to fit smaller supported GPUs, and the model picker hides H3 options the current hardware cannot run.
Settings > Debugging panelNEW65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
Adds a Settings > Debugging panel showing main server and model-runner logs with live, 3-second, and manual refresh modes; passwords, tokens, and API keys are redacted in the viewer.
— Names exact panel location and refresh modesv0.1.800-beta
16
GPU+RAM offload plannerIMPROVED60how completely this was documenteddepth30/40specificity20/30actionability10/3060 / 100
Enables 5x faster inference for RAM offloading, with large GGUFs automatically split across GPU and system RAM via the offload planner, now on by default.
— Gives a concrete speedup number but no manual controlsv0.1.804-beta
17
Muse Glimmer 30B local supportNEW60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Adds support for running and fine-tuning Meta's Muse Glimmer 30B dense model locally on 20 GB RAM/VRAM (Mac and GPU) via Unsloth Dynamic quants, under the Apache 2.0 license; also listed among models runnable locally in Unsloth Desktop.
Speech and embedding model handlingIMPROVED60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Adds Qwen3-ASR dictation to Unsloth Studio, with cancellable model downloads and a download prompt before starting; adds stop and send buttons on the Studio chat dictation bar; adds custom STT (speech-to-text) connections in Studio; loads text-to-speech models on demand rather than at startup; supports searching and downloading embedding models directly from Hugging Face.
Studio and chat UX improvementsIMPROVED60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Studio image and video pickers now populate from a curated catalog rather than raw model listings; Studio detects stalled Deep Research output streams and surfaces the condition to the user; Studio now applies saved per-model settings on API loads, adds an API monitor, and reports active training status in the UI; serves gated diffusion base models from ungated Unsloth mirrors, removing the need for user tokens; Desktop supports dropping documents into a chat (non-GGUF files accepted); Chat now provides downloadable artifacts from generated responses; pinned models can be reordered by dragging them in the model list; Chat now shows live prompt and generation speeds during streaming.
MCP tool integration and file editingNEW55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Adds MCP (Model Context Protocol) tool integration for workflows that need external apps, data, or actions; adds an edit_file tool for partial file modifications in chat/agent workflows; images returned by MCP tools now appear inline in chat.
VRAM and memory usage visibility and tuningIMPROVED55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
Shows estimated memory usage before loading a model in the Load Model panel and displays VRAM usage directly from the downloaded models list; VRAM usage is now tunable from the UI. Inference is up to 10% faster with lower VRAM use and a tunable memory limit in supported configurations, and idle image and video models can optionally unload to free VRAM for Chat or Training.
YouTube transcript attachment in chatNEW55how completely this was documenteddepth20/40specificity15/30actionability20/3055 / 100
Paste a YouTube link in Chat to attach its transcript, including title, channel, duration, link, and caption language.
— Gives exact action (paste link) and fields capturedv0.1.800-beta
25
OpenAI-compatible local APIIMPROVED50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Exposes an OpenAI-compatible API for serving local models to agents and other clients, with optional OpenAI and Anthropic cloud provider connections; the Responses API now also supports structured output formatting.
RAG support for local contextIMPROVED50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Adds RAG support for bringing user-supplied files into local model context; RAG document indexing now uses the CPU by default, preventing large GPU memory blocks from remaining reserved.
Unsloth Desktop native app launchNEW45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Launches Unsloth Desktop, a native GUI app for Windows, macOS, and Linux, for no-code local running, training, and export of LLM, diffusion, TTS, and embedding models.
Tool calling for external cloud providersNEW45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Adds tool calling and web search support for external cloud providers (OpenAI, Anthropic) inside Unsloth Desktop, with tool calling and tool results now passed back to the model for multi-step tasks.
Deep Research modeIMPROVED45how completely this was documenteddepth25/40specificity10/30actionability10/3045 / 100
Adds Deep Research mode that autonomously plans and produces cited reports from unlimited private web search; Deep Research now keeps running instead of stopping when a provider applies rate limiting.
Independent prompt queues per parallel chatIMPROVED40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
Supports independent prompt queues across parallel chat sessions in Studio, so concurrent conversations no longer share a single queue and avoid cross-contamination.
Sampling seed for reproducible inferenceNEW35how completely this was documenteddepth10/40specificity10/30actionability15/3035 / 100
Adds a sampling seed setting in chat run settings for reproducible inference.
— Names the setting location but nothing furtherv0.1.804-beta
32
Chat settings and session continuityIMPROVED35how completely this was documenteddepth20/40specificity10/30actionability5/3035 / 100
Chats now persist composer settings, system prompts, and model sampling options per model; local chats resume after a disconnect instead of losing the in-progress reply; model settings are preserved when switching between chats; chat settings also persist with the conversation across remote sessions.
Image and video diffusion model supportIMPROVED30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Adds preliminary image diffusion support alongside image and video diffusion model inference at up to 2x faster speed on supported workflows; Hub now supports more image and video workflows.
Kiro shipped a dedicated full-screen view for running V3 specs, plus terminal, extension-compatibility and MCP protocol improvements.
└──▷ WHAT SHIPPED · 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Full-screen spec execution viewNEW85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
The new /spec run command opens a dedicated full-screen task execution view for V3 spec runs, with real-time progress tracking and the ability to select task scope before execution begins.
Run a spec in full-screen mode to monitor real-time task progress and select task scope before execution begins.
Daytona is an open-source development environment platform that enables developers to spin up standardized, reproducible coding environments instantly.
Daytona standardized error handling by propagating daemon error codes consistently across all its SDKs.
└──▷ WHAT SHIPPED · 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
thinner coverage below
01
Consistent daemon error codes across SDKsIMPROVED28how completely this was documenteddepth15/40specificity8/30actionability5/3028 / 100
Daemon error codes are now propagated consistently across all SDKs, enabling uniform error handling for developers building on Daytona.
Superset is an agentic IDE to orchestrate 100+ coding agents in parallel. Run any agent with your own subscription.
Superset desktop v1.25.1 ships a new superset scripts add CLI, workspace tags, remote port forwarding, a PDF viewer, and a broad localization push (14 new UI languages with persisted locale and auto-translation), alongside expanded usage analytics across agent CLIs and quota tracking.
└──▷ WHAT SHIPPED · 13 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
superset scripts add CLI and terminal scripts renameNEW70how completely this was documenteddepth20/40specificity20/30actionability30/3070 / 100
Adds a new superset scripts add subcommand to create terminal scripts from the CLI, and renames the former 'terminal presets' feature to 'terminal scripts'.
Add a new terminal script to your Superset desktop environment from the CLI.
$ superset scripts add
— Runnable command named, but rename's scope not detailed.desktop-v1.25.1
02
Localization: persisted locale, switcher, and auto-translationNEW70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds locale persistence via a Postgres user.locale field and a desktop Language setting (Settings > Language), a language switcher on marketing and docs pages, and automatic translation of new strings on PRs; ships 14 new UI languages.
Set your preferred display language so the UI persists your locale across sessions.
📍In the desktop app, go to Settings › Language and select your preferred locale (e.g. Japanese, French, Spanish).
— Names the DB field and UI path with concrete language count.desktop-v1.25.1
03
Host service version gate raisedBREAKING60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Raises MIN_HOST_SERVICE_VERSION so pre-1.22 host services hit the version gate instead of displaying a blank terminal pane.
— Names the config gate and gives clear before/after behaviour.desktop-v1.25.1
thinner coverage below
04
Usage analytics for agent CLIs and quota trackingNEW55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
Adds usage analytics for agent CLIs grok, cursor, opencode, copilot, pi, omp, and fx, and adds Grok and Antigravity quota tracking to the usage view.
— Names every CLI tracked but no way to invoke it directly.desktop-v1.25.1
05
Pages visibility, thumbnails, and comment routingIMPROVED55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Pages now default to org visibility with cached thumbnails, owner info, and a delete action in the grid; published pages now watch for comments and route them to the owning agent.
— Describes new default behaviour and routing mechanism concretely.desktop-v1.25.1
06
Workspace tags and tag folder organizationNEW52how completely this was documenteddepth22/40specificity20/30actionability10/3052 / 100
Adds workspace tags and tag-derived sidebar folders for organizing workspaces, plus host-side tag folder presentation and a hide list for tag folders to control which tag folders are shown.
— Names all constituent surfaces but no exact UI path.desktop-v1.25.1
07
Copy-on-select for v2 terminalsNEW48how completely this was documenteddepth18/40specificity15/30actionability15/3048 / 100
Adds a 'copy-on-select' setting for v2 terminals in the desktop app, enabled via Settings > Terminal, so selected text is automatically copied to the clipboard.
Enable copy-on-select in v2 terminals so selected text is automatically copied to the clipboard.
📍In the desktop app, go to Settings › Terminal and enable 'Copy on select'.
— UI path given but limited mechanism detail.desktop-v1.25.1
08
Claude model picker restrictionsNEW40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Adds pinned Claude model IDs in the workspace-create picker, and rejects unsupported models.
— Describes behaviour but no model IDs or picker location.desktop-v1.25.1
09
Usage folded into SettingsIMPROVED35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Folds Usage into Settings and aligns the Settings sidebar with the main sidebar.
— States the reorg but no exact navigation path.desktop-v1.25.1
10
PDF viewer in file paneNEW25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Adds a PDF viewer to the file pane.
— Bare one-line addition with no further detail.desktop-v1.25.1
11
Remote port forwarding for workspacesNEW25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Forwards remote workspace ports to the local machine.
— No mechanism, ports, or protocol detail given.desktop-v1.25.1
12
Trigger-only integrationsNEW25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Adds trigger-only integrations scoped to surfaces where their triggers apply.
— Generic description with no named integrations or surfaces.desktop-v1.25.1
13
Nerd Font icon rendering in terminalsNEW25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Adds Nerd Font icon rendering for any terminal font.
— Bare one-line addition with no configuration detail.desktop-v1.25.1
└──▷ BREAKING ON UPGRADE
!The MIN_HOST_SERVICE_VERSION is raised so pre-1.22 host services hit the version gate instead of displaying a blank terminal pane.
Lightweight coding agent that runs in your terminal
Codex CLI's latest alpha builds add actionable rate-limit banners to the TUI, make the update_plan planning tool opt-in via config, and loosen MCP server naming rules to support npm-scoped package names.
└──▷ WHAT SHIPPED · 4 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
`update_plan` tool now opt-in via configBREAKING85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
Adds tools.update_plan.enabled config key, which now defaults to false; set it to true to explicitly expose the update_plan tool. When disabled, bundled planning guidance is removed from prompts, so workflows relying on update_plan being available by default will stop receiving it until the key is set explicitly.
Re-enable the update_plan tool when your workflow depends on Codex explicitly tracking and updating a plan during long-running tasks.
Expanded character set for MCP server namesIMPROVED85how completely this was documenteddepth25/40specificity30/30actionability30/3085 / 100
MCP server names may now contain :, @, /, and . in addition to letters, numbers, -, and _, enabling package-style names like npm:@modelcontextprotocol/server-sequential.thinking across mcp add, get, list, and remove commands, runtime tool namespaces, and OAuth credential lookup.
Register an npm-scoped MCP server using its full package-style name so the tool namespace and OAuth credentials stay properly isolated.
Actionable rate-limit banners in the TUINEW65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
The TUI now renders actionable rate-limit banners above the composer, with actions covering usage, credits, resets, owner notifications, plan management, and automatic fallback-model switching when instructed by the banner.
Reserved history-ingest metadata flag on Responses turnsIMPROVED65how completely this was documenteddepth30/40specificity25/30actionability10/3065 / 100
Sets history_ingest_requested to true in Responses turn metadata when the history-notes token-budget extension is enabled, and reserves the key so caller-provided metadata cannot override it.
— Names the exact metadata field but is an internal, non-user-actionable changerust-v0.152.0-alpha.6
└──▷ BREAKING ON UPGRADE
!The update_plan tool now defaults to disabled (tools.update_plan.enabled: false); any workflow relying on update_plan being available by default will stop receiving it until the key is explicitly set to true.
Cotool is an AI-powered security tool that analyzes code for vulnerabilities and provides automated remediation recommendations for developers.
Cotool v0.66.0 adds four new investigation integrations (Cloudflare, Auth0, 1Password, Tailscale) and strengthens alert triage with evidence attachment, prior-alert context, and escalation, alongside improvements to Slack notifications, the Detections overview, alert investigation, Linear/Notion integrations, and threat model generation.
└──▷ WHAT SHIPPED · 7 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
New investigation integrations: Cloudflare, Auth0, 1Password, TailscaleNEW65how completely this was documenteddepth20/40specificity30/30actionability15/3065 / 100
Adds four new integrations for investigation and alert triage: Cloudflare (HTTP traffic, firewall events, Zero Trust Gateway activity, DNS, zones, and devices), Auth0 (identity configurations, users, audit events, and sign-ins), 1Password (sensitive item activity and audit events), and Tailscale (devices, users, and configuration changes across tailnets).
— Names four integrations and data types but no setup stepsv0.66.0
thinner coverage below
02
Automated evidence and context for alert triageIMPROVED50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Alert triage now attaches evidence to every detection hit, gives response agents context from prior alerts, handles duplicate alerts, and escalates uncertain cases for human review.
— Describes mechanism but no config or UI path givenv0.66.0
03
Slack alert notifications with inline controlsIMPROVED45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Slack alert notifications now include concise evidence summaries, in-message status controls, and threaded follow-up with the assigned response agent.
— Names Slack feature specifics but no config detailv0.66.0
04
Detections overview UI improvementsIMPROVED45how completely this was documenteddepth15/40specificity15/30actionability15/3045 / 100
The Detections overview gains infinite scrolling, compact filters, bulk disable, and consistent true-positive metrics.
— Lists UI changes but no exact navigation pathv0.66.0
05
Alert investigation clarity and feedbackIMPROVED45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Alert investigation now shows clearer source attribution, more readable structured payloads, and lets users optionally leave feedback when closing alerts as benign or false positives.
— Describes changes without exact UI or API detailv0.66.0
06
Threat model generation improvementsIMPROVED45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Threat models now support safer regeneration, persistent progress, longer-running generation, and automatic availability to the default response agent.
— Names improvements but no config or command givenv0.66.0
07
Linear and Notion integration enhancementsIMPROVED30how completely this was documenteddepth10/40specificity15/30actionability5/3030 / 100
Linear integration gains duplicate issue handling, and Notion integration gains paginated database queries.
— Thin one-line mentions with no mechanism detailv0.66.0
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
Graphify v0.9.53 adds Robot Framework parsing support and fixes the code-only force rescan to fully refresh import/alias resolution.
└──▷ WHAT SHIPPED · 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Robot Framework extraction via `[robot]` extraNEW83how completely this was documenteddepth30/40specificity28/30actionability25/3083 / 100
Adds extraction of .robot and .resource files through the optional [robot] extra, capturing suites, test cases, user keywords, keyword-call edges, and resource/library imports, with case/space/underscore-insensitive keyword resolution. Install with uv tool install 'graphifyy[robot]'.
Install Graphify with Robot Framework support to start mapping .robot and .resource files into your knowledge graph.
$ uv tool install 'graphifyy[robot]'
— Names extra, edge types, and install command; no runnable extract example shown.v0.9.53
02
`extract --force --code-only` now fully rescans codeIMPROVED70how completely this was documenteddepth25/40specificity20/30actionability25/3070 / 100
The graphify extract --force --code-only flag now fully rescans all code files instead of skipping unchanged files and keeping stale import/alias resolution, while preserving the existing document/semantic tier.
Force a full code rescan to pick up changed imports or aliases without discarding existing document/semantic data.
$ graphify extract --force--code-only
— Exact flag and before/after behavior given with a runnable command.product docs
OpenClaw v2026.8.1 adds team-oriented access control — operator roles, per-operation approval grants, a shared SQLite-backed credential store, private credential requests, and an optional 1Password broker — alongside new memory, chat, and cloud-session features, while removing the bundled OpenProse plugin and forcing a migration of all codex model refs to openai/*.
└──▷ WHAT SHIPPED · 35 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
External supervisor mode for Gateway lifecycleNEW75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
New OPENCLAW_SUPERVISOR_MODE=external environment variable lets an external supervisor own Gateway restarts, service lifecycle, and updates without the native service competing for those changes.
— Names exact env var and behavior changev2026.8.1
02
Telemetry payload inspection commandNEW75how completely this was documenteddepth20/40specificity25/30actionability30/3075 / 100
New openclaw telemetry show command inspects the outgoing usage-statistics payload before deciding whether to opt in; feature statistics are off by default.
Inspect the exact payload OpenClaw would send with its daily version check before deciding whether to enable usage statistics.
OpenProse plugin removedBREAKING75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
The bundled OpenProse plugin and /prose command are removed; run openclaw doctor --fix to clean stale configuration and follow the upstream Agent Skill migration, keeping existing .prose source files.
— Exact command names and migration path givenv2026.8.1
05
Codex model refs migrated to openai namespaceBREAKING75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
All shipped codex/* and openai-codex/* model refs, provider config, stored sessions, and automation routes must be migrated to openai/*; run openclaw doctor --fix to perform the migration and flag conflicts for operator repair.
— Exact ref patterns and migration command namedv2026.8.1
06
Named agent onboarding and legacy migrationNEW70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
New --agent-name flag during interactive onboarding names the first agent and migrates legacy main-session history to its clear owner; onboarding now sets up named agents and reuses main as an ordinary agent ID after required doctor repairs.
Shared team credential storeNEW70how completely this was documenteddepth30/40specificity20/30actionability20/3070 / 100
New shared credential store manages team-scoped secrets and environment entries in SQLite, accessible through the CLI and Settings, with write-only secret values, protected egress bound to declared hosts, and a distinction between readable environment values and secrets.
— Names storage, access points, and egress controlv2026.8.1
08
Per-agent model allowlistsNEW65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
New modelPolicy.allow configuration key defines explicit per-agent model allowlists and provider wildcards, kept separate from aliases and per-model settings.
Plugin uninstall path cleanupIMPROVED65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Plugin uninstall now cleans up plugins.load.paths, removing exact recorded install paths for marketplace, npm, and other managed installs while preserving parent, child, prefix, and unrelated paths.
ClickClack integrationNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
New ClickClack integration supports one-use expiring setup codes, immediate account verification, and native command menus published at Gateway startup when the token has commands:write.
Plugin install provenance warningsNEW65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
Plugin installs from arbitrary executable sources via CLI or chat now require --force; trusted ClawHub, bundled, official-catalog, and tracked-update sources skip the warning.
Conversation-bound automations and /loop commandNEW65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
New conversation-bound automations and an owner-only /loop command support fixed-interval or self-paced checks, defaulting new agent-turn automations to their originating conversation.
— Names exact command and default scopingv2026.8.1
13
1Password credential brokerNEW60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Optional 1Password broker resolves SecretRefs or reads selected 1Password fields using service-account auth, with per-secret approval and value-free audit.
Recoverable database backupsNEW60how completely this was documenteddepth30/40specificity15/30actionability15/3060 / 100
New recoverable database backups schedule recorded backups, keep versioned snapshots in an operator-owned Git repository, and can restore a verified full archive into a fresh staging directory.
— Describes full backup and restore mechanismv2026.8.1
15
New official provider packages and pluginsNEW60how completely this was documenteddepth15/40specificity30/30actionability15/3060 / 100
New official provider packages for BytePlus, ComfyUI, Mistral, NovitaAI, OpenCode, Synthetic, Volcengine, Vydra, and Xiaomi are installable through onboarding; separately installable official plugins add Cohere and Meta providers, DuckDuckGo search, Voyage embeddings, and iMessage messaging.
Private credential requestsNEW55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
Agents can request credentials through a masked prompt without exposing values in chat or model context; an opt-in proxy limits protected-secret substitution to approved destinations.
— Explains mechanism, no exact config namedv2026.8.1
17
Per-operation automation approval grantsNEW55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
New per-operation automation approval grants let a permission be granted for an exact operation once, inspected or revoked later, and require fresh approval when the job or operation changes.
— Describes lifecycle but no named surfacev2026.8.1
18
Team operator rolesNEW55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
New team operator roles assign verified users named roles that limit which agents, other people's sessions, and operator scopes they can access, with optional sandboxed execution for newly created sessions.
— Explains scope limits and sandboxing optionv2026.8.1
19
Session permission modes and pickerNEW55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
New session permission modes let users choose an explicit mode and keep restricted filesystem access anchored to its recorded workspace or worktree; newly created worktrees inherit the configured policy unless a mode is selected. The Control UI's session permissions picker now shows a label indicating the configured default.
— Explains scoping and UI indicator togetherv2026.8.1
20
Memory import from other AI toolsNEW55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
New memory import brings in detected Claude Code, Codex, and Hermes memory during CLI, macOS, and Linux onboarding.
— Names source tools and onboarding platformsv2026.8.1
21
Pinnable widgets in chatNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
New widget support in chat lets users pin widgets to session dashboards, grant them specific actions or network origins, and export rendered views as images.
— Describes capabilities without exact configv2026.8.1
22
Incognito conversation threadsNEW50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
New incognito threads keep Control UI conversation transcripts and compaction state in Gateway memory only until restart, with memory flush off.
— Explains memory behavior but no UI path givenv2026.8.1
23
Personal conversation recallNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
New personal conversation recall retrieves bounded same-agent private conversation context by default on personal installs when Active Memory is enabled; explicit controls can disable recall.
Remembered model selection scopesNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
New remembered model selection lets users choose explicit scopes for whether a model change affects the current session, its agent, or the shared default.
Automatic self-learning skillsNEW45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
New automatic self-learning captures reusable lessons and applies scanner-approved new or Workshop-owned skills by default, while leaving user-authored skill changes pending.
— Explains approval distinction but no surface namedv2026.8.1
28
Structured agent question answeringNEW45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
New structured agent question answering lets agents ask via web and native cards, messaging buttons, or plain text, with free-text alternatives and an explicit Skip path.
Richer audio and video supportIMPROVED45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Richer audio and video support adds native playback controls, media persistence across uploads and reloads, and video uploads on Apple and Android clients.
PWA approval notifications and preferencesNEW15how completely this was documenteddepth5/40specificity5/30actionability5/3015 / 100
Adds PWA approval notifications and preferences.
— Bare one-line commit note, no mechanismv2026.8.1
└──▷ BREAKING ON UPGRADE
!The bundled OpenProse plugin and /prose command are removed; run openclaw doctor --fix to clean stale configuration and follow the upstream Agent Skill migration, keeping existing .prose source files.
!All shipped codex/* and openai-codex/* model refs, provider config, stored sessions, and automation routes must be migrated to openai/*; run openclaw doctor --fix to perform the migration and flag conflicts for operator repair.
Local-first AI agents with governed, approval-gated memory. Any model provider; MCP tools and web search built in.
Exxperts v0.11.0 ships self-contained desktop and server archives with a vendored Node runtime, so target machines no longer need Node, npm, or Git, plus checksum verification and stable download links for releases.
└──▷ WHAT SHIPPED · 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Checksum verification for release archivesNEW80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Adds SHA256SUMS.txt with per-archive checksums computed in CI from the tagged commit, verifiable via shasum -a 256 --ignore-missing -c SHA256SUMS.txt.
Verify the integrity of a downloaded archive before deploying to a machine without Node or Git.
$ shasum -a 256 --ignore-missing-c SHA256SUMS.txt
— Exact file name and runnable verification command providedv0.11.0
02
Self-contained desktop and server archivesNEW78how completely this was documenteddepth30/40specificity28/30actionability20/3078 / 100
Adds signed, self-contained desktop app builds (window + tray around a local server) for Windows x64 (exxperts-desktop-0.11.0-win-x64.zip, exxperts-setup-0.11.0.exe) and macOS Apple Silicon (exxperts-desktop-0.11.0-mac-arm64.dmg), with the macOS build Apple-notarized and Windows binaries publisher-signed by Exxeta AG to eliminate unknown-publisher prompts on first launch. Also adds self-contained exxperts server archives for Windows x64 (exxperts-0.11.0-win-x64.zip), macOS Apple Silicon (exxperts-0.11.0-darwin-arm64.tar.gz), and Linux x64 (exxperts-0.11.0-linux-x64.tar.gz) with a vendored Node runtime, requiring no Node, npm, or Git installation on target machines.
— Names every archive and platform but no runtime mechanism detailv0.11.0
thinner coverage below
03
Versionless download aliasesNEW55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Adds versionless download aliases such as exxperts-desktop-mac-arm64.dmg and exxperts-setup-win-x64.exe so releases/latest/download links always resolve to the newest release.
— States mechanism and named alias files, no runnable examplev0.11.0
Agno shipped a major knowledge-ingestion overhaul — SitemapReader, per-page website and folder ingestion, new fetch seams, and AgentOS knowledge content API routes — alongside a reworked KnowledgeManagementTools toolkit whose flags and import path changed in breaking ways, plus AtomicMail performance work that cut proof-of-work and warm-call latency by an order of magnitude.
└──▷ WHAT SHIPPED · 9 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
KnowledgeManagementTools write toolkit for knowledge basesBREAKING95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Adds KnowledgeManagementTools with operations ingest_url, ingest_text, ingest_path, list_content, ingest_status, and remove_content (confirmation required by default), supporting scope="shared"|"user", JSON envelopes, and sync/async variants. In the following release the constructor flags were renamed to match the tools they register — ingest_url, ingest_path, ingest_text, remove_content — giving per-tool opt-in control, with ingest_path now defaulting to off because under scope='shared' it exposes loaded content to every agent on the knowledge base; the old enable_ingest/enable_remove flags are removed and silently ignored. The toolkit also moved from agno.tools.knowledge_management to agno.tools.knowledge, alongside the read-only KnowledgeTools, mirroring the agno.tools.mcp and agno.tools.finance layout.
Enable only safe ingestion tools and explicitly opt in to path ingestion for an agent that needs to load local files into a shared knowledge base.
python
from agno.tools.knowledge import KnowledgeManagementTools
km_tools = KnowledgeManagementTools(
knowledge_base=my_kb,
ingest_url=True,
ingest_text=True,
ingest_path=True, # opt-in: exposes any path the server process can read
remove_content=False,
)
Attach knowledge management tools to an agent so it can ingest, list, and remove knowledge base content at runtime.
python
from agno.agent import Agent
from agno.tools.knowledge import KnowledgeManagementTools
agent = Agent(
tools=[KnowledgeManagementTools(scope="shared")],
)
agent.print_response("Ingest https://docs.agno.com and list all loaded pages.", stream=True)
— Names every flag, module path, default change and gives runnable code.v3.0.4v3.0.3
02
Knowledge content listing and refresh API routesNEW85how completely this was documenteddepth25/40specificity30/30actionability30/3085 / 100
AgentOS gains GET /knowledge/content?parent_id= to list a site's or folder's content rows with correct totals, and POST /knowledge/content/{id}/refresh to re-run ingest for a URL- or path-sourced row in the background.
Trigger a background re-ingest of a specific knowledge content row via the AgentOS API.
$ curl -X POST https://<agentos-host>/knowledge/content/<id>/refresh
List all child rows belonging to a previously ingested site or folder to inspect per-page status.
— Exact endpoints with method, path and working curl commands.v3.0.3
03
HttpxPageFetcher and ParallelPageFetcher for URL ingestionNEW80how completely this was documenteddepth35/40specificity30/30actionability15/3080 / 100
Adds HttpxPageFetcher and ParallelPageFetcher as fetch seams below URL readers; ParallelPageFetcher resolves Parallel's keyed SDK, then its keyless MCP endpoint, then plain httpx, honoring retry-after with exponential backoff and recording per-page extractor and attempts provenance. HttpxPageFetcher also routes application/pdf responses and %PDF- bytes served under a wrong content type through PDFReader; a missing pypdf surfaces as a per-page error naming agno[pdf].
— Detailed mechanism and fallback order but no direct usage example.v3.0.3
04
Parallel proof-of-work nonce search for AtomicMailIMPROVED78how completely this was documenteddepth30/40specificity28/30actionability20/3078 / 100
Adds pow_workers argument to AtomicMail (default min(4, cpu_count())) to parallelise scrypt nonce search across a bounded thread pool, cutting mean solve time from 25.9 s to 10.4 s at difficulty 10.
— Named argument and default with concrete before/after numbers.v3.0.4
05
SitemapReader for sitemap-based page discoveryNEW73how completely this was documenteddepth30/40specificity28/30actionability15/3073 / 100
Adds SitemapReader that discovers pages via the sitemap protocol (robots.txt Sitemap: lines, /sitemap.xml, /sitemap_index.xml, gzip and nested indexes) with canonical dedup and a max_pages cap; it is auto-selected for bare sitemap*.xml(.gz) URLs and also available in the UI reader dropdown.
— Names formats and cap; UI path given but no code example.v3.0.3
06
Cached auth context for AtomicMail warm callsIMPROVED70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Caches AtomicMail auth context (capability JWT, API URL, account and inbox IDs) on the instance until token expiry, reducing warm tool call latency from ~35 s to 0.4–3 s in both sync and async paths.
— Clear mechanism and dramatic latency numbers, no code sample.v3.0.4
07
Per-page website ingestion with digest-based re-ingestNEW69how completely this was documenteddepth32/40specificity22/30actionability15/3069 / 100
Per-page website ingestion stores one content row per page with content_id matching its vectors, supporting individual list, refresh, and delete; digest-driven re-ingest skips unchanged pages, replaces only changed pages' vectors, retries failed pages, and prunes removed sitemap entries.
— Clear mechanism described but no direct command shown.v3.0.3
08
Folder ingestion with byte-digest refreshNEW69how completely this was documenteddepth32/40specificity22/30actionability15/3069 / 100
Folder ingestion stores a folder row with one child row per file (nested folders flattened), with byte-digest refresh so unchanged files skip read and embed, per-file failure isolation, pruning of deleted files, and cascade delete.
— Concrete behaviour described, no runnable example attached.v3.0.3
09
Lazy-loading for file and knowledge tool packagesIMPROVED60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
Makes agno.tools.file and agno.tools.knowledge lazy-loading packages so importing FileTools no longer pulls in reportlab and python-docx — saves 44.8 ms on every FilesystemContextProvider import.
— Named packages and exact savings, but no action for readers to take.v3.0.4
└──▷ BREAKING ON UPGRADE
!The enable_ingest and enable_remove flags on KnowledgeManagementTools are removed and silently ignored if passed; replace them with the new per-tool flags ingest_url, ingest_path, ingest_text, and remove_content.
!KnowledgeManagementTools moved from agno.tools.knowledge_management to agno.tools.knowledge; any from agno.tools.knowledge_management import KnowledgeManagementTools import will break.
!ingest_path on KnowledgeManagementTools now defaults to off; existing code that relied on it being enabled by default must now pass ingest_path=True explicitly.
vMLX 1.6.48 focused on MTP (multi-token prediction) verification and caching, alongside smaller fixes to gateway replay attestation and Hugging Face download progress display.
└──▷ WHAT SHIPPED · 3 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
MTP verification and caching improvementsIMPROVED60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
Adds vectorized GLM KDA MTP verification for GLM-family models, adds typed prompt SSD cache support to the MTP benchmark, and makes native MTP restart cache proofs configurable via commit fc88a3ea.
— Names commit and model family but no runnable flag or commandv1.6.48
thinner coverage below
02
Gateway replay attestation from request IDsNEW30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Attests fast gateway replays from durable request IDs, tying replay verification to persisted request identifiers.
— Only prose description, no named endpoint or config surfacev1.6.48
03
Hugging Face download progress refresh fixIMPROVED25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Keeps Hugging Face download progress refresh-compatible so progress display continues to update correctly during downloads.
— Bare fix description with no mechanism or config detailv1.6.48
Native LLM inference server for Apple Silicon. OpenAI + Anthropic API compatible.
mlx-serve v26.8.11 adds native support for Qwen 3.8 Flash Next and gpt-oss, speculative decoding, multimodal video/image understanding, sparse attention kernels for long prompts, and concurrent batch inference.
└──▷ WHAT SHIPPED · 7 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Native support for Qwen 3.8 Flash Next (125B)NEW85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
Adds native support for Qwen 3.8 Flash Next (125B), delivering ~60 tok/s on M4 Max and ~78 tok/s with speculative decoding, using ~70 GB RAM with the 4-bit pack ddalcu/Qwen3.8-Flash-Next-MLX-Serve-4bit.
— Concrete throughput/RAM numbers and model package name givenv26.8.11
02
Speculative decoding via --mtp flag on Flash NextNEW85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
Adds a --mtp flag (and a MoE toggle in Settings) to opt into speculative decoding on Flash Next, yielding +41% throughput on code generation; speculative decoding is now also applied to image questions.
Enable speculative decoding on Flash Next to accelerate code generation by ~41% on an M4 Max.
Enable the MoE/speculative decoding toggle for Flash Next through the UI when running without CLI access.
📍In the mlx-serve Settings panel, locate the MoE toggle and enable it to activate speculative decoding for Flash Next.
— Exact flag and runnable command plus UI toggle pathv26.8.11
thinner coverage below
03
Concurrent request batching on Flash NextNEW50how completely this was documenteddepth25/40specificity20/30actionability5/3050 / 100
Adds concurrent request batching on Flash Next: 2 parallel streams yield 1.3x total throughput, 4 streams yield 1.8x, with no regression on single-stream latency.
— Specific throughput multipliers but no config/flag namedv26.8.11
04
Native support for gpt-oss 20B and 120BNEW45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
Adds native support for gpt-oss 20B and 120B (OpenAI MoE, harmony format).
— Names models and format but no usage detailv26.8.11
05
Sparse attention kernels beyond 2k tokensNEW45how completely this was documenteddepth25/40specificity15/30actionability5/3045 / 100
Adds sparse attention past 2k tokens via custom kernels, keeping 8k-token prompt throughput competitive even under speculative decoding.
— Mechanism and token threshold given, no usage commandv26.8.11
06
Image and video understanding with cached visual contextNEW35how completely this was documenteddepth20/40specificity10/30actionability5/3035 / 100
Adds image and video understanding with follow-up questions on the same image answered instantly by reusing the cached visual context.
— Describes behaviour but no API or config surface namedv26.8.11
07
MLX 0.32.2 upgradeIMPROVED30how completely this was documenteddepth15/40specificity15/30actionability0/3030 / 100
Updates to MLX 0.32.2, delivering up to +3% speed improvement on MoE models at long context.
— Version bump with a stated improvement, no action neededv26.8.11
LangSmith is a platform for debugging, testing, and monitoring LLM applications built with LangChain.
LangSmith shipped a new public API endpoint for experiment comparison, switched bulk export compression to zstandard by default, and surfaced OpenTelemetry resource attributes as trace metadata, alongside configurable monthly trace limits, dataset-split editing in experiment comparison, and a long tail of reliability and UX fixes across threads, runs, and ingestion.
└──▷ WHAT SHIPPED · 15 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Public API endpoint for experiment comparisonBREAKING80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
Adds POST /v2/datasets/{dataset_id}/experiment-runs as the supported public API for paginated experiment comparison. Legacy dataset comparison helpers are removed from the public OpenAPI spec and generated SDKs; existing HTTP routes continue to work only for LangSmith UI clients.
OpenTelemetry resource attributes as trace metadataNEW80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
OpenTelemetry resource attributes set via OTEL_RESOURCE_ATTRIBUTES now appear on traces as metadata namespaced under otel.resource.*, enabling attachment of fields like user IDs without changing span emission code.
Attach user IDs and environment metadata to every trace without changing span emission code, using standard OpenTelemetry resource attributes.
$ export OTEL_RESOURCE_ATTRIBUTES="user.id=u_12345,deployment.environment=production"
# Traces will appear in LangSmith with metadata keys otel.resource.user.id and otel.resource.deployment.environment
— Named env var and metadata namespace with runnable examplesnapshot-20260831
03
Thread evaluator config preview refinementsIMPROVED80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
The thread evaluator config preview now shows only the thread message formats the evaluator actually maps, and displays a locked 'Trace count ≥ 2' filter for managed thread evaluators. Evaluators can be tested against a real conversation before saving via the validate endpoint.
Test a multi-turn thread evaluator against a real conversation before saving it, to confirm it grades correctly on live thread data.
— Names endpoint and filter with a runnable validation examplesnapshot-20260831
04
Split assignment visibility and editing in experiment comparisonNEW65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
A reorderable 'Splits (latest)' column in the experiment comparison view shows each example's current dataset split assignments as chips reflecting live membership. Each split chip is interactive, with an 'Edit splits' action that opens the single-example split picker inline.
— Names UI elements but only a navigation path, no APIsnapshot-20260831
thinner coverage below
05
Configurable monthly trace limits per project and userNEW50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Enforces user-defined monthly trace limits scoped to individual projects and users; new traces exceeding a configured limit are rejected while patches and feedback for accepted traces continue to flow.
— Explains behaviour but no config key or UI path namedsnapshot-20260831
06
OpenTelemetry span ordering fixIMPROVED45how completely this was documenteddepth25/40specificity15/30actionability5/3045 / 100
Native OpenTelemetry child spans are no longer dropped when they arrive before an SDK-attributed parent span; they are buffered and correctly nested regardless of arrival order.
Oversized field placeholders in multipart ingestionIMPROVED45how completely this was documenteddepth25/40specificity15/30actionability5/3045 / 100
LangSmith now preserves traces in multipart ingestion batches when one run has oversized inputs or outputs, replacing oversized fields with a placeholder instead of rejecting the entire batch.
— Explains behaviour change but no size threshold givensnapshot-20260831
08
Project UUID support in MCP toolsIMPROVED40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
LangSmith MCP tools that fetch runs or thread history now accept project UUIDs in addition to project names.
Clearer error for oversized bulk exportsIMPROVED32how completely this was documenteddepth15/40specificity12/30actionability5/3032 / 100
Bulk export of a dataset comparison view now returns a 'file is too large to export' error instead of a generic server error when the export exceeds internal size limits.
— Describes the message but no limit value or triggersnapshot-20260831
13
Timeout banner for runs table queriesIMPROVED30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
When a runs query times out, the runs table now shows a timeout banner instead of a silent failure.
!Legacy dataset comparison helpers are removed from the public OpenAPI spec and generated SDKs; existing HTTP routes continue to work only for LangSmith UI clients.
!Bulk export compression now defaults to zstandard (zstd) on all deployments except self-hosted environments, which retain gzip via the FF_BULK_EXPORT_DEFAULT_COMPRESSION environment variable.
See what your coding agents did and what it cost. Breaks each task down into work steps — tools used, files changed, tests run, time and tokens spent.
agentacct v0.10.4 broadens its secret-redaction coverage to more AI provider tokens and improves how agent tool names are categorized in the dashboard.
└──▷ WHAT SHIPPED · 2 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Secret redaction for xAI, Groq, Google OAuth tokensIMPROVED61how completely this was documenteddepth25/40specificity28/30actionability8/3061 / 100
Value redaction now covers xAI keys (xai-), Groq keys (gsk_), and Google OAuth 2.0 access tokens (ya29.). Anthropic keys (sk-ant-) are now reported under their own named class instead of being lumped into a generic category.
— Names exact token prefixes but redaction is automatic, not user-drivenv0.10.4
thinner coverage below
02
More agent tool names mapped out of 'other'IMPROVED17how completely this was documenteddepth10/40specificity5/30actionability2/3017 / 100
agentacct now maps more agent tool names out of the 'other' bucket, reducing miscategorized tool usage in task breakdowns.
— Only mentioned in summary, no specifics on which toolsv0.10.4
LanceDB's v0.38.0 release adds computed columns, materialized views, GPU-backed remote Functions, and async table operations across the Python and Node.js SDKs, alongside a set of breaking changes, while parallel docs updates cover sequence-packing for LLM training, list-element FTS granularity, and direct Azure credential support.
└──▷ WHAT SHIPPED · 16 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Computed columns via SQL expressionsNEW80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
Tables (local and remote) can declare computed columns using SQL expressions, with columns able to read earlier declarations within the same batch for multi-step derivation. refresh_column_async returns a job handle for tracking refresh progress, and refresh operations now return typed refresh job results.
Kick off an async computed-column refresh and hold a job handle to poll or await the result.
python
job = await table.refresh_column_async("summary_embedding")
result = await job.wait()
— Named API with runnable async job-handle examplev0.38.0
02
Paginated table listing in Node.js SDKBREAKING78how completely this was documenteddepth25/40specificity28/30actionability25/3078 / 100
Adds listTables to the Node.js SDK, deprecating tableNames, for paginated table listing driven by the store's own cursor; existing code that constructed or passed page tokens for table listings must be updated.
List tables with the new Node.js listTables API instead of the deprecated tableNames.
javascript
for await (const name of db.listTables()) {
console.log(name);
}
— Named API, deprecation, and runnable listing examplev0.38.0
03
Remote Functions platform: GPU, conda, wire contracts, and column bindingsNEW73how completely this was documenteddepth28/40specificity30/30actionability15/3073 / 100
Remote Functions gain a gpu flag requiring a GPU for every execution (baked into the immutable Function version), conda_channels and channels options for pinning Conda packages and channel priority, first-class function wire contracts, scalar function authoring, and a catalog client for managing remote functions. Functions can be bound to a group of columns or to specific columns by version, and support large_utf8 return signatures and nested Arrow types in their definitions.
— Names many flags and surfaces but no usage examplev0.38.0
04
StreamingDataLoader for checkpointed resumptionNEW65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
StreamingDataLoader, a PyTorch DataLoader subclass, carries consumer-committed StreamingDataset checkpoints alongside every internal batch, enabling safe mid-epoch resumption with multiple workers.
Enable sequence-packing for LLM pre-training so the streaming dataset joins consecutive token lists into fixed-length blocks with document-index tensors for masking.
python
from lancedb.streaming import StreamingDataset, StreamingDataLoader
dataset = StreamingDataset(
table,
num_splits=8,
pack_sequences=2048, # block length in tokens
eos_id=2,
pad_id=1,
blocks_per_epoch="auto",
)
loader = StreamingDataLoader(dataset, batch_size=4, num_workers=4)
for batch in loader:
# batch contains 'input_ids' and 'doc_ids' LongTensors
train_step(batch)
checkpoint = dataset.state_dict() # consumer-committed checkpoint
— Names class and checkpoint mechanism; shares code exampleproduct docs
05
Field metadata convention keys for columnsNEW65how completely this was documenteddepth22/40specificity28/30actionability15/3065 / 100
Adds field metadata convention keys lancedb:description, lancedb:tag:<name>, lancedb:logical-column, and lancedb:status (values: production, candidate, deprecated, archived) for annotating table columns via the metadata API.
— Names all keys and values but no usage exampleproduct docs
06
Materialized views on local tablesNEW62how completely this was documenteddepth28/40specificity22/30actionability12/3062 / 100
Adds materialized view declarations on local tables plus a refresh API to update them, with Python and Node.js bindings included. Materialized view refresh is bound to the view incarnation so stale refreshes against a replaced view are rejected.
— Explains mechanism (incarnation binding) but no examplev0.38.0
thinner coverage below
07
Branch cherry_pick renameBREAKING55how completely this was documenteddepth15/40specificity20/30actionability20/3055 / 100
The branch merge operation is renamed to cherry_pick; any code calling merge on a branch must be updated to cherry_pick.
— Exact rename named, clear migration step, no examplev0.38.0
08
StreamingDataset fault tolerance, backpressure, and remote-table supportIMPROVED50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Adds on_transform_error to control fault-tolerance during data transforms, adds backpressure to the post-transform queue to prevent unbounded memory growth, supports remote tables in the data loader, and pins the base table version for data loader reads to ensure consistent snapshots.
— Named param and behaviors but no example givenv0.38.0
09
Blob data support: refresh, UDF signatures, and URI writesNEW48how completely this was documenteddepth18/40specificity20/30actionability10/3048 / 100
Computed-column refresh now extends to blob-typed columns, functions support Blob v2 UDF signatures for operating on blob data, and blob data can be written via URI reference (blob URI write acceptance).
— Thin one-line descriptions of three blob capabilitiesv0.38.0
10
Manifest-authoritative table existenceBREAKING47how completely this was documenteddepth22/40specificity15/30actionability10/3047 / 100
Table existence is now manifest-authoritative: tables that lack a manifest entry are no longer considered to exist, even if other store artifacts are present.
— Explains semantic change but no migration steps givenv0.38.0
11
Python expressions in update filtersIMPROVED45how completely this was documenteddepth15/40specificity15/30actionability15/3045 / 100
Update filters in Python now accept Python expressions, not just strings.
— Clear behavior change but no example or code shownv0.38.0
12
LSM checkpoint/stats surface across SDKsIMPROVED45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
Exposes LSM checkpoint and stats on the synchronous Python RemoteTable, and brings the MemWAL LSM surface to parity across all SDKs.
— Names surfaces but gives no mechanism or examplev0.38.0
13
Node.js embedding config keying changeBREAKING45how completely this was documenteddepth18/40specificity15/30actionability12/3045 / 100
The Node.js SDK now keys parsed embedding configs by vector column name; projects relying on the previous keying scheme will need to update their embedding config references.
— Notes new key basis but no config example shownv0.38.0
14
Asynchronous drop-table APINEW42how completely this was documenteddepth15/40specificity15/30actionability12/3042 / 100
Adds an asynchronous drop-table API so table deletion no longer blocks the caller.
— Bare description of API, no name or example givenv0.38.0
15
Pydantic v2 requirement in Python SDKBREAKING42how completely this was documenteddepth12/40specificity15/30actionability15/3042 / 100
The Python SDK now requires Pydantic v2; Pydantic v1 is no longer supported.
— Simple version requirement, no migration detail beyond thatv0.38.0
16
Node.js runtime and packaging requirement raisedBREAKING42how completely this was documenteddepth12/40specificity15/30actionability15/3042 / 100
Requires Node.js >= 22; npm lockfiles are dropped from the Node.js package.
— Exact version bump named, minimal further detailv0.38.0
└──▷ BREAKING ON UPGRADE
!Table existence is now manifest-authoritative: tables that lack a manifest entry are no longer considered to exist, even if other store artifacts are present.
!The Python SDK now requires Pydantic v2; Pydantic v1 is no longer supported.
!The Node.js SDK now keys parsed embedding configs by vector column name; projects relying on the previous keying scheme will need to update their embedding config references.
!The branch merge operation is renamed to cherry_pick; any code calling merge on a branch must be updated to cherry_pick.
!Table listings are now paged from the store's own cursor; external code that constructed or passed page tokens for table listings must be updated.
!The Node.js SDK now requires Node >= 22; projects running on Node 18 or 20 must upgrade.
Pinecone is a managed vector database service for storing and querying high-dimensional embeddings at scale.
Pinecone Nexus, a knowledge engine that grounds agent answers in curated sources with citations, is now generally available.
└──▷ WHAT SHIPPED · 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
thinner coverage below
01
Pinecone Nexus knowledge engine GANEW40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
Pinecone Nexus is now generally available. It lets users point it at their sources, curate them into a context, and query that context to receive grounded, cited answers for agent workflows.
— Describes purpose and workflow but no API, config or limits named.snapshot-20260831