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.
Perplexity API provides programmatic access to Perplexity's AI search and reasoning capabilities for building applications.
Perplexity API's Agent API presets now automatically use stable prompt cache keys, cutting costs by about 5% with no changes required to existing requests.
└──▷ WHAT SHIPPED · 1 FEATUREmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Stable prompt cache keys for Agent API presetsIMPROVED75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
Agent API presets automatically assign stable prompt cache keys, letting independent requests sharing the same preset reuse the cached system prompt and tool definitions prefix, reducing costs by ~5% with no request changes required. An explicit prompt_cache_key field can still be set per-request to override the preset default when finer cache control is needed.
— Names the mechanism and override field but no numbers beyond ~5%.snapshot-20260822
Anthropic is an AI safety company providing Claude, a large language model AI assistant for text generation, analysis, and conversation.
Anthropic shipped Python SDK v1.0, a major breaking release that migrates the HTTP transport to httpx2, raises the minimum Python version to 3.10, and removes several long-deprecated surfaces including the legacy Text Completions API, sampling parameter overrides, and tool runner compaction control.
└──▷ WHAT SHIPPED · 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
SDK v1.0 requires Python 3.10 and httpx2 transportBREAKING80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
The Python SDK v1.0 requires Python 3.10 or later and moves the HTTP layer from httpx to httpx2. Custom http_client, Timeout, and transport objects must now be built from httpx2, though the DefaultHttpxClient helpers are unchanged; users who patch httpx for tracing or mocking can preserve compatibility by calling httpx2.alias_httpx() before importing anthropic.
Preserve existing tracing or mocking libraries that patch httpx after migrating to the httpx2-backed SDK.
— Names exact migration helper, version floor and compatibility shim.snapshot-20260822
02
Async raw response parsing now requires awaitBREAKING70how completely this was documenteddepth25/40specificity20/30actionability25/3070 / 100
On the async client, .with_raw_response results now require await response.parse() instead of the previous synchronous .parse() call; calling it synchronously no longer works.
Correctly await a raw response parse on the async client under SDK v1.0.
OpenAI provides APIs and tools for accessing advanced language models like GPT for building AI-powered applications.
OpenAI added per-request regional processing selection for API projects configured with Global geography.
└──▷ 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
Per-request regional processing via prefixed domainNEW55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
For projects configured with Global geography, requests can select regional processing on a per-request basis by using a prefixed domain with the project's API key. This does not change existing eligibility, data retention, endpoint, or model support requirements.
— Names mechanism and constraints but not the actual domain prefix syntax.snapshot-20260822
HyperFrames rolled out a full audio FX rack with automation lanes, EQ, and track groups to all users, introduced a new Plan v2 distributed-rendering transport (now default), and added professional color grading, a media-treatment system, RFC 8628 device-authorization CLI login, and a reworked catalog with semantic search, live variable previews, and offline fallback.
└──▷ WHAT SHIPPED · 31 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
Audio FX rack and track groupsNEW90how completely this was documenteddepth40/40specificity30/30actionability20/3090 / 100
Ships a full audio FX rack in Studio (staged rollout, now enabled for all users alongside track groups, mute, and solo) including preset folding, per-preset title design, signal-path view, frequency ruler, and family/tint lettering; a Tone module (multi-band EQ) on faders in Studio and at the Core preset-node level; a fifth FX worklet for granular pitch-shifting unlockable through character presets; an audio FX preset catalogue with one-click application; FX tails that decay naturally past the clip boundary; and the Even Out Levels levelling script in Core for automatic level normalisation. Automation lanes let per-parameter keyframed envelopes be copied/pasted, retimed, edge-stretched, shaped/simplified, time-range selected, and edited via curve/snap/direct value entry, with a shared automation-lane row per track and live value display at the playhead. Track groups add group rows to the timeline with volume control, a level meter, split disclosure, and mute-group and solo ('hear-only-this', preview-only) controls, rendering grouped audio through a summed, FX-processed bus in both preview and export. The /hyperframes-audio skill adds agent-driven audio workflows with a waveform cache keyed by file.
drawElement parallel router and circuit breakerNEW85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
Adds HF_DE_PARALLEL_ROUTER environment variable to opt in (=true) or opt out (=false) of the parallel drawElement capture path, default-on for a 5% canary ramp behind a per-install circuit breaker that automatically disables the feature if a render fallback occurs. The router's engagement threshold was lowered from 2000 to 700 frames to reduce latency on mid-length renders. Circuit-breaker state now survives CLI config wipes, and parallel-worker init telemetry in the Producer surfaces the render band's motion axis for short-comp routing decisions; a default-off flag also enables single-worker inversion for short compositions under an element ceiling as groundwork for a fast-path render route.
Catalog browsing, preview, and install improvementsNEW85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
Catalog pages now play the real composition in the player instead of a pre-recorded video; the sidebar groups 358 items under eight collapsible sections organized by what you want to make; items with variables expose an editable variables panel whose preview rebuilds live as you change values — matching exactly the accent, size, or other variable selected — with shareable links carrying those values; the install command copies the item with variables attached; reinstalling a catalog item no longer overwrites local edits; and provider cost tier for media-use items is now derived from the registry.
— Concrete numbers and UI behaviour, but no exact pathsv0.8.2v0.7.106
04
Device authorization login for CLINEW85how completely this was documenteddepth35/40specificity25/30actionability25/3085 / 100
Adds device authorization login (RFC 8628) to the CLI, enabling sign-in from attended SSH and remote-terminal sessions without API keys or loopback callbacks. The fail-closed flow validates tokens before persisting them, and leaves existing browser login unchanged.
— Named standard and flow with clear login pathv0.7.94
05
`outputDynamicRange` field in Producer APINEW85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
Adds outputDynamicRange: auto | hdr | sdr field to the Producer API for explicit control over output dynamic range, while temporarily accepting the legacy hdrMode field for rolling migrations.
Prompt Guide intent-interview system and expanded docsNEW85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
Adds BRIEF.md output from the agent's intent interview, so a later session can resume without re-asking run-shape questions, and designates frame.md as the canonical design spec, replacing design.md references throughout the prompting documentation. Adds a seven-level novice-to-capstone Prompt Guide arc at /prompting, with 18 verified prompt-to-render examples and a 62-second capstone film dissected chapter by chapter; a motion grammar reference covering eight rules, each shown as an A/B render built from the same composition; a capstone chapter dissecting 'The Timeline' — one continuous camera across nine regions, rendered twice from one template; new chapters covering storyboards, porting from Remotion, and recreating a reference video from text alone; and an appendix documenting known traps: layout waivers, the contrast-gate side effect, fromTo back-render, and round-linecap dots.
— Names files, path, and counts but is documentation, not codev0.7.85
07
New lint rules and layout checksNEW80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
Adds the anchored-connector lint rule with source-traceable visuals doctrine to the Skills system, plus telemetry measuring which lint rules fire, their cost, and which fail to converge. Adds the data-layout-allow-caption-zone waiver letting narrow caption-zone layouts bypass the layout constraint; the opt-in proseCoverageFloor rule enforcing a minimum prose-coverage threshold; content_overlap dense motion re-sampling and off_pivot_rotation hub-referenced layout checks; and rotation_pivot_drift, surfacing off-center rotation pivots during layout audits before render. Lint findings now surface inside Studio alongside CLI output.
Plan v2 rendering support and direct publishingNEW80how completely this was documenteddepth35/40specificity30/30actionability15/3080 / 100
Introduces distributed plan protocol v2 in the Producer — versioned, integrity-checked, content-addressed artifacts — retaining Plan v1 compatibility, with AWS Lambda worker support extended to protocol v2. Adds direct Plan v2 publishing to S3 from AWS Lambda and to GCS from GCP Cloud Run, streaming content-addressed artifacts without an intermediate staging step.
— Mechanism and targets named but no config or endpoint givenv0.7.73v0.7.72
09
Plan v2 becomes default render transportBREAKING80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
Distributed cloud renders now default to Plan v2 transport. AWS Lambda or GCP Cloud Run infrastructure must be redeployed from the same package version before upgrading SDK callers, or pass planProtocol: "v1" explicitly to keep prior behavior; v0.8.0 is the supported migration boundary.
— Exact migration flag and version boundary givenv0.7.111
10
Semantic search, ranking, and offline catalog fallbackIMPROVED75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
Adds local, on-device semantic (meaning-based) catalog search via the CLI, so blocks can be found by concept rather than exact keyword. Catalog search now ranks results by word position and term rarity, improving accuracy for name and rare-word queries. Search and browse fall back to the last on-disk copy when the registry is unreachable, preventing a network timeout from wiping the local catalog, and when a search finds no match the CLI outputs the command to report the gap to the registry.
In-preview rich text editing with stylingNEW70how completely this was documenteddepth30/40specificity20/30actionability20/3070 / 100
Enables editing and styling text directly in the Studio preview panel, including applying a style to a partial run of characters (sub-selection styling) and displaying every colour present in a mixed text selection simultaneously in the colour swatch. Rich text is sanitized on ingestion into a composition in the Core pipeline.
— UI mechanism described with clear starting pointv0.7.107
12
`normalize-audio` CLI commandNEW65how completely this was documenteddepth20/40specificity20/30actionability25/3065 / 100
Adds normalize-audio CLI command to match one clip's loudness level to another.
Caption templates become data-drivenIMPROVED65how completely this was documenteddepth25/40specificity30/30actionability10/3065 / 100
Makes caption-editorial-emphasis data-driven with an emphasis heuristic, caption-highlight data-driven with automatic grouping, caption-emoji-pop data-driven with a generic emoji lexicon, caption-pill-karaoke data-driven via the caption-data runtime, and caption-weight-shift data-driven via the caption-data runtime. Caption template runtimes are now encapsulated in IIFEs for isolation.
— Names all five templates but no user-facing control shownv0.7.71
14
HTML payload detection in resolveMediaDurationIMPROVED65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Producer now sniffs HTML payloads before invoking ffprobe in resolveMediaDuration, preventing non-media HTML sources from being misidentified as media files.
— Names exact function and tool in the fixv0.7.100
15
drawElement fast capture on Windows GPU hostsIMPROVED60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
Extends drawElement fast capture (~2x speed) to Windows hosts with a hardware GPU, previously macOS-only; Linux and software-GPU hosts are unchanged.
— Clear before/after but no user action requiredv0.7.78
16
Render and CLI telemetry additionsIMPROVED60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
Adds RenderPerfSummary telemetry for host/render performance in the Producer. Emits the canary decision reason alongside cohort assignment on Core and CLI telemetry events, extending the same reason emission to Studio events so forced overrides are distinguishable from ordinary cohort rolls; classifies identity persistence on every CLI telemetry event, indicating whether an install's anonymous ID will survive to the next run; adds on_battery and low_power_mode fields to render telemetry for per-machine diagnosis; makes CLI telemetry opt-out durable across invocations; and embeds invisible, unsigned renderer and version metadata into encoded output files for diagnostics.
Render-safe creator edits and copyable recipesNEW60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Makes creator media edits render-safe, ensuring edits made in creator mode are compatible with the final render pipeline. Adds copyable recipes in Creator Skills for cuts, trims, zooms, masks, transitions, and placed audio, giving agents and users reusable edit patterns.
— Names recipe types but no exact command or pathv0.8.3
18
External file conflict recovery and timeline navigationNEW60how completely this was documenteddepth30/40specificity15/30actionability15/3060 / 100
New external conflict recovery UI in Studio detects when a project file has been edited outside HyperFrames and lets users resolve the conflict without losing either version, coordinating and preserving external file changes to prevent silent overwrites. Logical timeline navigation replaces raw frame-position movement in Studio, making keyboard control of the timeline more predictable.
— Describes UI behaviour but no exact controls namedv0.7.93
19
Studio timeline performance, easing, and lane enhancementsIMPROVED60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Adds track-timeline performance monitoring in Studio. Adds bulk-edit easing for merged keyframes, enabling uniform easing changes across multiple selected keyframes at once. Adds expandable keyframe property lanes, track headers, precise keyframe retiming interactions, and nested-composition timeline support.
— Three thin Studio timeline additions grouped, no exact controls namedv0.7.85v0.7.80v0.7.77
20
Media treatment system across Core, Studio, CLI, RegistryNEW60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Adds media treatment capabilities to the Core, agent-first media treatment tools to the CLI, a media treatment inspector to Studio, media treatment overlays to the Registry catalog, and renders media treatments deterministically in the Runtime.
— Spans four surfaces but each described only brieflyv0.7.72v0.7.71
thinner coverage below
21
Professional color grading in Core and StudioNEW55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
Adds professional color grading controls to the Core rendering engine and Studio UI, and exposes agent-native color grading through the CLI for use in agentic rendering workflows.
— Names three surfaces but no specific controls listedv0.7.73
22
Keyframe ease editor and deterministic runtimeNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Adds a keyframe ease editor to Studio, backed by a deterministic keyframe ease runtime in Core.
— Names two components with minimal mechanism detailv0.7.72
23
FFmpeg install prompt before exportIMPROVED45how completely this was documenteddepth20/40specificity10/30actionability15/3045 / 100
Studio now prompts to install FFmpeg before an export starts, rather than surfacing the error after a render fails.
Background preview in all launch modesIMPROVED40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
Runs a managed background preview in every launch mode, eliminating the need to pick a specific launch path to get preview support, with unified JSON lifecycle output for previews.
— Behaviour change described but no config surface namedv0.8.4
28
Cancelable thumbnail generation in Studio ServerNEW35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Studio Server now supports cancelable thumbnail generation, allowing in-progress thumbnail jobs to be aborted.
— Single-line description with no mechanism detailv0.7.96
29
Render-completion feedback prompt triggerIMPROVED30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Triggers feedback prompts when a render completes, replacing the previous session-counter-based trigger.
— Simple trigger change with no further mechanismv0.7.107
30
Preview volume control in StudioNEW25how completely this was documenteddepth10/40specificity5/30actionability10/3025 / 100
Studio gains a preview volume control.
— Bare one-line addition with no further detailv0.7.110
31
Registry clears brand styling on re-attachIMPROVED25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Registry clears brand CSS custom properties on unbranded re-attach.
!Distributed plans now default to Plan v2; AWS Lambda or GCP Cloud Run infrastructure must be redeployed from the same package version before upgrading SDK callers, or pass planProtocol: "v1" explicitly to keep prior behavior. Use v0.8.0 as the supported migration boundary.
fenic v0.12.0 and v0.13.0 expanded the roster of supported language models, extended Python compatibility, migrated the docs service to MCP, and dropped a retired Anthropic model.
└──▷ 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.
thinner coverage below
01
New language model backends addedNEW47how completely this was documenteddepth15/40specificity22/30actionability10/3047 / 100
fenic added support for Gemini 3.7 Flash, Claude Opus 5, Gemini 3.6 Flash, and Gemini 3.5 Flash-Lite as configurable language model backends across two releases.
— Names four models but no config mechanism shownv0.13.0v0.12.0
02
Claude Opus 4.1 support removedBREAKING45how completely this was documenteddepth15/40specificity15/30actionability15/3045 / 100
Claude Opus 4.1 has been removed from the list of supported models; pipelines configured to use it will break on upgrade to v0.13.0.
— Clear before/after but no migration path givenv0.13.0
03
Python 3.13 and 3.14 supportIMPROVED35how completely this was documenteddepth10/40specificity15/30actionability10/3035 / 100
Extends Python version support to include Python 3.13 and 3.14.
Transform geospatial relations into graphs for Graph Neural Networks and spatial network analysis
City2Graph 1.0.0 adds batch morphological graph construction, GBFS shared-mobility feed loading alongside the existing GTFS pipeline, and shifts to sparse neighbor queries for large spatial graphs while deprecating the as_nx parameter.
└──▷ 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 and expanded morphological graph constructionNEW80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Adds morphological_graphs() (plural) for batch construction of morphological graphs across multiple areas in a single call, with improved error handling for GeometryCollection inputs, and expands options on the existing morphological_graph() (singular) for finer control over generation.
Build morphological graphs for multiple urban areas in one call using the new batch function.
Augment Code is an AI-powered code completion and generation tool that helps developers write code faster with intelligent suggestions.
Auggie CLI 0.35.0 adds declarative configuration for daemon pool bundles and makes environment rebuilds asynchronous, alongside smaller fixes to plan-mode path handling and MCP scope permissions.
└──▷ 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.
thinner coverage below
01
Home directory expansion in plan-mode editor pathsIMPROVED40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Plan-mode editor paths now expand ~ to the home directory.
Daytona is an open-source development environment platform that enables developers to spin up standardized, reproducible coding environments instantly.
Daytona stabilized its sandbox fork and snapshot creation API, moving these operations out of experimental status and requiring callers to migrate off the old aliases.
└──▷ 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
Stable fork and create-snapshot APIBREAKING50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
The fork and create-snapshot operations are promoted from experimental to stable API status. The experimental API aliases for these operations are now deprecated, and callers using the experimental endpoints must migrate to the stable API.
— Names the two operations and migration need, but no exact endpoint paths givensnapshot-20260822
└──▷ BREAKING ON UPGRADE
!Experimental API aliases for fork and create-snapshot are deprecated; callers using the experimental endpoints must migrate to the stable API.
Kiro adds mouse support to spec review and automatic stream recovery with configurable timeouts.
›Adds api.streamIdleSoftTimeout, api.streamIdleHardTimeout, and api.timeout settings to tune idle watchdog thresholds and the overall streaming timeout.
›Adds a 60-minute default streaming timeout so long responses are no longer cut off mid-turn.
Command Code's window centers on a new Skills manager and per-feature model picker in the Desktop app, an expanded model lineup (Ox Alpha, Qwen 3, DeepSeek V4 Flash Vision) with reasoning-effort controls, and beta BYOK provider support through a new /connect CLI menu.
└──▷ WHAT SHIPPED · 10 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. 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
BYOK provider support via /connect menuNEW80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
A new /connect menu manages provider connections directly from the CLI, adding beta support for Bring Your Own Key (BYOK) providers so teams can supply their own API keys for AI backends, plus a local-only mode that keeps BYOK credentials and traffic off external networks.
— Exact command and scope named, missing provider list.v1.30.0
02
Skills manager in Desktop SettingsNEW75how completely this was documenteddepth33/40specificity24/30actionability18/3075 / 100
Adds a Skills section in Settings that lists installed skills grouped by project, global, or bundled source with token cost shown for each skill. Supports installing skills from a GitHub repository with per-skill selection, save-location choice, and a native confirmation dialog before installation, and lets users enable, disable, and remove managed skills from the Desktop app while keeping skill state in sync with the CLI.
— Names UI path and sync behavior but no exact command.v0.1.14
03
Per-feature model selection in SettingsIMPROVED66how completely this was documenteddepth28/40specificity22/30actionability16/3066 / 100
Adds per-feature model selection in Settings for compaction, session titles, command explanations, image vision, and other feature tasks. Feature-model choices now show plan availability and keep saved model overrides visible, and compact mode names and descriptions match the CLI with the selected compaction model shown in Config.
— Names the settings screen and options, no exact keys.v0.1.14
04
Terminal copy, zoom, and resize controlsNEW65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
Adds keyboard shortcuts and a right-click menu option to copy selected terminal text, terminal text size control from Settings with zoom shortcuts when the terminal is focused, and pointer and keyboard controls to resize the terminal drawer with drag-down to close it.
— Names shortcuts and settings but not exact key bindings.v0.1.14
05
Qwen 3 model support with reasoning effort levelsNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds Qwen 3.8 27B as an available model option, then adds low, medium, and xhigh reasoning effort levels for the Qwen 3 8B and 27B models.
— Names exact effort levels but no command to set them.v1.28.1v1.28.0
06
/status reports active model and reasoning effortIMPROVED62how completely this was documenteddepth20/40specificity20/30actionability22/3062 / 100
The /status command now reports the live session's active model and current reasoning effort.
Superset is an agentic IDE to orchestrate 100+ coding agents in parallel. Run any agent with your own subscription.
Superset shipped a GitHub-triggered automations engine with trigger tables and dispatch, cloud workspaces backed by Blaxel sandboxes across desktop and mobile, and new CLI commands for workspace lookup and host wake control, alongside a major sidebar overhaul, new agent skills (Mistral Vibe, Grok CLI, browser design mode, computer control), and expanded MCP install and agent-readiness surfaces.
└──▷ WHAT SHIPPED · 39 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
CLI workspace lookup, host wake, and host targetingNEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
The CLI adds a workspaces get <workspace-id> subcommand to look up a workspace by ID, set-wake <host-id> <command> and wake <host-id> subcommands that register and trigger a configurable per-host wake command before connecting, and single-host reads with explicit host targeting in the CLI and host-service.
Look up a specific workspace by its ID directly from the CLI to quickly inspect workspace metadata.
$ superset workspaces get <workspace-id>
Configure a custom wake command for a host so the CLI can bring it online on demand.
$ superset set-wake <host-id> "<wake-command>"
superset wake <host-id>
Retrieve full workspace details by ID to confirm a workspace exists or inspect its metadata.
$ superset workspaces get <workspace-id>
Register a custom wake command for a host so the CLI can bring it online on demand.
GitHub-triggered automations engineNEW80how completely this was documenteddepth35/40specificity30/30actionability15/3080 / 100
Introduces a trigger editor in the desktop and tRPC layer for building and managing automation triggers, fires automations from GitHub events by recording GitHub deliveries as automation events via the API, adds automation trigger and event tables to the database, dispatches automations from triggers via the API and tRPC, saves triggers as a set alongside the automation, adds identityProvider and automationId scope and triggerId narrowing on the shared dispatcher, expires raw webhook payloads after 14 days, introduces one identity table for every integration, and adds enum values for every planned trigger provider up front in the database.
— Rich mechanism and named tables/endpoints, no UI walkthrough.desktop-v1.23.0
03
MCP install and agent-readiness surfacesNEW75how completely this was documenteddepth25/40specificity30/30actionability20/3075 / 100
Adds a unified MCP-install page at /mcp-install for connecting AI agents to Superset, a /mcp alias, a docs MCP server with agent_auth identity types and a reinstated OpenAPI spec, MCP server instructions and destructive/read-only tool annotations for MCP v2, and MCP discovery, markdown twin pages, and agent auth metadata as agent-readiness surfaces across the API and docs.
Cloud workspaces backed by Blaxel sandboxesNEW70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Introduces cloud workspaces backed by Blaxel sandboxes across the desktop, tRPC, and host-service layers, adds pre-baked repo and schema to sandbox provisioning so the sandbox can start itself, and brings cloud workspace management to the mobile app — list, open, terminal access, provisioning, and actions — with creation via tRPC and optimistic 'creating'/'failed' interstitial states.
Sidebar navigation and organization overhaulIMPROVED70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
The v2 sidebar gains drag-and-drop pinning with collapsible Pinned and Sessions sections, reorderable sidebar groups anywhere in the project list, configurable folder-link clicks with an open-in-Finder binding, separated tasks and pull requests sections, a ChatHistorySidebar message rail, safe-triangle hover intent on hover cards, bulk workspace actions, right-click import of untracked worktrees from the context menu, workspace pinning on the v2 dashboard sidebar, click-to-open-file/cmd-click-to-open-diff behavior, a cleaner denser restyle, and a replacement of the sidebar activity strip with port/agent chips and bulk-close hover cards.
Backend performance and configuration improvementsIMPROVED70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Moves several hot paths off the Node event loop: adds an offLoop() worker-procedure resolver to host-service, ports branchPrefix.gitInfo off the event loop, moves workspace deletion off the event loop while removing status checks that blocked bulk delete, moves hot git reads off the event loops in host-service and desktop with ratchet enforcement, limits diff-stat queries to only the active sidebar workspace item, and derives domain constants from NEXT_PUBLIC_ROOT_DOMAIN for the boid.so cutover.
— Names concrete internal mechanisms and an env var.desktop-v1.18.3
07
CLI settings command for desktop appNEW70how completely this was documenteddepth25/40specificity20/30actionability25/3070 / 100
Adds a superset settings CLI command to manage desktop app settings and theme from the command line, with live-reload when changes are applied.
Change the desktop app theme from the terminal without opening the GUI — useful in headless or scripted setups.
$ superset settings
— Runnable command with described live-reload behavior.desktop-v1.21.0
08
Ports dropdown and scanner performanceIMPROVED65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds a top-bar ports dropdown as an alternative layout for accessing forwarded ports, adds collapsible per-workspace groups within that dropdown, and improves port-scanner performance with a shared ps per scan, lsof -a, and idle-session decay for faster local port discovery.
New agent skills: orchestration, browsing, and designNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds a Superset orchestration skill and shared 'decide' and 'redesign' skills to the agents layer, ships superset:* plugin skills to all agents with a private feedback pipeline, and adds a browser design mode that lets users click any page element and send it to an agent, computer control via Cua Driver, and an engine-generic browsing skill with a Browser Use 3.0 option.
MCP package renamed and de-versionedBREAKING65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
The MCP package is renamed from packages/mcp-v2 to packages/mcp, with all user-visible surfaces de-versioned; any references to mcp-v2 paths or versioned surface names will break.
— Exact old/new package paths given as migration note.desktop-v1.18.3
11
Relay fleet: Sydney region, telemetry, and host presenceIMPROVED60how completely this was documenteddepth25/40specificity25/30actionability10/3060 / 100
Adds a Sydney (syd) region to the relay fleet for lower-latency global coverage, relay WebSocket outage telemetry with version-stamped desktop events, typed WebSocket close codes with Sentry exception capture in the relay layer, and serves host presence live from the relay Durable Object, dropping database presence writes for lower latency.
Electric sync replaced with tRPC and React QueryBREAKING60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Replaces Electric sync with plain tRPC + React Query for data fetching on desktop and mobile; the EXPO_PUBLIC_ELECTRIC_URL environment variable is removed.
— Names removed env var, a concrete migration signal.desktop-v1.21.0
thinner coverage below
13
Live agent chat sessions on mobile via ACPNEW55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Adds live chat sessions routed over the relay on mobile, live ACP agent sessions end-to-end across the host harness, mobile UI, and desktop gate, and ACP-backed workspace pages on mobile including a restyled home, native workspace screen, and diff surface.
Mobile pull request reviewNEW55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
Adds a mobile pull request screen with merge, checks, reviewers, and description, plus a new mobile diff review surface with inline comments, a native review toolbar, and a rebuilt diff renderer.
Mobile composer, sessions, and input UXIMPROVED55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Adds a unified home, attachments sheet, and glass composer with voice dictation on mobile, unifies the terminal and home composers, adds terminal session reordering from a sessions sheet persisted per workspace, groups the mobile home screen by project, adds tap-to-open links, native text selection, and a scrollbar in the mobile terminal, adds photo, file, and camera pickers, image paste, and themed system surfaces, adds an all-native SwiftUI attachments sheet, and shows skipped PR checks in the mobile sheet.
Resizable pull requests split viewNEW55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
Adds a new pull requests split view with a resizable list/detail panel that supports merge, close, and reopen actions directly in the desktop UI.
— Names supported actions, no exact navigation path.desktop-v1.24.1
17
New coding agents and models: Mistral, GPT-5.6, GrokNEW50how completely this was documenteddepth15/40specificity25/30actionability10/3050 / 100
Adds a first-class Mistral Vibe coding agent and GPT-5.6 models to the Codex model picker, plus Grok CLI agent support via a new desktop,shared integration.
Linear integration: task filtering and Discord triageNEW50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Adds Linear project/cycle filtering and sorting to the Tasks view, and auto-ingests Discord support channels into Linear Triage, mirroring Discord artifacts and enhancing tickets with Claude Sonnet.
Terminal UX: status, confirmation, scrolling, and appearanceIMPROVED50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Adds a terminal connection status indicator with a diagnosis popover, a confirmation dialog before closing a terminal pane with a running process, native-fidelity terminal wheel scrolling via a custom xterm handler with kitty identity, a harness selector on the polygraph terminal agent, and surfaces editor and terminal appearance controls in the desktop app.
Desktop workspace chrome polishIMPROVED50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Adds cmd+f search to the v2 changes pane, a View menu toggle for the presets bar, tab-drag merge preview, and replaces the update toast with an inline settings updates pill featuring an animated countdown border and pixel-dissolve exit.
New-workspace and blank-project creation experimentsIMPROVED50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
The new-workspace screen gains richer templates with labeled model/effort pills, dismissible sample prompts, and a three-arm form-factor experiment; a prompt-cards arm to help users start faster; created_at flag targeting to gate the experiment; persisted prompt history with a search popover; and the ability to create blank projects directly from the desktop app.
Workspaces page triage view and filtersIMPROVED50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Reworks the Workspaces page into a status-grouped triage list, adds an 'All devices' option to the device filter, a pin-visibility filter, and per-lane visibility toggles on the workspaces board.
v1→v2 workspace auto-migration flowNEW50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Adds a v1→v2 auto-migration boot trigger with a migrate-then-flip gate and continuity restore, plus pre-flip notice and post-flip welcome screens for migrated v1 users.
— Explains migration mechanism, no manual trigger given.desktop-v1.18.3
24
Terminal-first mobile redesignIMPROVED50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Redesigns the mobile experience to be terminal-first: removes chat stacks, treats terminals as sessions, and enables agent launch from the home screen.
— Describes before/after shift, no exact UI path.desktop-v1.21.0
25
Usage tab with quota and cost analyticsNEW45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Adds a Usage tab with per-account quota meters and token-cost analytics in the desktop and host-service, later expanded with a pill toggle and a full-page machine resources section.
— Describes tab content, no navigation path given.desktop-v1.23.0
26
Chat composer and protocol updatesNEW45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
Adds @mention and /command suggestions to the ChatComposer input, and introduces a chat-kit chat protocol v1 package with a greenfield chat design.
Workspace and host management refinementsIMPROVED40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Surfaces agent failures as a 'failed' status in the desktop and host-service, allows workspace owners to delete hosts from the desktop, and pins the local workspace name to 'local', blocking renaming.
Remote Workspaces settings and relay toggleIMPROVED40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Renames the Security settings tab to 'Remote Workspaces' and adds a relay toggle on the local host page; also surfaces a host-unreachable screen for v2 workspaces.
Mobile account management: Apple sign-in and grace-period deletionNEW40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Adds Sign in with Apple authentication on mobile, and grace-period account deletion with reactivation support.
Automation reliability and creation UXIMPROVED35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Adds retry buttons for failed automations, automatically clears the automations failure badge when the automations page is opened, and opens a newly created automation immediately on its own page instead of in a modal.
Lifecycle and activation emailsIMPROVED30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Redesigns lifecycle emails and branch-activation nudge emails sent on install, ships lifecycle emails to every signup with a functional unsubscribe (retiring the prior A/B variant), and adds a unified email layout system with an activation email sequence.
Community engagement: roadmap page and star promptNEW30how completely this was documenteddepth10/40specificity15/30actionability5/3030 / 100
Revives a public roadmap page synced from the internal Notion roadmap, and prompts users to star the superset-sh/superset repository on GitHub from within the desktop app.
Mobile paid-plan gatingBREAKING30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Gates the mobile app behind a paid plan and flattens the mobile settings page.
— Behavior change stated with no upgrade path detail.desktop-v1.22.0
39
Auto-resume interrupted agent sessionsIMPROVED25how completely this was documenteddepth15/40specificity5/30actionability5/3025 / 100
Auto-resumes interrupted agent sessions idempotently in the desktop and host-service.
— States behavior only, no scope or trigger detail.desktop-v1.23.0
└──▷ BREAKING ON UPGRADE
!The EXPO_PUBLIC_ELECTRIC_URL environment variable is removed (dropped from env examples alongside the Electric sync replacement).
!The MCP package is renamed from packages/mcp-v2 to packages/mcp, with all user-visible surfaces de-versioned — any references to mcp-v2 paths or versioned surface names will break.
Lightweight coding agent that runs in your terminal
Across two alpha releases, Codex CLI adds Guardian-mediated review of escalated commands and environment network policies for remote execution, alongside Amazon Bedrock and browser/computer-use setup in the app server, new codex agents session-configuration options, TUI permission-mode keybindings, MCP server discovery and OAuth hardening, and realtime-call attachment support.
└──▷ WHAT SHIPPED · 12 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
TUI permission-mode keybindingsNEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds previous_permission_mode and next_permission_mode actions to tui.keymap.chat in config.toml, letting users bind keys to cycle through available built-in permission modes in the TUI.
Bind keys to cycle through TUI permission modes without touching the active config file.
Realtime call attachment via existingCall transportNEW80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
Adds existingCall transport to thread/realtime/start, accepting a client-provided callId and optional realtimeSessionId so clients can attach Codex to a pre-negotiated realtime call.
Session configuration for codex agentsNEW70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Allows codex agents to accept session-configuration options — model, approval policy, sandbox mode, web search, working directory, and config overrides — when opening the agents dashboard.
MCP server discovery and OAuth issuer bindingNEW55how completely this was documenteddepth20/40specificity25/30actionability10/3055 / 100
Discovers HTTP MCP servers from selected executors and honors required MCP servers declared by those executors, and enforces issuer binding for MCP OAuth endpoints.
Guardian internal session supportNEW50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Adds Guardian internal session support: escalated commands are routed through synchronous Guardian review, and Guardian reviews are reused in async risk scoring.
38 editorial diagram types for Claude Code, Codex, and Pi. Self-contained HTML + SVG.
Adds draw.io import with format/size/fidelity control, native Pi support, new chart types, named client profiles, and automatic plugin updates.
└──▷ GET THIS VERSION
$ git clone --branch commits-2026-08-11 https://github.com/cathrynlavery/diagram-design.git
# already have the repo? check out this version:$ git checkout commits-2026-08-11
└──▷ TRY IT
Redraw an existing draw.io file into the project design system at a chosen fidelity level — useful for migrating legacy architecture diagrams without copying draw.io geometry or styling.
$ /diagram-design:import
Verify sankey flow conservation, column totals, ribbon width constancy, and label accuracy before merging a budget or pipeline diagram.
$ python3 scripts/verify-sankey.py
Validate that all ridgeline chart ridges share a single amplitude and common bin positions so silhouettes remain comparable across rows.
$ python3 scripts/verify-ridgeline.py
›Adds /diagram-design:import workflow to redraw draw.io files (raw, compressed, PNG-embedded, and SVG-embedded) at a chosen format, size, and detail level in the project design system.
›Adds native Pi package support for compatibility with the Pi platform.
›Adds verify-sankey.py script enforcing five sankey invariants: flow conservation per node, equal column totals, constant ribbon width, printed-label accuracy, and light/dark variant consistency.
›Adds verify-ridgeline.py script enforcing eight ridgeline invariants including shared amplitude, even pitch, shared bins, and zero-closed outlines.
›Adds treemap diagram type for part-of-whole visualization by area.
+9 moreshow less
›Ships ten additional editorial diagram types in a single release.
›Adds dumbbell as a variant of the Bar diagram type.
›Adds slopegraph as a variant of the Line diagram type for visualizing change between two states.
›Adds animated example example-queue-animated.html for Semantic Pattern #1 (Fan-in Queue / Bottleneck).
›Adds animated example example-paved-road-animated.html for Semantic Pattern #5 (Secure Paved Road).
›Adds named client profiles support.
›Adds automatic plugin updates via native marketplaces with a version gate.
›Adds pre-draw checkpoint, docs-sync gate, packaged self-check, and ADRs to the skill package.
Autonomous coding agent as an SDK, IDE extension, or CLI assistant.
Cline's desktop beta focused on reliability and first-run experience, preventing lost prompts during cloud handoffs and reworking onboarding with centralized tool settings.
└──▷ 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.
thinner coverage below
01
Redesigned onboarding with centralized tool settingsNEW31how completely this was documenteddepth15/40specificity8/30actionability8/3031 / 100
Ships a redesigned first-run onboarding flow and centralizes tool availability settings across the desktop app.
Typed prompts persist through cloud handoffsIMPROVED25how completely this was documenteddepth15/40specificity5/30actionability5/3025 / 100
The desktop beta now preserves typed prompts when a task is handed off to Cline's cloud, preventing in-progress text from being lost during the transition.
Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.
Claude Code v2.1.239 ships a Python SDK migration helper, synced plugin management across cloud sessions, and data-residency cost transparency, alongside smaller reliability and platform-parity improvements.
└──▷ WHAT SHIPPED · 11 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. 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
`/claude-api upgrade` migration subcommandNEW75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
New /claude-api upgrade subcommand migrates Python projects from the anthropic 0.x SDK to 1.x, including updating timeout usage from httpx.Timeout to anthropic.Timeout.
— Names exact subcommand and API change but no output detailv2.1.239
02
Synced plugin management in cloud sessionsNEW75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
Plugins synced from claude.ai now appear as name@synced in cloud sessions and can be managed with claude plugin enable <name>@synced / claude plugin disable <name>@synced; a synced plugin never overrides a locally installed plugin with the same name.
Enable a plugin synced from claude.ai in a cloud session without overriding any locally installed plugin of the same name.
$ claude plugin enable my-plugin@synced
— Exact commands and override behavior given with examplev2.1.239
03
Cross-session messaging and agent discoveryIMPROVED65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Windows now supports cross-session messaging, letting Claude Code sessions message each other with SendMessage and discover each other via ListAgents, matching existing macOS/Linux behavior. ListAgents and /list-agents now also include live teammates, not just subagents and other local sessions.
— Names commands and platforms but no invocation examplev2.1.239
04
Data-residency cost transparencyIMPROVED60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Cost estimates shown via /cost, the status line, and --max-budget-usd now factor in the 1.1× US-only-inference premium charged for data-residency workspaces.
— Names surfaces and exact multiplier, no usage stepsv2.1.239
05
Retry watchdog fails fast on spend limitsIMPROVED60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
CLAUDE_CODE_RETRY_WATCHDOG persistent retry mode now fails immediately on organization spend-limit and out-of-credits errors instead of retrying indefinitely.
`/goal` check-in backoff scheduleIMPROVED50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Repeat check-ins on long-running background work started via /goal now back off on a schedule of 30 minutes, then 1 hour, then every 2 hours, instead of firing every 30 minutes.
Fullscreen renderer for enterprise cloud providersIMPROVED40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
The one-time fullscreen renderer offer, previously excluded for some setups, now extends to Bedrock, Vertex, Foundry and other previously excluded configurations; new installs on these providers now start in fullscreen.
— Names providers affected but limited mechanism detailv2.1.239
08
Chrome tab group cleanup in Claude in ChromeIMPROVED40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
/clear now closes the session's Chrome tab group, and empty tab groups are also closed automatically on /resume and on exit.
— Names commands and behavior but narrow scopev2.1.239
09
Alpine/musl native add-on supportIMPROVED35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
On Alpine/musl builds, native image paste, clipboard, and audio-capture add-ons now load using musl-built binaries.
— Names affected add-ons but no user-facing actionv2.1.239
10
Usage-limit reset timing in messagesIMPROVED30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
The usage-limit message now also shows when your session or weekly limit resets, in addition to the existing monthly spend limit display.
— Describes change but no interaction surface namedv2.1.239
11
File paths for mobile-uploaded imagesIMPROVED30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
In remote sessions, images uploaded from mobile now include their saved file path so Claude can copy them into files it creates.
— Describes benefit but no concrete surface namedv2.1.239
an open source, extensible AI agent that goes beyond code suggestions - install, execute, edit, and test with any LLM
Goose v1.47.0 adds OAuth pre-registration for streamable_http extensions, a git branch indicator in the chat UI, and a recent-models picker, while removing several tools from the computercontroller extension.
└──▷ 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
Tools removed from computercontroller extensionBREAKING70how completely this was documenteddepth20/40specificity30/30actionability20/3070 / 100
The automation_script, web_scrape, and cache tools are removed from the computercontroller extension.
— Names exact removed tools but no migration guidancev1.47.0
02
Pre-registered OAuth for streamable_http extensionsNEW65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Goose now supports pre-registered OAuth clients for streamable_http extensions, enabling MCP extensions that use pre-configured OAuth credentials without requiring interactive login.
— Explains mechanism and extension type, but no config key shownv1.47.0
thinner coverage below
03
Git branch indicator in chat bottom barNEW45how completely this was documenteddepth20/40specificity10/30actionability15/3045 / 100
Adds an interactive git branch indicator to the chat bottom bar, showing the current branch at a glance during sessions.
— Names UI location but no further behaviour detailv1.47.0
04
Recent-models pickerNEW10how completely this was documenteddepth5/40specificity5/30actionability0/3010 / 100
Adds a recent-models picker, as noted in the release summary, though no further detail on its behaviour is provided.
— Only mentioned in summary, no detail givenv1.47.0
└──▷ BREAKING ON UPGRADE
!The automation_script, web_scrape, and cache tools are removed from the computercontroller extension.
OpenHands v1.15.0 focuses on onboarding and workspace visibility, adding a getting-started checklist, an LLM provider-connections UI, an automations catalog installer, and improvements to the conversation view and event streaming.
└──▷ WHAT SHIPPED · 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
thinner coverage below
01
Batched StreamingDeltaEvents for real-time UIIMPROVED55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Batches StreamingDeltaEvents so the UI keeps pace with fast models, enabling reliable real-time streaming at higher throughput.
— Names event type and mechanism, but no user-facing actionv1.15.0
02
LLM provider-connections UINEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Adds an LLM provider-connections UI for the local agent-server, letting practitioners configure provider connections directly from the interface.
— Names UI and agent-server but no config keys or flagsv1.15.0
03
Getting-started checklist in sidebarNEW50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
Adds a getting-started checklist in the sidebar with a settings toggle to guide new users through initial setup.
— Clear UI location and toggle named, no further mechanismv1.15.0
04
Conversation overview panel and commits drawerNEW40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Adds a conversation overview panel and unified commits drawer to the conversation view.
— Two named UI additions but no behavior detailv1.15.0
05
Automations catalog installerNEW35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Adds the ability to install an automations catalog entry that ships a script bundle, expanding the automations workflow.
— Thin description, no install command or catalog path givenv1.15.0
06
Workspace path shown in Files viewIMPROVED35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Shows the workspace path in the Files view for easier orientation within multi-folder workspaces.
— Simple UI change, no further mechanism describedv1.15.0
DeepSeek Harness shipped a durable Agent Teams runtime, native Files API storage for images, and multimodal/vision support in the llm-deepseek provider, alongside MCP support and a series of image-pipeline and web UI refinements.
└──▷ WHAT SHIPPED · 17 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
File-store for DeepSeek Files APINEW80how completely this was documenteddepth35/40specificity25/30actionability20/3080 / 100
Introduces file-store for the DeepSeek Files API with a MAX_CHAT_IMAGE_BYTES cap of 32 MiB, upload deduplication, expiry-based invalidation, and quota-recovery batch cleanup.
— Names config key, cap value and cleanup mechanism preciselydsh-v0.1.1-rc.2
02
Canonical image encoding versioningNEW70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Stores a deterministic canonical image encoding, versioned as REQUEST_IMAGE_TRANSFORM_VERSION = 'request-image-v4', with preferred quality levels of 85 and 80, enabling stable cache and upload-index identity across requests.
— Names exact version string and quality valuesdsh-v0.1.1-rc.2
03
Unified image request pipelineIMPROVED65how completely this was documenteddepth30/40specificity20/30actionability15/3065 / 100
Unifies the 'master' and Files request image pipelines via offloadRequestImagesWithPolicy, consolidating how inline base64 and Files-API-referenced images are prepared for chat requests, and expands the source upload envelope to accept a broader set of image sources through this unified path.
— Names the consolidating function and its scopedsh-v0.1.1-rc.2
thinner coverage below
04
Decoupled Files and stream timeoutsIMPROVED55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Decouples Files and stream timeouts in the DeepSeek adapter, using separate deadline and idleWatchdog/timeoutOf controls so a slow Files upload no longer races the stream timeout.
— Names the specific timeout controls and the bug fixeddsh-v0.1.1-rc.2
05
Vision and multimodal support in llm-deepseekNEW50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Publishes the DeepSeek vision model via the llm-deepseek package and adds multimodal request support to the same provider, allowing image content alongside text in DeepSeek LLM calls.
read_image dimension reportingNEW50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Adds read_image dimension reporting: the tool now reports downscaled dimensions and the coordinate scale factor when an image is resized before being sent to the model.
— Names the function and the reported metadatadsh-v0.1.1-rc.2
07
Bounded multi-query web searchNEW50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
Adds bounded multi-query web search, letting agents issue multiple search queries in a single web tool call with enforced query-count limits.
— Describes mechanism but no exact limit givendsh-v0.1.0-rc.8
08
Durable Agent Teams runtimeNEW45how completely this was documenteddepth25/40specificity10/30actionability10/3045 / 100
Adds a durable Agent Teams runtime enabling persistent multi-agent coordination across sessions.
Markdown table display improvementsIMPROVED40how completely this was documenteddepth20/40specificity10/30actionability10/3040 / 100
Sizes markdown tables by column count in the web UI, automatically widening wide tables past the standard column boundary, and reveals wide-table scrollbars on hover instead of painting them persistently.
— Names two related UI behaviours, no config surfacedsh-v0.1.1-rc.1
11
Multi-line ask_user_question answersIMPROVED35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Enables multi-line responses to ask_user_question in the web UI, allowing agents to receive longer free-text answers from users.
— Names the tool but limited mechanism detaildsh-v0.1.1-rc.1
12
File-open failure handling in chat viewNEW35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Adds file-open failure handling in the chat view, surfacing errors inline when attachments cannot be opened.
— Names the surface but describes only outcomedsh-v0.1.0-rc.8
13
MCP support in packaged Python runtimeNEW30how completely this was documenteddepth15/40specificity10/30actionability5/3030 / 100
Adds MCP (Model Context Protocol) support in the packaged Python runtime.
— States the addition without configuration detaildsh-v0.1.0-rc.8
14
Structured index injection tableNEW25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Adds a structured index injection table and client boot seams via the webserver package.
Windsurf's Devin Desktop is an AI-powered IDE that provides autonomous coding assistance, debugging, and development workflow automation.
Devin Desktop v3.8.20 introduces detachable multi-window agent sessions, a reviewable Markdown plan mode, live shell output streaming, and a string of session-management, workspace-trust and network-access reliability fixes.
└──▷ WHAT SHIPPED · 12 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Multi-window Agent Command CenterNEW80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
New devin.agentWindow.location setting splits the Agent Command Center into a separate window from the editor. The Command Center now follows whichever space is selected instead of being tied to one folder, converts an editor window in place with no reload or save prompt, and supports any number of agent windows running side by side.
— Names the config key and behavior, minor gap on defaultsv3.8.20
02
post_setup_worktree hooks for Devin Local worktreesNEW75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
post_setup_worktree hooks now run for worktrees created from a Devin Local session, copying .env files and other untracked setup before the session starts.
— Named hook and file behavior fully explainedv3.8.20
03
Windows Devin CLI install shimIMPROVED65how completely this was documenteddepth25/40specificity20/30actionability20/3065 / 100
On Windows, Install Devin CLI now writes a shim to the bundled CLI so updating Devin Desktop also updates the devin command.
— Clear mechanism and command named, narrow scopev3.8.20
04
Live shell output streamingNEW60how completely this was documenteddepth30/40specificity15/30actionability15/3060 / 100
Live shell output now streams into the session while a command runs; finished shell rows expand to show the full command and its complete output.
— Mechanism fully described, no config surface namedv3.8.20
thinner coverage below
05
ACP agent activity-sharing settingsNEW55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
New settings control whether integrated terminal activity and local user-edit activity are shared with ACP agents; both default to on.
— Describes toggles but not exact setting namesv3.8.20
06
Plan mode Markdown plan fileIMPROVED55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
Plan mode now produces a full Markdown plan file that can be reviewed separately, with an explicit Implement button to proceed.
Session and tab management improvementsIMPROVED55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Devin Local tabs now show the same status indicators as Cascade legacy tabs; the Current Workspace view filters out other projects' conversations; the sessions sidebar gains improved filtering and sorting controls; session tabs and the command palette now offer 'Copy Session URL'; and sessions can now be renamed from the tab dropdown.
— Groups five thin UI increments, each namedv3.8.20
08
Workspace trust prompts for local agentsNEW55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
The agent sidebar, composer, and welcome page now warn when a workspace is untrusted and offer a trust workspace prompt to activate local agents.
— Names three surfaces where the warning appearsv3.8.20
09
Network config conflict and failure explanationsIMPROVED55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
Saving a session's network config now reports a conflicting change instead of silently discarding it, and approving a network access request now explains why it failed.
— Describes two concrete before/after error-handling fixesv3.8.20
10
Faster Agent/Editor mode switchingIMPROVED40how completely this was documenteddepth10/40specificity15/30actionability15/3040 / 100
Significantly improved performance for switching between Agent and Editor mode via Ctrl/Cmd+G.
Persistent project memory for AI coding agents. Structured scaffold + drift detection CLI.
mex built a local SQLite code knowledge graph with new mex graph/mex impact commands, then substantially extended mex graph scope into bounded, source-backed, evidence-aware retrieval, added compiler-backed TypeScript extraction (with a new hard TypeScript version pin), and shipped several new drift checkers for mex check.
└──▷ WHAT SHIPPED · 10 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. 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
`mex graph scope` and JSONL agent protocolNEW88how completely this was documenteddepth35/40specificity28/30actionability25/3088 / 100
Introduced in v0.7.0 as a command for compact, scored task-neighborhood retrieval, backed by a deterministic JSONL agent protocol with explicit detail levels, scored selection reasons, stable ordering, node quotas, and a hard estimated-output-token ceiling. In v0.7.2, mex graph scope now defaults to bounded source-backed retrieval, returning meta, source, flow, and summary JSONL records prioritized by relevance and execution-path confidence instead of a minimal manifest; adds evidence-aware JSONL protocol v3 records for source ranges, directed execution flows, summaries, omissions, and trustworthy fallback guidance; and scope budgets now adapt to repository size, enforcing per-response file, node, flow, and source ceilings while distinguishing mandatory evidence from optional truncation.
Get source-backed, token-budgeted scope for a task query so an agent can answer from a single graph call instead of expanding node IDs or reopening files.
$ mex graph scope "how does the authentication middleware handle token expiry"
Retrieve a compact, scored task neighborhood around a symbol to feed focused context to an agent.
$ mex graph scope <node-id>
— Names protocol fields, ceilings and version history; runnable example given.v0.7.2v0.7.0
02
New and improved drift checkers in `mex check`IMPROVED73how completely this was documenteddepth30/40specificity28/30actionability15/3073 / 100
Adds a twelfth drift checker for grounds_to code-node grounding, covering drift, gone, ambiguous, and durable moved-node repair behavior. Adds checkFrontmatterCompleteness, flagging context/*.md and patterns/*.md files missing recommended frontmatter fields (name, description, last_updated). Adds checkStalePatterns, flagging pattern files with no inbound reference from ROUTER.md or any context/*.md file. Improves checkToolConfigSync to skip user-authored files lacking the scaffold marker and to identify the actual managed config file that drifted rather than always blaming the first file in the list.
— Every checker and the fields/files it flags are named verbatim.v0.7.0v0.7.2
03
`mex graph`, `mex graph query`, `mex graph get`, `mex impact` commandsNEW70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
Adds mex graph, mex graph query, mex graph get, and mex impact commands for graph building, structural lookup, targeted source expansion, and blast-radius analysis.
Build the code graph for your project, then inspect the blast radius of a specific symbol before refactoring it.
$ mex graph && mex impact <node-id>
— Commands named with runnable example, but purpose only briefly described.v0.7.0
04
Compiler-backed TypeScript extraction via TS compiler APIBREAKING70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds compiler-backed TypeScript extraction via the TypeScript compiler API, resolving calls, imports, inheritance, containment, callback flow, and declaration-aware source regions. TypeScript 5.9.3 is now an exact runtime dependency, so projects on a different TypeScript version must pin or align to 5.9.3 for graph construction to work.
— Names the compiler API and exact version pin with clear migration note.v0.7.2
05
Local SQLite code graph engineNEW68how completely this was documenteddepth30/40specificity28/30actionability10/3068 / 100
Builds a deterministic local SQLite code graph (stored in .mex/graph.db) for TypeScript, TSX, JavaScript, JSX, Python, and Rust, with cross-file resolution, body hashes, MinHash fingerprints, and LSH reconciliation. This graph engine requires Node.js 22.5 or later, raised from the previous minimum.
— Rich mechanism and languages named, but no direct command shown here.v0.7.0
thinner coverage below
06
`mex graph ground` retro-grounding for pre-0.7 scaffoldsNEW55how completely this was documenteddepth20/40specificity15/30actionability20/3055 / 100
Adds mex graph ground to idempotently retro-ground populated pre-0.7 scaffolds while preserving their prose.
Retro-ground an existing pre-0.7 scaffold to attach grounds_to code-node entries without rewriting prose.
$ mex graph ground
— Command and behavior named with a runnable example.v0.7.0
07
Inline `mex://<node-id>` anchors for symbol mentionsNEW45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Introduces inline mex://<node-id> anchors for navigable symbol mentions, with warning-only drift detection and durable sync repair.
— Names the anchor format but no usage example given.v0.7.0
08
Express route-to-handler resolver in code graphNEW30how completely this was documenteddepth10/40specificity15/30actionability5/3030 / 100
Adds an Express reference resolver that links route registrations to handler nodes in the code graph.
— Single-sentence description with no mechanism or example.v0.7.0
09
Reproducible retrieval and agent evaluation harnessesNEW30how completely this was documenteddepth10/40specificity10/30actionability10/3030 / 100
Ships reproducible retrieval and agent evaluation harnesses under evaluate/.
— Names the `evaluate/` path but no further detail on usage.v0.7.0
10
Source-chunk search and graph-integrity reportingNEW25how completely this was documenteddepth10/40specificity10/30actionability5/3025 / 100
Adds source-chunk search, parser-health metadata, and graph-integrity reporting.
— Bare list of capability names with no detail on behavior.v0.7.2
└──▷ BREAKING ON UPGRADE
!TypeScript 5.9.3 is now an exact runtime dependency; projects using a different TypeScript version will need to pin or align to 5.9.3 for graph construction to work.
!Minimum Node.js version is now 22.5 (raised from the previous minimum) because the graph engine requires it.
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 added two new language backends (OCaml and Common Lisp), a JS/TS factory-function graph modeling improvement, and Markdown corpus filtering with frontmatter parsing, alongside a run of reliability fixes across the MCP server, Bedrock backend, merge-graphs, and TSX parsing, plus new extraction flags for deduplication and partial-build handling.
└──▷ 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
Shared viz_node_limit config for git hooksNEW90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
Adds viz_node_limit=<int> key to .graphifyrc — graphify hook install reads it and bakes the value into generated git hooks as a ${GRAPHIFY_VIZ_NODE_LIMIT:-<n>} default, so a per-run env var still overrides the committed limit. graphify hook status now reports the baked viz_node_limit from .graphifyrc and degrades gracefully on a malformed .graphifyrc.
— Config key, env var, and commands all namedv0.9.44
02
`--no-dedup` flag for extractionNEW85how completely this was documenteddepth30/40specificity25/30actionability30/3085 / 100
graphify extract --no-dedup skips fuzzy near-duplicate node merging during build and incremental merge runs, while preserving exact-id uniqueness and refusing surprising node drops via a shrink guard.
Preserve symbolically distinct nodes that fuzzy-matching would otherwise collapse — useful when distinct but similarly-named symbols (e.g. overloads or homonymous types across modules) must stay separate in the graph.
$ graphify extract --no-dedup .
— Runnable command with mechanism and guardrail namedv0.9.48
03
Common Lisp language extractionNEW85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
Adds Common Lisp extraction for .lisp, .cl, .lsp, and .asd files via tree-sitter-commonlisp (optional [commonlisp] extra), covering packages, classes, functions, methods, generics, macros, variable definers, same-file calls, and cross-file opened/:used package resolution.
— File extensions, install extra, and resolution scope namedv0.9.46
04
OCaml language extractionNEW85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
Adds OCaml language support (.ml/.mli) via the optional [ocaml] extra, extracting modules, top-level and module-level values/functions, types and variant constructors, open imports, and function calls — including qualified calls like Geo.area resolved to the real definition across files.
— Extensions, extra, and cross-file resolution example namedv0.9.43
05
Bedrock backend timeout, retry, and response fixesIMPROVED80how completely this was documenteddepth30/40specificity25/30actionability25/3080 / 100
The Bedrock backend now honors GRAPHIFY_API_TIMEOUT and GRAPHIFY_MAX_RETRIES environment variables instead of silently defaulting to botocore's 60-second timeout, and reads the first text block of a Converse response rather than block 0, enabling reasoning-capable models to return non-empty graphs.
Set aggressive timeout and retry limits for the Bedrock backend so long reasoning traces do not hang indefinitely.
— Two env vars and exact prior default namedv0.9.30
06
Bounded MCP graph-context cacheIMPROVED75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
The MCP server's multi-project graph-context cache is now bounded via GRAPHIFY_MAX_CONTEXTS (LRU eviction, default 8) instead of growing unbounded.
Cap the MCP server's in-memory graph cache to avoid unbounded growth in a workspace with many projects.
$ GRAPHIFY_MAX_CONTEXTS=4 graphify-mcp
— Env var, default, and eviction mechanism namedv0.9.30
07
`--allow-partial` flag and stricter extract failure handlingBREAKING70how completely this was documenteddepth25/40specificity20/30actionability25/3070 / 100
graphify extract now exits non-zero instead of writing a zero-node graph when a whole-pass AST failure occurs on a fresh build; pass --allow-partial to opt into the previous best-effort partial-graph behavior.
— Exact flag and before/after behavior namedv0.9.33
08
Factory-function API object modeling for JS/TSNEW65how completely this was documenteddepth30/40specificity25/30actionability10/3065 / 100
JavaScript/TypeScript factory functions that assign callable members to a local object literal (const api = {}; api.foo = fn) now keep those members in the graph — the API object is modeled beneath its factory and assigned functions attach as methods, including arrow-function assignments and their intra-factory call edges.
— Mechanism detailed but no user-facing commandv0.9.47
09
Markdown node-kind filtering and frontmatter attributesNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Markdown nodes now carry a node_kind attribute (page vs heading) so a docs corpus can be filtered by kind, and leading YAML frontmatter is parsed onto the page node as bounded, sanitized attributes.
— Attribute and values named but no query syntax shownv0.9.46
thinner coverage below
10
Edge direction preserved in merge-graphsIMPROVED50how completely this was documenteddepth20/40specificity15/30actionability15/3050 / 100
merge-graphs now preserves edge direction instead of rewiring import edges to the importing file.
— Names command but limited mechanism detailv0.9.30
11
TSX grammar for .tsx parsingIMPROVED50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
TypeScript .tsx files now parse with the TSX grammar, preventing absolute-path node IDs from leaking into edge endpoints.
— Names file type and fixed bug, no user actionv0.9.30
12
AST-cache re-anchoring after corpus moveIMPROVED50how completely this was documenteddepth25/40specificity15/30actionability10/3050 / 100
AST-cache hits after a corpus move or clone now re-anchor stored root-relative node IDs to the new root, preventing stale absolute IDs from replaying.
— Mechanism described but no direct reader actionv0.9.30
13
One-time hosted platform pointer in installIMPROVED30how completely this was documenteddepth10/40specificity10/30actionability10/3030 / 100
graphify install now prints a one-time pointer to the hosted platform after the setup summary.
!graphify extract now exits non-zero instead of writing a zero-node graph when a whole-pass AST failure occurs on a fresh build — use --allow-partial to restore the previous best-effort behavior.
herdr's headline shift this window is Windows reaching general availability with full agent-integration parity and remote attach from Windows clients, alongside a wave of new config keys, keybindings, and session-restore support for Qwen Code, Grok CLI, and Antigravity CLI.
└──▷ 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
Native session restore for Qwen Code, Grok CLI, and Antigravity CLINEW83how completely this was documenteddepth30/40specificity28/30actionability25/3083 / 100
Adds Qwen Code detection for idle, working, and user-confirmation states plus optional native session restore. Adds Grok CLI session reporting and native restore via grok --resume <id> (also exposed via herdr integration), and Antigravity CLI session reporting and native restore via agy --conversation <id>.
Resume a detached Grok CLI session by ID after reconnecting to a long-running herdr server.
Right-click routing to mouse-reporting apps in panesNEW78how completely this was documenteddepth25/40specificity28/30actionability25/3078 / 100
Panes can now route right-click gestures to mouse-reporting applications via the pane menu, herdr pane input, pane.input.set, or the pane split --right-click pane launch option.
Windows general availabilityNEW75how completely this was documenteddepth35/40specificity28/30actionability12/3075 / 100
Windows support is now generally available and ships through the stable update channel by default, with installer and keybinding support. Cursor Agent CLI, MastraCode, Hermes Agent, and Grok CLI integrations now install and run natively on Windows, and all agent integrations are supported on Windows, closing the gap with Unix workflows. Windows preview downloads bundle Herdr and a modern app-local ConPTY runtime in a single archive, and the IME automatically switches to ASCII in prefix mode on Windows (Korean IME) for more reliable keyboard input.
Terminal appearance and tab bar config keysNEW75how completely this was documenteddepth25/40specificity30/30actionability20/3075 / 100
Adds ui.window_title to keep the outer terminal window title in sync with the active workspace and host, ui.pane_outer_borders to independently show or hide outside split-pane edges, ui.pane_scrollbars = false to hide pane scrollbars and reclaim their column, and ui.tab_bar_position = "bottom" to move the tab row below panes. Adds ui.status_indicators = "symbols" for distinct static shapes per agent state, theme.custom.sidebar_bg for a custom sidebar background, and theme.custom.selection_bg for a per-theme selection cursor color. The desktop tab bar also gained configurable right-aligned status entries for zoom state, hostname, date/time, literal text, and asynchronously refreshed command output.
Keep your terminal emulator's tab bar and window manager title bar showing the active Herdr workspace and host.
Keyboard bindings for tab reorder and pane resizeNEW73how completely this was documenteddepth20/40specificity28/30actionability25/3073 / 100
Adds optional keys.move_tab_previous and keys.move_tab_next bindings to reorder the active tab in place, wrapping at either end, and keys.resize_pane_left, keys.resize_pane_down, keys.resize_pane_up, and keys.resize_pane_right bindings to resize the focused pane in one keystroke without entering resize mode.
Resize the focused pane instantly from the keyboard without entering resize mode — useful in keyboard-driven workflows.
Headless agent detection improvementsIMPROVED70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds HERDR_PROCESS_DETECTION=child-groups environment variable to opt Linux runtimes without terminal foreground process groups into child-group agent detection, and adds automatic text history reads for idle alternate-screen agents, with the application viewport restored after collection.
— Named env var but viewport-restore mechanism only described in prosev0.8.0
08
`herdr --skill` flag for agent contextNEW70how completely this was documenteddepth20/40specificity20/30actionability30/3070 / 100
Adds herdr --skill flag to print the agent skill bundled with the running binary, so an agent can load it without fetching external docs. Startup output now also prints the bundled agent skill and next CLI steps to guide agents and users toward herdr --skill and related entry points.
Print the agent skill embedded in the binary so an AI agent can load it into context without fetching external docs.
Headless server terminal sizing and frame streamingIMPROVED60how completely this was documenteddepth20/40specificity20/30actionability20/3060 / 100
Headless servers now use a configurable 120×40 virtual terminal (up from 80×24) when no client is attached, and panes gained direct frame streaming for lower-latency terminal output delivery.
Observe a remote herdr session at a fixed terminal geometry — useful for headless CI agents that need a predictable screen size.
Plugin marketplace discoveryNEW57how completely this was documenteddepth25/40specificity22/30actionability10/3057 / 100
The plugin marketplace now discovers valid manifests at repository roots and subdirectories, groups multiple plugins per repository, and publishes their versions and exact default-branch commits. It also adds discovery shelves — trending and new arrivals — for browsing available plugins, and indexes manifests with star-history tracking to power those trending and new-arrival surfaces.
Live filtering in keybind help overlayIMPROVED48how completely this was documenteddepth15/40specificity18/30actionability15/3048 / 100
Adds live filtering to the keybind help overlay using /, Backspace, and Ctrl+U, letting users search or narrow the keybind reference directly in the UI.
vMLX 1.6.35 makes SSD prompt caching the default cache tier, switches cache budgets to a percent-of-disk model, stores prefix caches at full precision, and lets prompt caches survive a hard restart across five cache architectures.
└──▷ WHAT SHIPPED · 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Unified SSD cache budget and eviction policyIMPROVED70how completely this was documenteddepth32/40specificity28/30actionability10/3070 / 100
One unified budget now covers all cache types vMLX writes — plain KV blocks, typed companion state, native composite records, rotating sliding-window state, and multimodal blocks — across every model and session, with oldest prompts evicted first. Eviction additionally protects the prefix currently being actively reused and removes idle ones first, including for models that are not currently running.
— Names all covered cache types and eviction logic, but no user-facing controlv1.6.35
02
SSD prompt cache enabled by defaultBREAKING62how completely this was documenteddepth28/40specificity16/30actionability18/3062 / 100
The SSD prompt cache is now the default; the in-memory paged cache is OFF by default, keeping memory consumption close to the loaded model size rather than growing with conversation length. This is a breaking change: any setup relying on the RAM tier being active must re-enable it explicitly via Session Settings.
— Names the toggle and re-enable path but no exact setting namev1.6.35
03
Prompt cache survives restart across five architecturesNEW62how completely this was documenteddepth26/40specificity28/30actionability8/3062 / 100
Prompt caches now survive a hard kill and restart across five cache architectures: DeepSeek-V4 composite, rotating sliding-window with images, SSM/GatedDelta companion, dots3 DSA, and MiniMax sparse MSA.
— Names five specific architectures but no manual action describedv1.6.35
thinner coverage below
04
Full precision stored prefix cachingIMPROVED58how completely this was documenteddepth26/40specificity24/30actionability8/3058 / 100
Stored prefix caches are now full precision for every model family; TurboQuant stored-KV encoding was measured under 1% improvement on time-to-first-token, so exactness is preferred over the quantized encoding.
— Cites the benchmark tradeoff but change is automatic, not user-facingv1.6.35
05
Percent-based SSD cache budget with size warningIMPROVED56how completely this was documenteddepth24/40specificity20/30actionability12/3056 / 100
SSD cache budget is now expressed as a percent of available disk (10% by default) instead of a flat gigabyte value, scaling proportionately across drive sizes. The engine also now emits an explicit warning when a cache budget is smaller than a single prompt's block chain, instead of silently storing nothing.
— Gives the default percentage but no config key to change itv1.6.35
06
Session Settings cache visibility and controlsIMPROVED51how completely this was documenteddepth20/40specificity16/30actionability15/3051 / 100
Session Settings now surfaces the RAM-tier trade-off at the top — noting the ~2% time-to-first-token gain and the memory cost — with a direct link to the setting. The 'Clear SSD cache for this session' button now reports which cache tiers were actually cleared and which were still in use, rather than claiming success either way.
— Names the exact UI button and setting locationv1.6.35
└──▷ BREAKING ON UPGRADE
!The in-memory paged cache is now OFF by default; any setup relying on the RAM tier being active will need to re-enable it explicitly via Session Settings.
SGLang is a high-performance serving framework for large language models and multimodal models.
SGLang v0.5.18 headlines a 2.38x faster cold start via overlapped checkpoint staging and a FlashInfer MNNVL allreduce path for higher decode throughput, alongside seven new model integrations, a unified kernel cache directory, and a string of kernel- and dependency-level optimizations.
└──▷ 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
Overlapped checkpoint staging at startupNEW93how completely this was documenteddepth35/40specificity28/30actionability30/3093 / 100
The --startup-weight-load-mode overlap flag overlaps checkpoint page staging with CUDA graph capture at startup; on Qwen3-32B on H100 this cuts startup time from 84.8s to 35.6s, a 2.38x speedup.
Dramatically cut server cold-start time on large models by overlapping weight loading with CUDA graph capture.
— Exact before/after numbers, mechanism, and a runnable command.v0.5.18
02
FlashInfer MNNVL pure allreduceNEW88how completely this was documenteddepth32/40specificity28/30actionability28/3088 / 100
The --enable-flashinfer-pure-allreduce flag routes non-fused allreduce sites through the FlashInfer MNNVL workspace instead of NCCL; it is auto-enabled for DeepSeek-V3/V3.2/V4 and delivers up to +6.9% decode throughput at small batches on Blackwell GPUs.
Boost small-batch decode throughput on non-DeepSeek models by routing allreduce through the FlashInfer MNNVL workspace.
— Names flag, target models, hardware and throughput gain.v0.5.18
03
Unified kernel cache directoryBREAKING82how completely this was documenteddepth28/40specificity26/30actionability28/3082 / 100
All kernel caches — Triton, FlashInfer, Inductor, DeepGEMM, and CUDA driver — are consolidated under a single SGLANG_CACHE_DIR environment variable, letting operators redirect them to a shared persistent volume. This is a breaking change: the first launch after upgrading will recompile all kernels once.
Redirect all SGLang kernel caches to a shared persistent volume to avoid recompilation across container restarts.
— Names the env var, lists caches, and states the migration impact.v0.5.18
04
Delayed sampling for overlap decodeNEW66how completely this was documenteddepth22/40specificity22/30actionability22/3066 / 100
The SGLANG_ENABLE_DELAY_SAMPLE environment variable enables delayed sampling for general overlap decode, allowing sampling overhead to overlap with model execution.
— Names env var and mechanism but no benchmark numbers.v0.5.18
05
All-to-all optimization for TP LMHeadIMPROVED66how completely this was documenteddepth30/40specificity26/30actionability10/3066 / 100
Replaces allgather + scatter in TP LMHead with a single all-to-all for pure-DP dp-attention, reducing LMHead time from 320us to 169us on DeepSeek-V4-Pro B200.
— Exact before/after latency numbers and hardware target given.v0.5.18
06
New GPU kernels for quantization and MoE servingNEW60how completely this was documenteddepth20/40specificity28/30actionability12/3060 / 100
Adds FlashInfer CuTe DSL NVFP4 MoE quantization support, FlashInfer mHC fusion for DeepSeek-V4 (now enabled by default), SM12x FA4 architecture-owned kernels, and a Triton MoE TMA up kernel.
— Names four distinct kernels but gives no benchmark figures.v0.5.18
thinner coverage below
07
Support for seven new modelsNEW53how completely this was documenteddepth15/40specificity26/30actionability12/3053 / 100
Adds support for new models: Muse Glimmer (autoregressive multimodal), Intern-S2-Mobius (autoregressive), SANA-Video (diffusion), LingBot-Video-MoE (diffusion), LTX-2.5 (diffusion), Cosmos3 Edge & Distilled (diffusion), and LongCat-Image (diffusion).
— Names all seven models but gives no usage instructions.v0.5.18
08
Core dependency upgradesIMPROVED53how completely this was documenteddepth15/40specificity28/30actionability10/3053 / 100
Updates core dependencies: torch 2.13.0 with triton 3.7.1, flashinfer 0.6.17, CuTeDSL 4.6.2, DeepEP from sgl-deep-ep wheels, and sgl-kernel 0.4.6.post1.
— Exact versions listed but no behavioral changes described.v0.5.18
09
Speculative decoding improvements for DSpark and DFlashIMPROVED52how completely this was documenteddepth20/40specificity20/30actionability12/3052 / 100
SGLang now supports logprobs output with DSpark and DFlash speculative decoding, and adds MegaMoE support for DSpark under DP attention.
— Names both additions but no mechanism detail.v0.5.18
10
DiT residency policy controlNEW50how completely this was documenteddepth12/40specificity18/30actionability20/3050 / 100
Adds --dit-layerwise-residency-policy flag for strided DiT residency control in diffusion model serving.
— Names the flag but not its values or effect.v0.5.18
11
Native Qwen VL multimodal processing in Rust serverNEW45how completely this was documenteddepth15/40specificity18/30actionability12/3045 / 100
Adds native multimodal processing for Qwen VL in the Rust server via integrated sglang-mm.
— Names the integration but no configuration detail.v0.5.18
12
Removal of torchao quantization integrationBREAKING40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
The --torchao-config flag and its torchao integration have been removed from SGLang.
— States removal but gives no migration path.v0.5.18
13
Content-addressed JIT build cacheNEW38how completely this was documenteddepth15/40specificity15/30actionability8/3038 / 100
Adds a content-addressed JIT build cache generated from a custom ninja build system.
— Names the mechanism but no config surface or usage steps.v0.5.18
14
Tuned FP8 GEMM tile configsIMPROVED31how completely this was documenteddepth10/40specificity15/30actionability6/3031 / 100
Adds tuned Triton tile configs for channelwise FP8 GEMM.
— Names the target op but no numbers or how-to.v0.5.18
15
Extensible serve backend pluginsNEW26how completely this was documenteddepth10/40specificity8/30actionability8/3026 / 100
Adds extensible serve backend plugins for the CLI, allowing the serve backend to be extended via plugins.
— Bare mention with no plugin interface or example.v0.5.18
16
EPLB balancedness reporting modesNEW24how completely this was documenteddepth8/40specificity10/30actionability6/3024 / 100
Adds explicit EPLB balancedness reporting modes.
— Bare mention with no named modes or usage.v0.5.18
└──▷ BREAKING ON UPGRADE
!All kernel caches (Triton, FlashInfer, Inductor, DeepGEMM, CUDA driver) now live under SGLANG_CACHE_DIR; the first launch after upgrading will recompile all kernels once.
!The --torchao-config flag and its torchao integration have been removed.
llama.cpp v0.2.0 introduces stable semantic versioning alongside nightly builds, adds support for several new model architectures, ships a broad set of backend kernel optimizations across ARM, OpenCL, Vulkan, WebGPU, RPC and CUDA, and adds a handful of server and multimodal API surfaces.
└──▷ 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
Backend kernel optimizations across GPU/CPU targetsIMPROVED80how completely this was documenteddepth35/40specificity30/30actionability15/3080 / 100
Adds SME2 F32 GEMV kernel support via KleidiAI on ARM; ports a fused ssm_scan kernel (Mamba-2, d_state 128/256) to GPU via OpenCL; adds tiled transpose for 0<->2 permuted CONT on the Vulkan backend; adds mulmat support with overlapping src0/src1 (e.g. for MiniMax-01) on the WebGPU backend; adds RPC use_count population to enable operation fusion inside backends; adds CUDA switch points per hardware and quantisation type to tune the MVQ-to-MMQ decode crossover; optimises quantisation memory usage by evicting weights after processing each layer; and adds the GGML_OPENCL_A7X_LMHEAD_CPU environment variable to override automatic CPU offload of vocab-scale K-quant lm_head on Adreno A7X GPUs.
— Names every kernel/backend and one env var, but most are automatic.v0.2.0
02
Server API and configuration additionsIMPROVED65how completely this was documenteddepth20/40specificity25/30actionability20/3065 / 100
Adds the dedup-cache-models preset option to the server, makes the /metrics endpoint accessible during server sleep state, and makes models endpoints private when authentication is enabled on the server.
— Names config option and endpoint plus a security behavior change.v0.2.0
03
New model architecture supportNEW60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Enables tensor split support for LFM2 and LFM2MOE models, adds support for GraniteSWAForCausalLM and GraniteMoeSWAForCausalLM model architectures, and adds support for the DSpark architecture for LFM2 models.
— Names the architectures but gives no usage steps.v0.2.0
04
Multimodal subsystem additionsNEW60how completely this was documenteddepth15/40specificity25/30actionability20/3060 / 100
Adds the --mmproj-device argument to specify the device for multimodal projector inference, and adds the mtmd_bitmap_set_mergeable API to the multimodal subsystem.
— Names a runnable flag and an API but no usage example.v0.2.0
thinner coverage below
05
Stable semantic versioning schemeIMPROVED55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Agno's v3.0.0a3 alpha adds clearer database migration error handling, a CodeMode execution surface for agents and teams, media offloading to external storage, SuperGrok OAuth for xAI, and workflow registry integration with Studio.
└──▷ WHAT SHIPPED · 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
CodeMode for agents and teamsNEW60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Adds CodeMode for agents and teams, enabling result offloading via a result_store handle, along with kernel fixes and execution bounds.
— Names class and handle but lacks usage examplev3.0.0a3
thinner coverage below
02
MigrationRequiredError for stale schemasNEW55how completely this was documenteddepth25/40specificity15/30actionability15/3055 / 100
Adds MigrationRequiredError to surface stale database schema errors with an actionable migration path instead of a silent table failure.
— Names the exception class but no migration steps shownv3.0.0a3
03
Media offloading to external storageNEW40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Adds media offloading from the database to local, S3, or GCS storage backends.
— Lists backends but no config keys or flags givenv3.0.0a3
04
SuperGrok OAuth for xAI modelNEW40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Adds SuperGrok OAuth device-code authentication for the xAI model.
— Names auth flow and model but no setup stepsv3.0.0a3
05
LearningMachine as sole Studio memory surfaceIMPROVED40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
Makes LearningMachine the sole Studio memory surface, consolidating memory management.
— Names the class but no migration or usage detailv3.0.0a3
06
Workflow registry and Studio integrationNEW35how completely this was documenteddepth15/40specificity10/30actionability10/3035 / 100
Adds a workflow registry and zero-config Studio integration for workflows.
— Describes feature broadly without config or endpoint namesv3.0.0a3
DSPy: The framework for programming—not prompting—language models
DSPy 3.3.1 ships a managed Deno runtime for PythonInterpreter, multi-proposal GEPA optimization with objective-aware frontier tracking, and structured MCP tool results, alongside expanded callback lifecycle visibility, sandbox hardening, and breaking changes to media timeouts and the CodeAct/ProgramOfThought modules.
└──▷ WHAT SHIPPED · 11 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. 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
Multi-proposal and objective-aware GEPA optimizationNEW88how completely this was documenteddepth32/40specificity28/30actionability28/3088 / 100
Supports GEPA 0.1.4's multi-proposal contracts via gepa_kwargs, accepting sampling_strategy, selection_strategy, and acceptance_criterion to enable concurrent candidate evaluation within the existing num_threads budget. Also adds objective-aware frontier tracking via gepa_kwargs, supporting objective_scores dimensions (quality, privacy, cost) for parent/merge selection while the scalar metric continues to gate acceptance.
Run GEPA optimization with four concurrent proposals, strict-improvement acceptance, and best-candidate selection — all within a fixed thread budget of 8.
— Runnable example with real strategy classes and thread budget.3.3.1
02
Managed Deno runtime for PythonInterpreterNEW83how completely this was documenteddepth28/40specificity25/30actionability30/3083 / 100
Adds the pip install 'dspy[deno]' optional extra to provide a managed Deno 2.x runtime for PythonInterpreter, pinning Pyodide and validating Deno >=2.0.0,<3.0.0 so a system Deno install is no longer required.
Install the managed Deno runtime so PythonInterpreter works without a system Deno install.
$ pip install "dspy[deno]"
— Exact install command and version constraints given.3.3.1
03
Structured results and SDK v2 support in MCP bridgeNEW83how completely this was documenteddepth30/40specificity28/30actionability25/3083 / 100
Adds result_mode='structured' to dspy.Tool.from_mcp_tool(), returning structuredContent from MCP SDK v2 servers (arrays, scalars, empty values, and explicit JSON null) with fallback to the existing content conversion. The MCP bridge also now supports MCP SDK v2 field names, v1 ClientSession, and v2 high-level Client, without changing default tool-result semantics.
Return machine-readable structured content from an MCP tool call instead of the default text conversion.
— Names the parameter, return field, and SDK versions supported.3.3.1
04
Default timeouts for Image and Audio URL loadingBREAKING70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Adds a timeout parameter to Image.from_url() and Audio.from_url(), defaulting to 30 seconds; pass timeout=None to restore the previous unbounded behavior. Code relying on unbounded download time must now pass timeout=None explicitly.
— Exact default value and migration flag given.3.3.1
05
PythonInterpreter sandbox isolation hardeningIMPROVED62how completely this was documenteddepth30/40specificity22/30actionability10/3062 / 100
Strengthens PythonInterpreter sandbox isolation: request IDs are now unpredictable, recursive execution through host tools is rejected, Deno-cache access is revoked after startup, and guest code cannot mutate JavaScript globals or prototypes to change host-tool identity.
— Concrete mechanisms named but no user-facing action.3.3.1
06
Deprecation of CodeAct and ProgramOfThoughtDEPRECATED60how completely this was documenteddepth22/40specificity20/30actionability18/3060 / 100
dspy.CodeAct and dspy.ProgramOfThought now emit DeprecationWarning on construction and are scheduled for removal in DSPy 3.5; users should migrate to dspy.RLM.
— Names removal version and exact migration target.3.3.1
thinner coverage below
07
Callback lifecycle visibility for interpreter and optimizerIMPROVED59how completely this was documenteddepth25/40specificity22/30actionability12/3059 / 100
Exposes full PythonInterpreter lifecycle events through DSPy's callback API: interpreter execution start/end, sandbox-to-host tool-call start/end, and interpreter process startup/shutdown, with callback ancestry retained across modules. Optimizer compile() runs now get equivalent start/end callback coverage.
— Names the events but no code example of registering callbacks.3.3.1
08
Nested type support in XMLAdapterIMPROVED57how completely this was documenteddepth25/40specificity20/30actionability12/3057 / 100
XMLAdapter now formats and parses nested Pydantic models, typed dictionaries, lists, mappings, nullable fields, and unions as nested XML, while remaining backward-compatible with the previous JSON-inside-XML representation.
— Lists supported types but no example of usage or output.3.3.1
09
Execution instructions for RLM's Pyodide environmentNEW43how completely this was documenteddepth18/40specificity15/30actionability10/3043 / 100
Adds PythonInterpreter.execution_instructions to give RLM an accurate description of the Pyodide environment, including state persistence and unavailable native process capabilities.
— Names the attribute but not its content format or usage.3.3.1
10
CodeInterpreterError unified into DSPyError hierarchyIMPROVED43how completely this was documenteddepth18/40specificity15/30actionability10/3043 / 100
CodeInterpreterError is now also a DSPyError subclass while retaining RuntimeError compatibility, enabling unified catch blocks across interpreter and agent modules.
— Names the class change but no example catch block.3.3.1
11
Clear validation for GEPA max_reflection_costIMPROVED35how completely this was documenteddepth15/40specificity12/30actionability8/3035 / 100
max_reflection_cost in DSPy's GEPA adapter now raises clearly when set instead of silently providing an ineffective budget.
!dspy.CodeAct and dspy.ProgramOfThought now emit DeprecationWarning on construction and are scheduled for removal in DSPy 3.5; migrate to dspy.RLM.
!Image.from_url() and Audio.from_url() now default to a 30-second timeout instead of waiting indefinitely; code relying on unbounded download time must pass timeout=None explicitly.
Open-source AI orchestration framework for building context-engineered, production-ready LLM applications. Design modular pipelines and agent workflows with explicit control over retrieval, routing, memory, and generation.
Haystack's v3.1.0 release candidates add context compaction and exit_reason reporting to Agent, a new token-counting module, PDF link extraction, and a process-wide unsafe-deserialization override, alongside a run of breaking changes to pipeline snapshots, deserialization safety checks, retrievers, document stores, tool warm-up, and evaluator scoring.
└──▷ WHAT SHIPPED · 5 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Context compaction hook for AgentNEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Experimental CompactionHook and SlidingWindowCompactor in haystack.hooks.compaction, configurable via context_window, compact_at, and compact_to fractions, are wired into an Agent through hooks={'before_llm': [hook]}; a Compactor protocol allows custom compaction strategies to automatically trim long conversations before hitting the model's context limit.
Attach context compaction to an Agent so long conversations are automatically trimmed before each LLM call.
python
from haystack.components.agents import Agent
from haystack.components.generators.chat import OpenAIResponsesChatGenerator
from haystack.hooks.compaction import CompactionHook, SlidingWindowCompactor
hook = CompactionHook(
compactor=SlidingWindowCompactor(),
context_window=400_000,
compact_at=0.7,
compact_to=0.4,
)
agent = Agent(
chat_generator=OpenAIResponsesChatGenerator(model="gpt-5.4-nano"),
tools=[web_search],
hooks={"before_llm": [hook]},
)
Attach context compaction to an Agent so long conversations are automatically trimmed before hitting the model's context limit.
python
from haystack.components.agents import Agent
from haystack.components.generators.chat import OpenAIResponsesChatGenerator
from haystack.hooks.compaction import CompactionHook, SlidingWindowCompactor
hook = CompactionHook(
compactor=SlidingWindowCompactor(),
context_window=400_000,
compact_at=0.7,
compact_to=0.4,
)
agent = Agent(
chat_generator=OpenAIResponsesChatGenerator(model="gpt-5.4-nano"),
tools=[web_search],
hooks={"before_llm": [hook]},
)
— Names hook, compactor, config params, and a wiring example.v3.1.0-rc3v3.1.0-rc2
02
Process-wide unsafe deserialization overrideNEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
New HAYSTACK_UNSAFE_DESERIALIZATION environment variable (truthy values 1 or true) skips all deserialization safety checks across Pipeline.load, Pipeline.loads, Pipeline.from_dict, Tool.from_dict, State.from_dict, ConditionalRouter, and OutputAdapter; it is read once on first deserialization and frozen for the process lifetime, intended for deployments loading only fully trusted pipelines.
Enable process-wide unsafe deserialization in a trusted deployment so every pipeline load skips safety checks without passing unsafe=True at each call site.
$ export HAYSTACK_UNSAFE_DESERIALIZATION=1
Enable unsafe deserialization process-wide when deploying with fully trusted pipelines and you cannot pass unsafe=True at every call site.
— Names the exact env var, scope, freeze behavior, and shell command.v3.1.0-rc3v3.1.0-rc2
03
Agent exit_reason and resolved_state_schemaBREAKING75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
Agent now returns exit_reason — 'text', 'max_agent_steps', or the name of the exit-condition tool — also readable in hooks via state.get('exit_reason'); the new agent.resolved_state_schema attribute exposes the full runtime state schema including internally managed keys (messages, step_count, token_usage, exit_reason). exit_reason is now reserved, so a custom state_schema containing that key raises ValueError at init, and Agent.state_schema itself now reflects only the user-provided schema rather than the full runtime one.
PDF link extraction via link_formatNEW70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
link_format parameter added to PyPDFToDocument and PDFMinerToDocument, parsing links from PDF annotations and appending them at the bottom of each page's content.
— Names the parameter and components but gives no code example.v3.1.0-rc3v3.1.0-rc2
05
Toolset warm_up runs on every callBREAKING70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Toolset._is_warmed_up internal flag is removed; warm_up() is now called before every run rather than only the first, so custom Tool or Toolset implementations doing expensive setup must add their own early-return guard.
!exit_reason is now a reserved key on Agent.state_schema; initializing an Agent with a custom state_schema containing exit_reason raises ValueError.
!Agent.state_schema now contains only the user-provided schema as passed to __init__; code that read agent.state_schema to inspect the full runtime schema must switch to agent.resolved_state_schema.
!PipelineSnapshot.pipeline_state.inputs (and BreakpointException.inputs) changed shape from {component: {socket: value}} to {component: {socket: [{"sender": ..., "value": ...}]}}; code reading these fields directly must index with [0]["value"]. A new inputs_format field records which shape a snapshot uses.
!Loading a serialized OutputAdapter or ConditionalRouter with unsafe: true in its init parameters now raises DeserializationError unless the pipeline is loaded with Pipeline.load(..., unsafe=True) (or the equivalent Pipeline.loads / Pipeline.from_dict option).
!SentenceWindowRetriever.run and SentenceWindowRetriever.run_async now raise ValueError when window_size=0 is passed at runtime; callers relying on 0 to mean 'use the constructor value' must omit the argument or pass None instead.
!InMemoryDocumentStore.get_metadata_field_unique_values (and its async counterpart) search_term parameter now matches against the metadata field value (case-insensitive substring) instead of document content.
!Toolset._is_warmed_up internal flag is removed; warm_up() is now called before every run rather than only the first, so custom Tool or Toolset implementations that do expensive setup there must add their own early-return guard.
!DocumentMAPEvaluator scores may change because average precision now uses all unique, valid ground-truth comparison values as its denominator and credits each value at most once; existing evaluation baselines should be recalculated.
!Serialized OutputAdapter and ConditionalRouter components containing Jinja custom_filters must now be loaded with Pipeline.load(..., unsafe=True) (or Pipeline.loads / Pipeline.from_dict with unsafe=True).
!exit_reason is now a reserved state key on Agent; if your state_schema defines a key named exit_reason, the Agent raises ValueError at initialization — rename the key.
!PipelineSnapshot.pipeline_state.inputs (and BreakpointException.inputs) changed shape from {component: {socket: value}} to {component: {socket: [{"sender": ..., "value": ...}]}}; code that reads these fields directly must be updated; inputs_format field records which shape a snapshot uses.
!Loading a serialized OutputAdapter or ConditionalRouter with unsafe: true in its init parameters now raises DeserializationError unless Pipeline.load, Pipeline.loads, or Pipeline.from_dict is called with unsafe=True.
!Serialized OutputAdapter and ConditionalRouter components containing Jinja custom_filters must now be loaded with Pipeline.load(..., unsafe=True) (or equivalent Pipeline.loads / Pipeline.from_dict option).
!Passing window_size=0 to SentenceWindowRetriever.run or SentenceWindowRetriever.run_async now raises ValueError instead of silently falling back to the constructor value; pass None or omit the argument to use the constructor's window_size.
!InMemoryDocumentStore.get_metadata_field_unique_valuessearch_term parameter now matches against the metadata field value (case-insensitive substring) instead of document content; callers relying on content-matching must pre-filter documents themselves.
!The Toolset internal _is_warmed_up flag is removed; warm_up() is now called before every Agent run, so custom Tool or Toolset implementations doing expensive setup must guard with their own state (e.g. if self._client is not None: return).
!DocumentMAPEvaluator scores may change because average precision now uses all unique, valid ground-truth comparison values as its denominator and credits each value at most once — re-baseline any evaluations that depended on previous scores.
Hermes overhauls its web search backend with a 5-vendor keyless ring, Tavily dual-auth, and rescue annotations, while also giving the agent direct control over a browser preview and refreshing the desktop app's update flow and theming.
└──▷ WHAT SHIPPED · 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Keyless web ring failover and keyed rescue annotationsNEW84how completely this was documenteddepth32/40specificity30/30actionability22/3084 / 100
The keyless web tier now round-robins across a 5-vendor ring (Exa, Parallel, Tavily, Firecrawl, Keenable) with automatic failover to the next vendor on rate-limit-shaped errors, marking the actual serving vendor with a served_by field. Tavily supports keyed/keyless dual auth via X-Tavily-Access-Mode: keyless and X-Client-Name: hermes-agent headers in plugins/web/keyless_mcp.py, and keyed web rescue now annotates results with rescued_from and backend_error fields naming the original failure and retry semantics.
— Names vendors, headers, file path and result fields precisely.v2026.8.19
02
Agent-driven browser preview and act engine updatesNEW68how completely this was documenteddepth28/40specificity22/30actionability18/3068 / 100
New drive_preview and annotate_preview agent tools let the agent interact with and annotate a browser preview page it has opened, with the desktop preview overlay now showing a real-time display of the agent's actions driven by real input rather than synthetic events. The desktop act engine also replaces full-page snapshots with durable element handles and delta-only page updates.
— Names the tools and mechanism change but no usage example.v2026.8.19
03
`hermes version` consolidated into `hermes --version`BREAKING63how completely this was documenteddepth15/40specificity20/30actionability28/3063 / 100
The hermes version subcommand is removed; users must now use hermes --version instead to check the installed version.
— Exact old and new command given, nothing more to explain.v2026.8.19
thinner coverage below
04
GitHub-style desktop themes and glass effectsNEW48how completely this was documenteddepth18/40specificity18/30actionability12/3048 / 100
Desktop ships GitHub themes with Nous blue as the default, an accent picker plugin (off by default), and glass effects tuned per appearance and platform.
— Names theme details but no navigation path given.v2026.8.19
05
Unified desktop update flowIMPROVED42how completely this was documenteddepth18/40specificity12/30actionability12/3042 / 100
The desktop update flow now updates every target — remote backends, other gateways, and the app itself — in a single operation.
— States the scope but no mechanism or UI path.v2026.8.19
06
Deduplicated agent tool re-calls in contextIMPROVED40how completely this was documenteddepth20/40specificity12/30actionability8/3040 / 100
Identical agent tool re-calls are now deduplicated into reference stubs in context rather than duplicate payloads, reducing token consumption.
— Explains mechanism briefly but no numbers or config.v2026.8.19
└──▷ BREAKING ON UPGRADE
!The hermes version subcommand is removed; use hermes --version instead.
Local-first AI agents with governed, approval-gated memory. Any model provider; MCP tools and web search built in.
Exxperts shipped self-contained, signed desktop and server distributions across three releases (v0.8.0–v0.10.0) that bundle a vendored Node runtime so the tool runs without Node, npm, or Git installed, plus checksum verification and stable download aliases for the release archives.
└──▷ 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
Signed, self-contained desktop app buildsNEW79how completely this was documenteddepth30/40specificity29/30actionability20/3079 / 100
Ships a signed desktop app (window + tray) for Windows and macOS that bundles a vendored Node runtime so no Node, npm, or Git is required on the target machine. macOS builds are Apple-notarized and Windows binaries are publisher-signed by Exxeta AG, eliminating unknown-publisher prompts on first launch; latest artifacts are exxperts-setup-0.10.0.exe, exxperts-desktop-0.10.0-win-x64.zip, and exxperts-desktop-0.10.0-mac-arm64.dmg.
— Exact signed filenames and signing/notarization behavior given, no install commandv0.10.0v0.9.0v0.8.0
02
Self-contained server-mode archivesNEW78how completely this was documenteddepth28/40specificity28/30actionability22/3078 / 100
Publishes standalone archives exposing the exxperts terminal command for Windows, macOS, and Linux, each bundling a vendored Node runtime so no local toolchain is needed for terminal use or one-line installers. Latest artifacts are exxperts-0.10.0-win-x64.zip, exxperts-0.10.0-darwin-arm64.tar.gz, and exxperts-0.10.0-linux-x64.tar.gz.
— Named archives and command given but no run instructions beyond downloadv0.10.0v0.9.0v0.8.0
03
Release checksums and versionless download aliasesNEW74how completely this was documenteddepth22/40specificity26/30actionability26/3074 / 100
Every release publishes SHA256SUMS.txt with CI-computed checksums for all archives, verifiable via shasum -a 256 --ignore-missing -c SHA256SUMS.txt (or Get-FileHash on Windows PowerShell). v0.9.0 added versionless asset 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.
— Exact filenames and verification command given, fully runnablev0.9.0v0.10.0v0.8.0
OpenWorker added four new model providers — AWS Bedrock, Google Vertex AI, OpenRouter, and Meta's Model API — alongside session-history auto-compaction, cross-provider token-usage metering, Anthropic extended thinking enabled by default, and mid-session model switching.
└──▷ WHAT SHIPPED · 17 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
AWS Bedrock provider with per-family dispatchNEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Adds an AWS Bedrock provider with per-family model dispatch: Claude models route through the native AnthropicBedrock client, while all other families (Llama, Nova, Mistral, Cohere, DeepSeek, and others) use the Converse API (bedrock-runtime.converse / converse_stream). Authentication is selectable via api_key (bearer token read from AWS_BEARER_TOKEN_BEDROCK), profile (named ~/.aws profile or default credential chain), or iam (explicit access keys plus optional STS session token).
Connect to AWS Bedrock using a console-issued API key (no AWS CLI required) and run a task on a Bedrock-hosted model.
$ # In Settings, add a Bedrock provider entry, set auth_method to api_key,
# and paste your bearer token. Model IDs follow the pattern:
# bedrock:claude/<bedrock-model-id> — native Anthropic path
# bedrock:other/<bedrock-model-id> — Converse API path
#
# The bearer token is picked up via AWS_BEARER_TOKEN_BEDROCK;
# you can also set it in the environment before launching OpenWorker:
export AWS_BEARER_TOKEN_BEDROCK=<your-bedrock-api-key>
— Names client, API, auth methods, and env var precisely.v0.1.7
02
Auto-compaction of long session historiesNEW86how completely this was documenteddepth38/40specificity28/30actionability20/3086 / 100
Introduces auto-compaction of long session histories (coworker/compaction.py): when outbound history approaches the model context limit, computed as min(threshold_pct × context_window, cap_tokens) with defaults DEFAULT_THRESHOLD_PCT = 0.8 and DEFAULT_CAP_TOKENS = 250_000, older turns are replaced with an LLM-written structured summary while the persisted transcript is never modified. Thresholds are configurable via Settings overrides.
— Full trigger formula and defaults, but exact settings key unnamed.v0.1.7
03
Extended thinking enabled by default, settings field removedBREAKING75how completely this was documenteddepth30/40specificity25/30actionability20/3075 / 100
Anthropic extended thinking is now enabled by default via a thinking_budget field, defaulting to 8192 tokens; set it to 0 to disable. The user-facing thinking_budget settings field has been removed and now survives only as a hidden provider-profile override.
— Names field, default value, and disable value; removal noted.v0.1.6
04
Mid-session model switchingNEW75how completely this was documenteddepth25/40specificity25/30actionability25/3075 / 100
Adds mid-session model switching via engine.switch_model(model), which persists a transcript marker and warns when the new model cannot see earlier images in history.
— Exact method name and behavior, minor mechanism detail.v0.1.6
05
Interpreters removed from auto-run allowlistBREAKING70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Interpreters and package managers (python, python3, node, npm, npx) have been removed from the default shell auto-run allowlist; workflows that relied on auto-approving these commands must now explicitly allowlist them.
— Names exact commands removed and required migration action.v0.1.7
06
Cross-provider token usage meteringNEW60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
Meters normalized token usage (input, output, cache reads, cache writes) across all model providers and surfaces it in the composer as a chip with a per-session popover breaking down totals per model, including an 'Uncached input' row and a cumulative 'Total input' row when prompt caching is active.
Review per-session token usage, including cache hits, after a long Anthropic session where prompt caching is active.
📍In the composer, click the token-usage chip to open the popover. Rows show session totals per model: 'Uncached input', cached reads, cache writes, output, and a cumulative 'Total input' row when a cache split exists.
— Clear UI location to inspect usage, no export or API surface.v0.1.7
thinner coverage below
07
Google Vertex AI provider with per-family dispatchNEW59how completely this was documenteddepth25/40specificity22/30actionability12/3059 / 100
Adds a Google Vertex AI provider with per-family dispatch: Gemini and Claude models use their native paths, while open-weight models route through the MaaS endpoint. Authentication supports Google Cloud ADC, a service account, or an API key.
— Describes dispatch and auth but no config keys or commands.v0.1.7
08
WorkspaceTrustStore gating MCP configNEW55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Adds WorkspaceTrustStore gating workspace MCP config, with global MCP config winning over a trusted workspace's config on name clash.
— Names the store and clash rule, no CLI or config key given.v0.1.7
09
Gemini 3 models with thought_signature supportNEW53how completely this was documenteddepth25/40specificity20/30actionability8/3053 / 100
Adds Gemini 3 models with thought_signature support, replaying signatures on tool-result turns so multi-turn tool loops remain coherent.
— Explains signature-replay mechanism but no config surface.v0.1.6
10
Grep tool excludes generated directoriesIMPROVED52how completely this was documenteddepth22/40specificity20/30actionability10/3052 / 100
The ripgrep-backed grep tool now explicitly excludes generated directories (node_modules, dist, and similar) regardless of .gitignore presence, with these exclusions applied after any caller-provided globs.
— Names exact directories and ordering but no flag to toggle.v0.1.7
11
Session transcript persistence improvementsIMPROVED48how completely this was documenteddepth20/40specificity18/30actionability10/3048 / 100
Persists Always-allow tool grants with the session so they survive across turns; persists error and interrupt markers in history with a Retry action surfaced on failed turns; and keeps interrupted partial streams in the transcript rather than discarding them.
— Lists three persistence behaviors, no config keys.v0.1.6
12
Live reasoning trace displayNEW46how completely this was documenteddepth20/40specificity18/30actionability8/3046 / 100
Shows live reasoning traces — a streaming Thinking block during generation and a persisted disclosure in the transcript — for both Anthropic and Gemini thinking-capable models.
— Describes UI behavior but no toggle or config.v0.1.6
13
Anthropic prompt caching via ephemeral breakpointsNEW45how completely this was documenteddepth20/40specificity20/30actionability5/3045 / 100
Enables Anthropic prompt caching via two ephemeral breakpoints per request: the last system block and the final message block.
— Names exact breakpoints but no toggle or config.v0.1.7
14
New models added to matrix: Nemotron, Kimi K3, Kimi K2.7 CodeNEW43how completely this was documenteddepth15/40specificity20/30actionability8/3043 / 100
Adds Nemotron Super 3 120B to the Bedrock model matrix, Kimi K3 via Together (1M context window, vision), and Kimi K2.7 Code via Together.
— Lists model names and providers but no usage guidance.v0.1.6v0.1.7
15
Provider credentials form in SettingsIMPROVED42how completely this was documenteddepth15/40specificity12/30actionability15/3042 / 100
Settings gains a multi-field provider credentials form with a segmented per-method auth panel and an add-model family dropdown for the new cloud providers.
OpenRouter and Meta Model API providers addedNEW38how completely this was documenteddepth15/40specificity15/30actionability8/3038 / 100
Adds OpenRouter as an OpenAI-compatible reseller provider, and adds a Meta Model API provider featuring Muse Spark 1.1 with tool calling, vision, and streaming support.
— Names providers and one model but no setup detail.v0.1.7
17
Transcript message clampingIMPROVED26how completely this was documenteddepth10/40specificity8/30actionability8/3026 / 100
The transcript view now clamps long user messages with a more…/less… toggle.
!Interpreters and package managers (python, python3, node, npm, npx) have been removed from the default shell auto-run allowlist; workflows that relied on auto-approving these commands must now explicitly allowlist them.
!The user-facing thinking_budget settings field has been removed; extended thinking is now enabled by default (budget 8192) and the field survives only as a hidden provider-profile override.
LangSmith is a platform for debugging, testing, and monitoring LLM applications built with LangChain.
LangSmith replaced its legacy dataset-comparison SDK helpers with a new paginated experiment-runs API, added a thread-evaluator validation endpoint and OTEL-based trace metadata tagging, and switched self-hosted bulk export to zstd compression by default.
└──▷ 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
Paginated experiment comparison APIBREAKING90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 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, so code using those SDK methods must migrate to the new endpoint.
— Full endpoint named with explicit migration requirementsnapshot-20260822
02
Batched-run ingestion log format changeBREAKING60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
The batched-run ingestion log now emits run_verbs as a list of run_id and verbs objects instead of a map keyed by run UUID, which will break structured-log aggregators or pipelines that expected the previous map format.
— Names field and format change but no migration commandsnapshot-20260822
thinner coverage below
03
PEP 604 union types in code evaluatorsIMPROVED55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Code evaluator upload now accepts Python entrypoints annotated with PEP 604 union return types (e.g., -> dict | None).
!Legacy dataset comparison helpers are removed from the public OpenAPI spec and generated SDKs; code using those SDK methods must migrate to POST /v2/datasets/{dataset_id}/experiment-runs.
!The batched-run ingestion log now emits run_verbs as a list of run_id and verbs objects instead of a map keyed by run UUID, which will break structured-log aggregators or pipelines that expected the previous map format.
Arize Phoenix shipped a new retrieval relevance evaluator for RAG pipelines and enabled GraphQL mutations by default in PXI's manual mode with user approval.
└──▷ 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.
thinner coverage below
01
Default GraphQL mutations in PXI manual modeIMPROVED40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
PXI (Phoenix Intelligence) now enables phoenix-gql mutations by default in manual mode, requiring user approval before execution.
Open-source observability tool that uses AI agents to self-heal your software
Superlog adds Google Cloud disconnect, GCP log filters, Sentry webhook routing, MCP timeout recovery, and PR overlap guards.
└──▷ GET THIS VERSION
$ git clone --branch commits-2026-07-23 https://github.com/superloglabs/superlog.git
# already have the repo? check out this version:$ git checkout commits-2026-07-23
└──▷ TRY IT
Disconnect a Google Cloud integration when rotating credentials or offboarding a GCP project.
›Adds POST /api/gcp/authorizations/{authorizationId}/disconnect endpoint to disconnect a Google Cloud integration.
›Adds GCP log group intake filters and bounded GCP log group discovery to control what gets ingested.
›Adds shared Sentry callback and webhook routing for Sentry alert ingestion.
›Adds guardProposedPullRequestOverlap and overlappingFilesForPullRequestClaim to block conflicting agent pull request deliveries when changed files overlap.
›Adds changedFilesFromAgentRunResult and changedFilesFromUnifiedDiff utilities to extract file-level change sets from agent runs and diffs.
+10 moreshow less
›Adds resolvePullRequestTargetBaseBranch for improved PR base-branch resolution during delivery.
›Adds a materialized SuperlogProjectId column and dedicated set index to ClickHouse logs and traces tables, routing log and trace queries through the materialized column for indexable multi-tenant scans.
›Wraps query_logs, query_traces, query_metrics, and list_services MCP tools with timeout recovery, converting ClickHouse timeouts into retry_required results that narrow the query to a one-hour window.
›Captures ad-network click IDs (twclid, gclid, fbclid, msclkid, li_fat_id) from signup URLs into a short-lived first-party cookie (sl_click_ids, 30 min) for server-side attribution.
›Shows quota reset date in the billing usage view.
›Fits three incidents in the active-incidents home widget with an animated scroll shadow.
›Acknowledges Vercel quota drops as a recognized signal.
›Preserves alert-to-incident correlation across queued intake.
›Allows configured Portless web hosts.
›Adds org_name to the first_telemetry_received analytics event.
Braintrust is an open-source evals framework for testing and monitoring AI applications with custom test cases and metrics.
Braintrust's biggest change this window is write access for its MCP server, letting coding agents create and update prompts, scorers, evals and other objects with the calling account's permissions; it also shipped two new built-in models, annotated version history, trace groups in dataset rows, a SQL sandbox sidebar, and several breaking changes to Go SDK span formats across Anthropic, Bedrock, Google GenAI and Eino integrations.
└──▷ WHAT SHIPPED · 11 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. 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
Eino span output format changesBREAKING90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
Go SDK v0.11.1 changes Eino ChatModel span output to an OpenAI-compatible choices array ([{"index": 0, "finish_reason": "...", "message": {...}}]) instead of a flat message map. Embedding input is now {"inputs": [{"content": "..."}]} and output is {"count": N}, removing embedding_length and renaming embeddings_count. Provider metadata is now lowercase (e.g. 'openai' instead of 'OpenAI'); trace queries relying on the previous formats need updating.
— Full before/after JSON shapes given for migrationsnapshot-20260822
02
Firebase Genkit tracing options in Go SDKNEW85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
Go SDK v0.11.1 adds WithProvider and WithModel options on NewMiddleware and traced tool wrappers DefineTool, DefineToolWithInputSchema, and DefineMultipartTool for Firebase Genkit; auto-instrumentation now replaces genkit.DefineTool, genkit.DefineToolWithInputSchema, and genkit.DefineMultipartTool calls with their traced equivalents.
— Names exact functions and describes auto-instrumentation swapsnapshot-20260822
03
New open-source models in Braintrust providerNEW68how completely this was documenteddepth20/40specificity28/30actionability20/3068 / 100
Adds kimi-k3 and deepseek-v4-flash-0731 as built-in open-source models available under the Braintrust provider in playgrounds, prompts, and scorers, or via the Braintrust Gateway — no AI provider setup required.
— Exact model ids and access surfaces named, no code samplesnapshot-20260822
04
Audio/video capture and streaming support for Bedrock Claude spansNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Go SDK v0.11.0 adds audio and video content block capture and full instrumentation for InvokeModelWithResponseStream for Anthropic Claude models in Bedrock Runtime spans.
— Names exact API method and content types instrumentedsnapshot-20260822
05
Anthropic span metadata format changesBREAKING65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Go SDK v0.11.0 removes endpoint from Anthropic span metadata, changes the output field to a single message object instead of an array, and stops emitting time_to_first_token for non-streaming spans.
— Exact fields changed named but no query migration examplesnapshot-20260822
06
Bedrock span metadata format changesBREAKING65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Go SDK v0.11.0 renames stop_sequences to stop in Bedrock span metadata, removes additional_model_request_fields, and aligns image, document, and tool block shapes with Bedrock's native wire format.
Collapsible query sidebar in SQL sandboxNEW63how completely this was documenteddepth25/40specificity20/30actionability18/3063 / 100
Adds a collapsible query sidebar to the SQL sandbox with search by name, drag-to-reorder, command-bar navigation, and a 'Copy share link' option that opens a query in a teammate's sandbox without running it.
— Concrete UI features named with clear starting pointsnapshot-20260822
08
TTL-specific prompt cache token capture for Anthropic spansNEW60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Go SDK v0.11.0 adds prompt_cache_creation_5m_tokens and prompt_cache_creation_1h_tokens capture for TTL-specific prompt caching on Anthropic spans.
Google GenAI provider metadata renamedBREAKING53how completely this was documenteddepth15/40specificity20/30actionability18/3053 / 100
Go SDK v0.11.1 changes Google GenAI provider metadata from 'gemini' to 'google'; trace queries that filter on the previous provider value need updating.
— Before/after values named but no migration scriptsnapshot-20260822
10
Async invoke method in Python SDKNEW48how completely this was documenteddepth10/40specificity20/30actionability18/3048 / 100
Adds invoke_async() as an async counterpart to the existing invoke() method in the Python SDK v0.32.0.
Enable Vercel AI SDK tracing in Python so every AI call is automatically captured in Braintrust.
python
from braintrust import auto_instrument
auto_instrument() # Vercel AI SDK for Python instrumentation is enabled by default
└──▷ BREAKING ON UPGRADE
!Python SDK v0.32.0: LiveKit Agents audio attachments on agent_speaking spans are now disabled by default. Set BRAINTRUST_CAPTURE_AGENT_AUDIO_ATTACHMENTS=true to restore the previous behavior.
!Go SDK v0.11.1 (Google GenAI): Provider metadata changed from 'gemini' to 'google'. Update trace queries that filter on the previous provider value.
!Go SDK v0.11.1 (Eino): ChatModel span output is now an OpenAI-compatible choices array ([{"index": 0, "finish_reason": "...", "message": {...}}]) instead of a flat message map. Embedding input is now {"inputs": [{"content": "..."}]} and output is {"count": N}, removing embedding_length and renaming embeddings_count. Provider metadata is now lowercase (e.g. 'openai' instead of 'OpenAI'). Update trace queries that rely on the previous formats.
!Go SDK v0.11.0 (Anthropic): Span metadata no longer includes endpoint. The output field is now a single message object instead of an array. Non-streaming spans no longer emit time_to_first_token.
!Go SDK v0.11.0 (Bedrock): Span metadata renames stop_sequences to stop and removes additional_model_request_fields. Image, document, and tool block shapes align with Bedrock's native wire format.
Self-evolving Context Database for AI Agents. Unify Agent Memory, Knowledge RAG and Skills.
OpenViking shipped a wave of agent-memory infrastructure across four releases: server-side recall context assembly (mode="context"), a new ov compile command for turning source directories into structured artifacts, OIDC/LDAP authentication, MCP write/edit/tree operations, and a declarative Assets Manifest for resource ingestion — alongside several breaking changes including removal of the Qdrant/openGauss backends, the embedded Python client classes, and the experimental Resource Relations API.
└──▷ WHAT SHIPPED · 40 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
`ov compile` command and Context Compilation workflowsNEW100how completely this was documenteddepth40/40specificity30/30actionability30/30100 / 100
New ov compile command compiles one or more viking:// source directories into structured artifacts using a Skill-driven isolated AgentLoop, committing results to a target Resource, Memory, or Skill namespace; accepts --from, --to, --skill, --reason, --wait, and --timeout flags. A new GET /bot/v1/compile/{task_id} endpoint lets callers poll async compile task status, distinguishing created, updated, and unchanged artifacts and reporting page count, link count, warnings, and OKF version. Context Compilation also gains source materialization, read-chain tracing, and reusable long-running-agent workflow support (LLM Wiki, knowledge graph, daily digest, knowledge distillation).
Compile scattered research notes into a browsable, searchable wiki — run without --wait first to get a Task ID, or add --wait to block until done.
— Full command flags, endpoint, and example runnable command.v0.4.16v0.4.12
02
Session Commit retention and auto-commit controlsIMPROVED100how completely this was documenteddepth40/40specificity30/30actionability30/30100 / 100
Sessions support setting default event-memory tags at creation time, updating them via the configuration interface, and overriding or clearing them per single commit; auto-commit policies can also be updated or disabled dynamically. The memory.session_auto_commit server-side config controls default enablement and idle scheduler for Session Auto Commit v2, which supports a per-session auto_commit_policy triggered by pending token count, message count, idle time, recent-message retention count, and minimum commit interval. A new turn_budget retention mode for the Session Commit API (POST /api/v1/sessions/{id}/commit) preserves complete user turns rather than fixed message counts, controlled via retention_mode, keep_recent_turn_count, retained_message_token_budget, and min_raw_tail_steps fields.
Enable auto-commit for a session by setting a token-count threshold and idle timeout at the server level.
Retain the last two full conversation turns (bounded by 12,000 tokens) when committing a session, so long sessions stay within context limits without losing mid-turn coherence.
— Exact endpoint, config keys, fields, and two runnable examples.v0.4.14v0.4.13v0.4.12
03
Async task management for resource import and long-running operationsNEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
wait=falseadd-resource source-data preparation now runs in a persistent background task chain, reducing request latency while preserving task ownership and reliability, and resource upload tasks expose context count and queued-upload-stage statistics for observability. New ov task cancel <task_id> command and Python SDK client.cancel_task("uuid-xxx") enable cooperative cancellation of add_resource, session_commit, admin_reindex, and snapshot_restore_reindex tasks, with status transitioning from cancelling to cancelled and idempotent repeat calls.
Import a large resource asynchronously in the background to avoid blocking the caller, then monitor task progress via the task stats that now include context count and queued-upload stage.
$ ov add-resource --wait=false viking://~/datasets/corpus.zip
— Names exact command, SDK call, task types, and state transitions.v0.4.16v0.4.12
04
DSH Memory Plugin for DeepSeek HarnessNEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
New @openviking/dsh-memory-plugin for DeepSeek Harness adds automatic recall, Session capture, retryable-write replay, viking:// path protection, and model-callable tools (viking_search, viking_read, viking_browse, viking_remember, viking_add_resource, viking_forget); pinned to @deepseek-ai/dsh0.1.0-rc.6 and Node.js ^22.19.0 or >=24. DSH plugin environment variables OPENVIKING_WORKSPACE_PEER=1 and OPENVIKING_RECALL_PEER_SCOPE=actor control workspace-scoped actor peer derivation and recall restriction. DSH tools are now also served over the shared stdio MCP Proxy.
Install the DSH memory plugin so every DeepSeek Harness session automatically captures context and recalls workspace memories before each agent step.
DeerFlow MemoryManager integrationNEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
DeerFlow integration adds MemoryManager (automatic write, recall, and context injection) configurable via memory block in config.yaml with keys manager_class, mode, startup_policy, failure_policy.read, and failure_policy.write; MCP access is configured in extensions_config.json under mcpServers.openviking.
Wire DeerFlow to OpenViking so conversations are automatically written and recalled; also expose MCP tools for agent-invoked search and editing.
— Exact config keys and file names, with runnable YAML example.v0.4.14
06
Server-side recall context assembly (`mode="context"`)NEW95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Adds mode="context" to the /search endpoint for server-side recall context assembly — executes recall planning, quota allocation, token budgeting, detail-tier downgrade, cross-turn deduplication, and optional LLM digest, returning context blocks ready to inject into a model; existing mode="list" remains the default. The endpoint returns HTTP 400 when target_uri is supplied in context mode, and the level parameter is replaced by the detail tier.
Retrieve model-ready context blocks server-side without client-side assembly, for a RAG pipeline that needs token-budgeted, deduplicated context.
$ curl -X POST https://<host>/search \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer <token>' \
-d '{"query": "How does the payment flow work?", "mode": "context", "detail": "full"}'
— Exact endpoint, parameters, error behavior, and runnable example.v0.4.13
07
Per-user memory policy admin endpointsNEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds GET and PATCH /api/v1/admin/accounts/{account_id}/users/{user_id}/settings endpoints to read and update per-user memory_policy, controlling which Memory types can be extracted; setting memory_policy to null clears the override and restores the inherited default.
Restrict a specific user to only certain Memory extraction types, then clear the override to fall back to the server default.
$ # Set a memory policy for a user
curl -X PATCH https://<host>/api/v1/admin/accounts/<account_id>/users/<user_id>/settings \
-H 'Content-Type: application/json' \
-d '{"memory_policy": {"allowed_types": ["episodic"]}}'
# Clear the override and restore inherited default
curl -X PATCH https://<host>/api/v1/admin/accounts/<account_id>/users/<user_id>/settings \
-H 'Content-Type: application/json' \
-d '{"memory_policy": null}'
— Names exact endpoint, method, and field; example included.v0.4.16
08
MCP `tree`, `write`, and `edit` operationsNEW90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
MCP gains tree, write, and edit operations against viking:// workspaces; write supports create, replace, and append modes; edit performs exact string replacement and leaves the file unchanged when a match is missing or ambiguous; wait=true blocks until semantic and vector indexes are refreshed; viking://user/... addresses the authenticated user's own workspace.
— Full behavior and modes named, but no runnable example given.v0.4.14
09
Assets Manifest for declarative resource ingestionNEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
New ov add-resource --manifest <manifest.yaml> command supports the openviking-assets/1 YAML manifest protocol for declarative, version-controllable asset catalog management, with --args dry_run:true preflight and --wait --timeout flags; state is persisted to <manifest>.state.json.
Validate a new asset manifest (credentials, Git access, sync plan) before committing any changes to disk or creating Resources.
$ ov add-resource --manifest manifest.yaml --args dry_run:true
— Exact command, flags, protocol name, and runnable example.v0.4.12
10
New agent harness integrations: agent-plugins, OpenCode, ZCode, OpenClaw, TRAENEW85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
New agent-plugins/ package provides a portable Agent Plugins 1.0 bundle with a zero-runtime-dependency stdio-to-HTTP MCP proxy and openviking-memory Skill for clients that conform to Agent Plugins 1.0 but lack dedicated hooks. OpenCode gains a hooks-only memory mode. ZCode Memory Plugin adds session capture, auto recall, MCP proxy, and shared pending queue. The OpenClaw plugin adds Experience Memory tools and skills for querying, reading, and using experience memory stored in OpenViking. A TRAE/TRAE CN Hooks + MCP install script also enables automatic recall, per-turn session capture, and short-session commits.
Install the TRAE/TRAE CN Hooks + MCP integration for automatic recall, per-turn session capture, and short-session commits.
— Names each integration and its capability, plus one install example.v0.4.14v0.4.13
11
OIDC and LDAP authentication modesNEW85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
Adds OIDC and LDAP authentication modes supporting Okta, Auth0, Keycloak, Azure AD, Windows AD, and OpenLDAP, with claim/attribute mapping to account, user, and role; installable via uv pip install 'openviking[auth]'; CLI gains LDAP credential support.
— Names providers, install command, and mapping mechanism.v0.4.13
12
Resource import processing controlsNEW85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
Adds args.parse_mode=no_split to resource import so PDF, Word, PowerPoint, and HTML sources are parsed and converted to Markdown but kept as a single body without splitting by heading, paragraph, or length. Adds processing_mode to resource import and content write: semantic_and_vectors (default) regenerates .abstract.md, .overview.md, and vectors; vectors_only skips VLM semantic understanding and only vectorizes the current file, preserving existing semantic artifacts; supported in the Python SDK, TypeScript SDK, CLI, and HTTP API.
— Names exact parameters, modes, and supported surfaces.v0.4.13
13
`ov snapshot diff` commandNEW85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
New ov snapshot diff <path> --from <ref> --to <ref> command produces a Unified Diff for UTF-8 text files between two commit references, returning added, deleted, modified, or unchanged; also available via Python SDK client.snapshot.diff(path, from_ref=..., to_ref=...) and HTTP API. Per-side limit is 10 MiB / 100,000 lines, diff limit is 20 MiB.
— Exact command, SDK call, and size limits, but no worked example given.v0.4.12
14
Resource Relations API and CLI removedBREAKING80how completely this was documenteddepth25/40specificity30/30actionability25/3080 / 100
The experimental Resource Relations REST API (/api/v1/relations), CLI commands (ov relations, ov link, ov unlink), and associated documentation have been removed. Any integrations using these must be deleted or replaced before upgrading.
— Names exact endpoint and CLI commands removed, with migration note.v0.4.16
15
LangChain integration package and capabilitiesNEW80how completely this was documenteddepth30/40specificity30/30actionability20/3080 / 100
Adds langchain-openviking as a standalone package providing Retriever, Tools, Message History, Context Wrapper, Store, and Middleware; the original openviking.integrations.langchain import path is retained as a compatibility shim, and the forced LangChain client dependency was removed from the main openviking server package, reducing image size and dependency surface. The LangChain/LangGraph integration also adds native async calls and request-level Actor Peer support.
— Package name and components listed but no install/usage example.v0.4.13v0.4.12
16
New server tuning config keysNEW80how completely this was documenteddepth25/40specificity30/30actionability25/3080 / 100
Adds queue_workers.external_parse.max_concurrent to set ExternalParse worker concurrency (default 4, takes effect after restart); enable_watch_scheduler to let read-only replicas skip redundant resource refresh sweeps (default true); and server.timeout_keep_alive to set the HTTP idle keep-alive timeout (default 5 seconds).
— Names all three config keys with defaults and effect.v0.4.13
17
Agent Evolution disabled by defaultBREAKING80how completely this was documenteddepth25/40specificity30/30actionability25/3080 / 100
HTTP Server server.agent_evolution.enabled now defaults to false; deployments relying on automatic Case, Trajectory, and Experience generation after Session Commit must explicitly set {"server": {"agent_evolution": {"enabled": true}}} in ov.conf to restore the previous behavior.
— Exact config key, default change, and restoration snippet.v0.4.12
18
MinerU endpoint config changesBREAKING75how completely this was documenteddepth25/40specificity30/30actionability20/3075 / 100
mineru_endpoint is now treated as a base URL and OpenViking calls POST {endpoint}/file_parse; mineru_params is renamed to mineru_bodys; mineru_api_key has been removed.
— Names exact config keys, endpoint call, and rename.v0.4.14
19
Redis backend for QueueFSNEW75how completely this was documenteddepth25/40specificity30/30actionability20/3075 / 100
Adds Redis backend for QueueFS (storage.agfs.queuefs) supporting standalone, Cluster, and Sentinel modes for multi-instance shared-queue deployments; existing SQLite QueueFS remains the default.
— Names config key and supported Redis modes, no example given.v0.4.13
20
Code outline/search/expand endpoints removedBREAKING75how completely this was documenteddepth25/40specificity30/30actionability20/3075 / 100
The /api/v1/code/outline, /api/v1/code/search, and /api/v1/code/expand endpoints and the MCP tools code_outline, code_search, and code_expand have been removed; callers must migrate to the Skeleton-first code summary and the generic read, grep, find, and search capabilities.
— Names all removed endpoints/tools and migration target.v0.4.12
21
`viking://~` URI shorthand for user rootNEW70how completely this was documenteddepth20/40specificity25/30actionability25/3070 / 100
Adds viking://~ URI alias that resolves to the authenticated caller's user root directory, usable anywhere a viking://user/... URI is accepted.
Reference the caller's own user root without hard-coding a user path, useful in scripts or agent configs that run as different identities.
$ ov add-resource viking://~/documents/report.pdf
— Concrete alias syntax and example, limited mechanism beyond resolution.v0.4.16
22
Agent Evolution experience tracking and aggregationIMPROVED70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
Experience trajectory list and outcome distribution endpoints accept inclusive UTC date range filters. Configuring experiences now automatically enables cases and trajectories; Agent Evolution derivative memories are generated only when extraction actually produces a case. Agent Evolution also gains experience trajectory lineage tracking, recording associations between experiences and their originating trajectories with corresponding API and vector metadata support, plus experience outcome aggregation and snapshot refinement that combines lineage and historical outcomes to produce more stable experience versions.
— Describes mechanism and config trigger but no named endpoint paths.v0.4.14v0.4.13
23
Embedded Python client classes removedBREAKING70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
The embedded Python client classes OpenViking, SyncOpenViking, AsyncOpenViking, and LocalClient are no longer exported; callers must run OpenViking as a separate service and connect via openviking-sdk.
— Names removed classes and migration path (`openviking-sdk`).v0.4.14
24
OpenClaw/ArkClaw `SecretRef` exec source removedBREAKING70how completely this was documenteddepth25/40specificity25/30actionability20/3070 / 100
Packed OpenClaw/ArkClaw marketplace plugins no longer support {source: 'exec'}SecretRef; {source: 'env'} and {source: 'file'} remain supported. Callers must switch to {source: 'env'} or {source: 'file'}, or inject secrets into the environment before launching OpenClaw.
— Names exact removed and supported SecretRef sources with migration path.v0.4.13
25
New resource connectors: TOS, private Git, Feishu/Lark DriveNEW65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
Adds new TOS resource connector arguments for the add-resource command. OpenViking Assets resource ingestion now accepts pinned 40-character Git commit SHAs, explicit to destination targets, and HTTPS private repository credentials; add_resource and Watch flows also support private Git authentication. Feishu/Lark ingestion now supports Drive files and recursive folder imports.
— Names connector targets and Git auth details but no example command.v0.4.16v0.4.14
26
Memory V2 extraction removedBREAKING60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
memory.version is now ignored and V2 extraction is no longer selectable; memory.v2_lock_retry_interval_seconds and memory.v2_lock_max_retries are no longer supported.
— Names exact config keys removed, no migration step given.v0.4.14
thinner coverage below
27
Web Studio Watch management and operational UINEW55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Web Studio adds complete Watch management (view, edit, pause, resume, trigger, and history flows) plus richer remote resource import options; request logs now display error details alongside Task API limit enforcement; and the Skills view is grouped by scope.
— Lists UI flows but no exact navigation paths or config keys.v0.4.16v0.4.14
28
`reindex` replace/append tag modesIMPROVED55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
reindex now accepts replace or append mode to update tags on successfully rebuilt records.
— Names exact modes but no command syntax shown.v0.4.14
29
Audio/video multimodal understanding backendNEW55how completely this was documenteddepth25/40specificity20/30actionability10/3055 / 100
Adds audio/video multimodal understanding backend based on Volcano Ark (火山方舟), supporting long media upload, async polling, result caching, timeout control, and audio/video summary templates.
— Describes capabilities but no config or API to invoke it.v0.4.13
30
VikingBot remote Skills discovery and executionNEW45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
VikingBot can now discover, cache, and execute Skills hosted on remote OpenViking instances.
— Describes mechanism briefly but no config or command shown.v0.4.16
31
Web Studio account deletion flowNEW45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
Web Studio adds an account deletion flow with immediate identity revocation and durable-queue data cleanup.
— Names mechanism (identity revocation, queue cleanup) but no API path.v0.4.14
32
MCP Streamable HTTP stateless modeIMPROVED45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
MCP Streamable HTTP switches to stateless mode, eliminating intermittent Session not found errors in multi-instance or load-balanced deployments.
— Explains fix and scenario but no config to enable.v0.4.14
33
VectorDB `text` field typeNEW45how completely this was documenteddepth15/40specificity20/30actionability10/3045 / 100
VectorDB gains a text field type for storing large strings that exceed ordinary string field limits.
— Names field type but no size limit or usage example.v0.4.13
34
RAGFS structured lock tracing logsIMPROVED45how completely this was documenteddepth20/40specificity15/30actionability10/3045 / 100
RAGFS gains structured lock tracing logs covering wait, contention, expiry, and release lifecycle for lock debugging.
— Describes log coverage but no log format or access path.v0.4.13
35
`find`/`search` results expose explicit tagsIMPROVED40how completely this was documenteddepth15/40specificity15/30actionability10/3040 / 100
find and search results now return explicit tags and omit empty optional fields.
— Names the field change but no example response.v0.4.13
36
CLI init wizard plan tiers and custom configNEW35how completely this was documenteddepth10/40specificity15/30actionability10/3035 / 100
Adds VolcEngine/BytePlus plan tiers and custom interactive configuration to the CLI init wizard.
— Thin one-line description, no flags or steps given.v0.4.16
37
Protected OKF metadata for L0/L1 semantic sidecarsIMPROVED35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
L0/L1 semantic sidecars are now managed as protected OKF metadata, with write-protection enforced.
— Describes change but no config or migration detail.v0.4.16
38
Qdrant and openGauss vector backends removedBREAKING35how completely this was documenteddepth10/40specificity20/30actionability5/3035 / 100
The Qdrant and openGauss vector backends have been removed.
— Names backends removed but no migration guidance.v0.4.14
39
VikingBot Chat API image inputNEW35how completely this was documenteddepth10/40specificity15/30actionability10/3035 / 100
VikingBot Chat API now accepts OpenAI-style image input.
— Bare statement, no format or endpoint detail.v0.4.12
40
SessionCommit worker concurrency default changeBREAKING30how completely this was documenteddepth10/40specificity15/30actionability5/3030 / 100
SessionCommit worker default concurrency changed from 4 to 8.
— States the numeric change only, no config key to adjust.v0.4.14
└──▷ BREAKING ON UPGRADE
!The experimental Resource Relations REST API (/api/v1/relations), CLI commands (ov relations, ov link, ov unlink), and associated documentation have been removed. Any integrations using these must be deleted or replaced before upgrading.
!The embedded Python client classes OpenViking, SyncOpenViking, AsyncOpenViking, and LocalClient are no longer exported; callers must run OpenViking as a separate service and connect via openviking-sdk.
!mineru_endpoint is now treated as a base URL and OpenViking calls POST {endpoint}/file_parse; mineru_params is renamed to mineru_bodys; mineru_api_key has been removed.
!memory.version is now ignored and V2 extraction is no longer selectable; memory.v2_lock_retry_interval_seconds and memory.v2_lock_max_retries are no longer supported.
!The Qdrant and openGauss vector backends have been removed.
!SessionCommit worker default concurrency changed from 4 to 8.
!Packed OpenClaw/ArkClaw marketplace plugins no longer execute SecretRef with {source: 'exec'}; switch to {source: 'env'}, {source: 'file'}, or inject secrets into the environment before launching OpenClaw.
!search(mode="context") returns HTTP 400 when target_uri is supplied; the level parameter is replaced by the detail tier in context mode.
!HTTP Server server.agent_evolution.enabled now defaults to false; deployments relying on automatic Case, Trajectory, and Experience generation after Session Commit must explicitly set {"server": {"agent_evolution": {"enabled": true}}} in ov.conf to restore the previous behavior.
!The /api/v1/code/outline, /api/v1/code/search, and /api/v1/code/expand endpoints and the MCP tools code_outline, code_search, and code_expand have been removed; callers must migrate to the Skeleton-first code summary and the generic read, grep, find, and search capabilities.
An open-source, ontology-based semantic context accelerator that enables AI agents to make more accurate, consistent, and explainable decisions.
Context Ontology Accelerator v0.2.0 and v0.2.1 add Redshift Serverless as an alternative query engine with its own SQL firewall and guardrail observability, deterministic IRI minting for ontology graphs, a new CloudWatch dashboard, and a breaking rename plus pagination of the list_metrics MCP tool.
└──▷ WHAT SHIPPED · 6 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Redshift Serverless as alternative query engineNEW90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
New executionEngine=REDSHIFT and redshiftWorkgroup onboarding parameters route Glue-backed sources through Amazon Redshift Serverless via the redshift-data API instead of Athena, with automatic Trino→Redshift SQL transpilation and awsdatacatalog."<db>"."<table>" reference rewriting.
— Names exact onboarding params and API path, mechanism of transpilation describedv0.2.0
02
Guardrail observability metrics in CloudWatchNEW85how completely this was documenteddepth35/40specificity30/30actionability20/3085 / 100
Adds guardrail observability under the COA/Guardrails CloudWatch namespace, emitting GuardrailInvocations (Count), GuardrailBlocked (Count), and GuardrailLatency (Milliseconds) metrics, supporting both transport="put" (PutMetricData, used by ECS Fargate kg-build/enrichment/ontology tasks) and Embedded Metric Format via CloudWatch Logs.
— Full namespace and metric names given, queryable directly in CloudWatchv0.2.0
03
Pagination and renamed parameters in list_metrics MCP toolBREAKING85how completely this was documenteddepth30/40specificity30/30actionability25/3085 / 100
Adds a nextToken pagination parameter to the list_metrics MCP tool, alongside renamed parameters namespaceId and maxResults (max 1000). This is a breaking change: the previous namespace_id and max_results keyword names will fail for existing callers.
Deterministic IRI minting for ontology graphsNEW70how completely this was documenteddepth30/40specificity30/30actionability10/3070 / 100
Introduces CatalogConstraint and parse_referred_column imports alongside deterministic IRI minting via table_identity and _name_discriminator (a SHA-256-derived 8-char suffix), enabling stable cross-run ontology graph generation.
— Internal mechanism named precisely but not user-invokablev0.2.0
05
SQL firewall and query limiting on Redshift pathNEW60how completely this was documenteddepth30/40specificity20/30actionability10/3060 / 100
Adds SQLFirewall.validate enforcement and dialect-aware LIMIT injection to the Redshift execution path, restricting queries to SELECT-only and preventing large scans from fully materializing.
— Names the validator and behavior but it's automatic, no user-facing controlv0.2.0
thinner coverage below
06
CloudWatch dashboard for scan and enrichment pipelineNEW35how completely this was documenteddepth15/40specificity15/30actionability5/3035 / 100
Adds a CloudWatch dashboard for the structured scan and enrichment pipeline, sourcing custom metrics from sources Lambdas via EMF-stdout.
— Names metric source but no dashboard location or metric names givenv0.2.1
└──▷ BREAKING ON UPGRADE
!The list_metrics MCP tool parameters namespace_id and max_results are renamed to namespaceId and maxResults; any caller passing these by keyword name will break.
Agentic Ontology Assisted Framework for Semantic Triple Extraction
OntoCast's v0.6.x window centers on a new LangChain/LangGraph tool integration and a redesigned triple-budget system that caps ontology context per prompt without dropping load-bearing schema, alongside a large set of breaking changes: JSON-LD becomes the default LLM wire format, the in-memory vector store backend is removed in favor of Qdrant/LanceDB, and several internal APIs, console scripts, and the provenance node data shape changed or were removed.
└──▷ 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
Ontology triple budget split into prompt cap and working-graph backstopBREAKING95how completely this was documenteddepth35/40specificity30/30actionability30/3095 / 100
Adds ONTOLOGY_CONTEXT_MAX_TRIPLES (default 4000) to bound ontology context size in every prompt mode (selected_single_ontology, fixed_single_ontology, and facts fan-out), enforced at format_ontology_chapter; when over budget, onto/ontology_condense.py drops triples in increasing order of harm (header/list noise first, redundant structure second, glosses third) and never drops labels, types, hierarchy, or domain/range. Correspondingly, ONTOLOGY_MAX_TRIPLES now defaults to unlimited (was 50000) and remains only as a runaway-growth backstop on the per-unit working graph; use ONTOLOGY_CONTEXT_MAX_TRIPLES to cap prompt size instead.
Cap how many triples reach the LLM prompt to stay within a provider's context window, without truncating load-bearing schema.
— Full mechanism, exact env vars, defaults, and a runnable commandv0.6.1
02
LangChain/LangGraph tool integration with diagnosticsNEW90how completely this was documenteddepth30/40specificity30/30actionability30/3090 / 100
Adds ontocast.integrations.langchain exposing ontocast_tools(tools), which returns a list of BaseTool objects any LangChain or LangGraph agent can call, with capability-gated tool inclusion and opt-in mutation via mutating=True. Adds ontocast_tool_diagnostics to explain which tools were omitted from the toolset and why, making missing-backend failures visible.
Wire OntoCast's ontology and retrieval capabilities into a LangChain agent, with write operations enabled.
Diagnose which OntoCast tools were excluded from the LangChain toolset due to missing backends.
python
from ontocast import Config, ToolBox
from ontocast.integrations.langchain import ontocast_tool_diagnostics
tools = await ToolBox.acreate(Config.in_memory())
await tools.initialize()
print(ontocast_tool_diagnostics(tools))
— Named module, function signatures, and two runnable code examplesv0.6.0
03
LLM_GRAPH_FORMAT defaults to JSON-LDBREAKING85how completely this was documenteddepth25/40specificity30/30actionability30/3085 / 100
Changes LLM_GRAPH_FORMAT default from Turtle to jsonld across ServerConfig, AgentState, UnitState, and the llm_graph_format_ctx ContextVar; Turtle remains available via explicit configuration. Deployments that never set the variable will switch wire format on upgrade unless LLM_GRAPH_FORMAT=turtle is set explicitly.
Keep Turtle as the LLM wire format for providers whose structured-output handling works better with plain strings than nested JSON-LD objects.
— Names every affected component plus an exact override commandv0.6.1
04
In-memory vector store backend removedBREAKING75how completely this was documenteddepth25/40specificity30/30actionability20/3075 / 100
Removes the in-memory vector store: VECTOR_STORE_BACKEND=memory, VectorStoreBackend.MEMORY, and tool/vector_store/in_memory.py are gone; retrieval now requires Qdrant or LanceDB, and Config.in_memory() is triple-store only (pyoxigraph).
— Names removed config values, files, and required replacementsv0.6.0
05
Shared graph-pruning moduleIMPROVED65how completely this was documenteddepth25/40specificity30/30actionability10/3065 / 100
Moves seed-free graph pruners and predicate vocabularies (NOISY_EXPANSION_PREDICATES, GENERIC_INDIVIDUAL_TYPES, MIN_MEANINGFUL_RESTRICTION_PREDICATES, OWL_RESTRICTION_MEANINGFUL_PREDICATES, bfs_triple_rank, count_meaningful_restriction_predicates, prune_degenerate_restriction_bnodes, prune_orphaned_bnode_subjects, remove_bnode_subgraph) into a new shared module onto/graph_prune.py, reusable by both induced-subgraph retrieval and the prompt condenser.
— Names every moved symbol but is an internal refactor with no user actionv0.6.1
06
Provenance metadata terms moved to shared constantBREAKING60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
Introduces ontocast.onto.constants.PROVENANCE_METADATA_TERMS, a module-level frozenset naming the classes and predicates the pipeline mints on provenance nodes, replacing the former class attribute TripleStoreManager._PROVENANCE_METADATA_PREDICATES.
— Exact old and new symbol names with import pathv0.6.0
07
AtomicToolBox and EmbeddingBasedAggregator take config objectsBREAKING60how completely this was documenteddepth20/40specificity25/30actionability15/3060 / 100
AtomicToolBox now takes WebSearchConfig and EmbeddingBasedAggregator now takes AggregationConfig; flat kwargs are removed from both constructors.
— Named classes and config objects but no migration examplev0.6.0
08
Provenance unit node retyped from property to classBREAKING60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
A provenance unit node is now typed schema:Text (a class) instead of schema:text (a property IRI); graphs already in a triple store keep the old type until re-extracted, and any query filtering on schema:text must be updated.
— Clear before/after typing with migration note for existing graphsv0.6.0
09
ontology_directory made strictly read-onlyBREAKING60how completely this was documenteddepth25/40specificity20/30actionability15/3060 / 100
ingest_ontology_ttl no longer requires or touches ontology_directory, and delete_ontology_by_iri no longer removes files from it; an ingested ontology now lives only in the triple store and vector index and does not survive a rebuild from seeds.
— Names both affected functions and the resulting persistence changev0.6.0
thinner coverage below
10
RENDER_MODE environment override for extract toolIMPROVED55how completely this was documenteddepth15/40specificity20/30actionability20/3055 / 100
The ontocast_extract LangChain/MCP tool now reads its render_mode default from the RENDER_MODE environment variable (via parse_render_mode_param) instead of hardcoding ontology_and_facts.
— Exact env var and default named, settable directlyv0.6.1
11
Internal API surface cleanup: dead modules, symbols, and state fields removedBREAKING55how completely this was documenteddepth20/40specificity30/30actionability5/3055 / 100
Removes dead modules onto/context.py, tool/graph_version_manager.py, and tool/graph_diff.py (~1,222 lines), and drops numerous previously import-visible symbols including route_after_convert, route_after_ontology_consolidation, WorkflowNode.AGGREGATE_FACTS, WorkflowNode.PARALLEL_MAP_UNITS, aggregate_anchor_metrics, URIPromoter, OntologyDecision, FactsDecision, CHUNK_NULL_IRI, render_ontology_rank_diagnostics, set_failure (which no longer takes success_score), graph_uri_override, and ToolBox._unlink_ttl_files_if_ontology_iri. Also drops AgentState fields including UnitState shadows, never-read writers, and graph_uri_override; graph_uri is now always doc_namespace.
— Enumerates every removed symbol but offers no migration pathv0.6.0
12
Retrieval metric for context-mode triple countsIMPROVED50how completely this was documenteddepth20/40specificity20/30actionability10/3050 / 100
Adds an ONTOLOGY_SNAPSHOT_TRIPLES retrieval metric, now written for every context mode; previously only the vector resolver recorded a size under patch_retrieval.
— Named metric but no way shown to consume itv0.6.1
13
Removed test-api and cmp-states console scriptsBREAKING50how completely this was documenteddepth15/40specificity25/30actionability10/3050 / 100
Removes the test-api console script and cli/test_api.py (and drops requests from the server extra), and removes the cmp-states console script and ontocast/cli/cmp_states.py.
— Names both removed scripts and their files/extrasv0.6.0
14
ExternalEvidenceCacheEntry replaces evidence mirrorsNEW30how completely this was documenteddepth10/40specificity15/30actionability5/3030 / 100
Introduces ExternalEvidenceCacheEntry as the supported replacement for UnitState external-evidence mirrors.
— Names the new type but gives no usage detailv0.6.0
15
First PyPI publication since v0.4.3NEW30how completely this was documenteddepth10/40specificity15/30actionability5/3030 / 100
v0.6.0 is the first release published to PyPI since v0.4.3; v0.5.0 and v0.5.1 were in-tree version bumps never tagged or published.
!LLM_GRAPH_FORMAT now defaults to jsonld; any deployment that never set this variable will switch wire format on upgrade. Set LLM_GRAPH_FORMAT=turtle explicitly to preserve the previous behaviour.
!ONTOLOGY_MAX_TRIPLES now defaults to unlimited (was 50000); workloads relying on the old cap to bound working-graph growth must set the variable explicitly.
!Removed in-memory vector store: VECTOR_STORE_BACKEND=memory, VectorStoreBackend.MEMORY, and tool/vector_store/in_memory.py are gone; retrieval now requires Qdrant or LanceDB. Config.in_memory() is triple-store only (pyoxigraph).
!AtomicToolBox now takes WebSearchConfig and EmbeddingBasedAggregator now takes AggregationConfig; flat kwargs are removed from both.
!Removed test-api console script and cli/test_api.py; requests is dropped from the server extra.
!Removed cmp-states console script and ontocast/cli/cmp_states.py.
!A provenance unit node is now typed schema:Text (the class) instead of schema:text (a property IRI); graphs already in a triple store keep the old type until re-extracted, and any query filtering on schema:text must be updated.
!TripleStoreManager._PROVENANCE_METADATA_PREDICATES is removed; use ontocast.onto.constants.PROVENANCE_METADATA_TERMS instead.
!Removed dead modules onto/context.py, tool/graph_version_manager.py, and tool/graph_diff.py (~1,222 lines).
!Removed numerous previously import-visible symbols including route_after_convert, route_after_ontology_consolidation, WorkflowNode.AGGREGATE_FACTS, WorkflowNode.PARALLEL_MAP_UNITS, aggregate_anchor_metrics, URIPromoter, OntologyDecision, FactsDecision, CHUNK_NULL_IRI, render_ontology_rank_diagnostics, set_failure (no longer takes success_score), graph_uri_override, ToolBox._unlink_ttl_files_if_ontology_iri, and others; anything importing them out-of-tree breaks.
!ontology_directory is now strictly read-only: ingest_ontology_ttl no longer requires or touches it, and delete_ontology_by_iri no longer removes files from it. An ingested ontology lives only in the triple store and vector index and does not survive a rebuild from seeds.
!Dropped AgentState fields including UnitState shadows, never-read writers, and graph_uri_override; graph_uri is always doc_namespace.
One portable memory layer for every AI agent: local-first, Markdown-native, user-owned, and self-evolving across apps, tools, and workflows.
EverOS's biggest change this window is making embedding and rerank optional, with three capability tiers and a new everos cascade backfill command to fill in vectors later; alongside that it shipped cascade index health monitoring and recovery tooling, a canonical /api/v2 API prefix, native OpenTelemetry tracing, and several reliability and breaking changes to the vector store and SDK.
└──▷ WHAT SHIPPED · 11 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. 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
Optional embedding/rerank with capability tiers and backfillNEW100how completely this was documenteddepth40/40specificity30/30actionability30/30100 / 100
[embedding] and [rerank] are now soft runtime dependencies in everos.toml — EverOS boots with only [llm] configured and degrades gracefully across three tiers: Tier 1 ([llm] only, KEYWORD search), Tier 2 (+ [embedding], VECTOR/HYBRID search plus backfill), and Tier 3 (+ [rerank], AGENTIC search plus knowledge write/search). LanceDB schema v2 allows vector NULL on the six tables (episode, atomic_fact, foresight, agent_case, agent_skill, knowledge_topic), enabling row writes without an embedding provider; a startup banner emits unbackfilled_memory_rows and points at the new everos cascade backfill command, which runs three phases (vectors → clusters → skills, or --phase all) with interactive row/token estimates, --yes/-y for CI, and exit codes 0 success / 1 declined / 2 preconditions unmet / 3 server running / 4 completed-with-failures / 130 SIGINT. Write and search endpoints that need embed or rerank now return HTTP 422 CAPABILITY_UNAVAILABLE with a hint pointing at the relevant everos.toml section, instead of aborting startup or returning 500.
After adding [embedding] to a previously embedding-free instance, fill in NULL vectors for all existing rows without manual intervention.
$ everos cascade backfill --phase all --yes
Run only the vector phase interactively to review row and token estimates before committing — useful when storage or token budget is a concern.
$ everos cascade backfill --phase vectors
Start EverOS with only an LLM provider to get Tier 1 (KEYWORD search) while deferring embedding setup — no longer causes an abort on startup.
toml
[llm]
model = "gpt-4o"
api_key = "<key>"
# [embedding] and [rerank] intentionally omitted — EverOS boots in Tier 1
— Extensive named tiers, keys, commands, and codes; runnable examplesv1.2.1
02
`everos cascade rebuild` recovery commandNEW93how completely this was documenteddepth35/40specificity28/30actionability30/3093 / 100
New CLI command for recovering a drifted or corrupt LanceDB index: drops all business LanceDB tables, clears the cascade queue, and re-indexes all markdown from scratch. Supports --yes / -y for non-interactive use and requires the server to be stopped first, exiting with code 3 if the server is running or 130 on Ctrl-C.
Recover a drifted or corrupt LanceDB index non-interactively after stopping the server — re-enqueues all markdown files so nothing is left silently un-indexed.
$ everos cascade rebuild --yes
— Exact command, flags, and exit codes given; fully actionablev1.2.2
03
GET /health readiness fields for cascade and capabilitiesIMPROVED90how completely this was documenteddepth35/40specificity30/30actionability25/3090 / 100
GET /health now returns a cascade readiness block with fields healthy, reasons, pending, failed_permanent, failed_retryable, drain_consecutive_failures, unrecoverable_total, optimize_failure_streak, and prune_stale_seconds, with HTTP status kept at 200 to avoid triggering container restarts on degraded state; operators should alert on cascade.healthy flipping false for drain-loop failures (≥3 in a row), wedged index maintenance (≥5), or stalled per-table version cleanup (≥3 missed 300s beats). It also now returns a typed Pydantic HealthResponse model with capabilities and disabled_features fields, producing real OpenAPI shapes instead of additionalProperties: true.
Poll the health endpoint to alert on cascade operational faults — drain failures, stuck index maintenance, or stalled per-table version cleanup.
— Names all fields and thresholds; runnable curl example providedv1.2.1v1.2.2
04
Native OpenTelemetry tracing with OTLP exportNEW74how completely this was documenteddepth32/40specificity24/30actionability18/3074 / 100
Adds native OpenTelemetry tracing, enabled via the [observability] config section plus the optional otel extra, exporting memory operations — add/flush, memcell boundary, episode extraction, search, and OME reflection — to any OTLP backend (e.g. Langfuse) as nested traces carrying LLM/embedding token usage, per-request correlation, and recall-quality scores. Supports opt-in content capture (query and extracted memory) with redaction awareness.
Point an existing OTLP-compatible observability backend (e.g. Langfuse) at EverOS memory operations to capture token usage and recall-quality scores.
$ curl -X GET https://<everos-host>/api/v2/memory/search
— Config key and extra named; mechanism described, no exact commandv1.2.0
05
Canonical `/api/v2` API prefixIMPROVED73how completely this was documenteddepth28/40specificity25/30actionability20/3073 / 100
Adds /api/v2 serving all memory/*, ome/*, and knowledge/* endpoints, aligning the open-source API with the EverOS Cloud contract; /api/v1 is retained as a permanent backward-compatible alias. Docs, README, QUICKSTART, and everos demo --live were updated to target /api/v2 as canonical.
— Endpoint prefixes named; alias behavior clear, no runnable examplev1.2.0v1.2.1
06
Deadlines on write-lock operationsIMPROVED70how completely this was documenteddepth30/40specificity28/30actionability12/3070 / 100
All seven write-lock operations — add, upsert, update, delete, delete_by_md_path, prune, and rebuild_indexes — now run under a deadline covering both lock acquisition and body execution, surfacing contention as the retryable VectorStoreBusyError instead of silently wedging a table.
— Lists all operations and error type; monitoring only, no commandv1.2.2
07
Calibrated vs raw recall scoringBREAKING70how completely this was documenteddepth30/40specificity25/30actionability15/3070 / 100
KEYWORD and single-route VECTOR searches now report their top score as recall_top_score_raw; recall_top_score is reserved for calibrated methods (HYBRID logistic-regression sigmoid, AGENTIC cross-encoder) on a comparable [0, 1] scale, with metadata = {"method": ..., "calibrated": ...} attached to every recall score. Dashboards built on the old recall_top_score for keyword search must switch to recall_top_score_raw, since the old name now carries only calibrated values.
— Precise field semantics named; migration guidance but no commandv1.2.1
08
SDK breaking renames: MemoryRoot and cluster lookupBREAKING65how completely this was documenteddepth25/40specificity25/30actionability15/3065 / 100
MemoryRoot.default() is renamed to MemoryRoot.resolve(); default() is kept as a shim that emits DeprecationWarning and will be removed in a future major release. cluster_repo.find_cluster_id_for_member now requires (app_id, project_id, owner_id) instead of entry_id alone.
— Exact renamed methods and new signature named; clear migrationv1.2.1
09
Startup schema check detects column type driftIMPROVED62how completely this was documenteddepth28/40specificity22/30actionability12/3062 / 100
Startup schema verification now detects column type drift in addition to missing or extra columns — e.g. catching episode.subject_vector stored as string instead of the declared 1024-d fixed_size_list — and points the operator at everos cascade rebuild when a mismatch is found.
— Concrete before/after example; lacks direct command to runv1.2.2
10
Lock-free LanceDB compaction and reclamationIMPROVED62how completely this was documenteddepth32/40specificity22/30actionability8/3062 / 100
LanceDB maintenance is now split into a lock-free optimize() compaction step and a write-locked prune() reclamation step; files older than 60s become eligible for reclamation on a 300s beat, preventing unbounded index growth without manual intervention.
— Mechanism explained with timings; no user-facing action neededv1.2.2
thinner coverage below
11
Fast-fail on embedding dimension mismatchIMPROVED56how completely this was documenteddepth28/40specificity20/30actionability8/3056 / 100
A query vector whose dimension disagrees with the embedding provider's declared dim now fails immediately with CONFIGURATION_ERROR instead of reaching LanceDB and returning an opaque unhandled 500 after 13–14s.
— Named error code and behavior change; no example givenv1.2.2
└──▷ BREAKING ON UPGRADE
!Dashboards built on recall_top_score for keyword search must switch to recall_top_score_raw — the old name now carries only calibrated (HYBRID/AGENTIC) values.
!MemoryRoot.default() is renamed to MemoryRoot.resolve(); default() is kept as a shim that emits DeprecationWarning and will be removed in a future major release.
!cluster_repo.find_cluster_id_for_member now requires (app_id, project_id, owner_id) instead of entry_id alone.
gridctl's three releases this window built out a full agent and pack ecosystem around the skill library, adding agent resources, a packs manifest and REST surface, poisoning-aware skill pin review, declarative client linking and tool groups in stack.yaml, native OAuth brokering, a server catalog, and new Logs/Traces/Metrics workspaces in the web UI.
└──▷ WHAT SHIPPED · 22 FEATURESmost completely described firstwhat's the number?
Each feature carries 0–100 for how completely the vendor documented
it — not how big or important the work is. A major capability
described in eight words scores low, and that is the finding.
depth0–40what it does and how it works or what changed
specificity0–30names real surfaces — APIs, flags, formats, limits, numbers
actionability0–30enough to go use it — a named endpoint, flag, or config key tops this; a UI path is a starting point
Code and config rank first by construction: a documented endpoint,
flag or config key scores at the top of specificity and actionability,
so it sorts above a feature described only in prose. Under
60 the notes go thin — everything below the “thinner
coverage” line is thinner documentation, not smaller work.
Hover any meter for that feature's three sub-scores.
01
Declarative client linking via stack.yamlNEW91how completely this was documenteddepth35/40specificity28/30actionability28/3091 / 100
Adds a link: block to stack.yaml for declarative client linking — lists clients (e.g. claude, cursor, grok) that are auto-linked to the gateway on every gridctl apply and removed on gridctl destroy --unlink.
Automatically link Claude Desktop and Cursor to the gateway every time you apply your stack, so you never manually edit client configs again.
— Exact config key and commands with runnable examplev0.1.0-beta.15
02
Tool groups with per-group endpoints and management UINEW90how completely this was documenteddepth32/40specificity30/30actionability28/3090 / 100
Adds tool groups with per-group endpoints at /groups/{name}/mcp, configurable via a groups: block in stack.yaml with servers, tools, and exclude keys; adds a tool groups panel to the web UI for managing groups.
Expose a focused subset of tools to local-model clients by defining a named tool group with its own /groups/release/mcp endpoint.
— Exact endpoint pattern and config keys with examplev0.1.0-beta.15
03
Native OAuth brokering for remote MCP serversNEW83how completely this was documenteddepth30/40specificity25/30actionability28/3083 / 100
Adds native OAuth brokering for remote MCP servers: authorize once with gridctl auth login <provider>, and tokens are stored encrypted and auto-refreshed.
Local state reset controlsNEW80how completely this was documenteddepth25/40specificity25/30actionability30/3080 / 100
Adds a GRIDCTL_HOME environment variable to override the default home directory (useful for isolated workspaces), a gridctl reset command to clear local state, and a matching reset dialog in the web UI.
Override the default gridctl home directory in a shared CI environment where multiple workspaces must stay isolated.
Wipe local gridctl state when a workspace has drifted or you need a clean slate without reinstalling.
$ gridctl reset
— Named env var and command with two runnable examplesv0.1.0-rc.2
05
Packs: manifest, import auth, and provenance trackingNEW78how completely this was documenteddepth30/40specificity28/30actionability20/3078 / 100
Adds packs support for skills, agents, and wiring via a gridctl-pack.yaml manifest, a packs REST surface, and a Library Packs segment in the UI; adds pack credential collection in the import wizard with auth parity across the engine, CLI, and REST API; and adds pack provenance chips across the Library and Connections views.
Import existing MCP client configs into stack.yamlNEW78how completely this was documenteddepth28/40specificity22/30actionability28/3078 / 100
Adds gridctl import to scan existing MCP client configs and append discovered servers to stack.yaml, offering plaintext secrets into the encrypted variable store.
Scan existing MCP client configs and import discovered servers into your stack, migrating secrets into the encrypted variable store.
$ gridctl import
— Runnable command with clear behaviour describedv0.1.0-beta.15
07
Skill pinning and governance with poisoning detection and reviewNEW67how completely this was documenteddepth30/40specificity22/30actionability15/3067 / 100
Adds a skill governance backend (pins) with UI in Pins and Library; adds poisoning-aware pins with injection heuristics evaluated at pin and approve time; and adds pins review with word and schema diffs plus review actions and findings ergonomics.
Agent resource kind with git import and multi-client renderingNEW65how completely this was documenteddepth28/40specificity22/30actionability15/3065 / 100
Adds an agent resource kind with git import support, plus REST and projection endpoints for agents, and adds multi-client agent renders.
— Names REST/projection endpoints without exact pathsv0.1.0-rc.1
09
Server catalog with search, gridctl add, and catalog pickerNEW64how completely this was documenteddepth22/40specificity20/30actionability22/3064 / 100
Adds a server catalog with search and a gridctl add command for appending catalog servers to stack.yaml by name, plus a catalog picker in the add-server wizard in the web UI.
— Named command with clear usage, no example givenv0.1.0-beta.15
thinner coverage below
10
Logs, Traces, and Metrics workspaces in web UINEW58how completely this was documenteddepth25/40specificity18/30actionability15/3058 / 100
Adds Logs and Traces workspaces to the web UI with MCP-native log list/findability and trace waterfall depth views; adds a metrics drill-down view and Overview home screen to the Metrics workspace, including limit consumption display; and adds a resizable Traces workspace layout.
OpenAPI-backed server creation: operations picker and spec previewNEW55how completely this was documenteddepth20/40specificity20/30actionability15/3055 / 100
Adds an OpenAPI operations picker to the create-server wizard, letting users select specific operations when defining an OpenAPI-backed MCP server, plus an OpenAPI spec preview endpoint for inspecting the resolved spec before applying.
— UI wizard flow and preview endpoint named, no exact path givenv0.1.0-rc.2
12
Server authorization configuration and controlsNEW53how completely this was documenteddepth20/40specificity18/30actionability15/3053 / 100
Adds wizard-based auth configuration for external MCP servers with OAuth, bearer, and header options, and surfaces server authorization controls in the web UI.
— Named auth options but no exact UI path or configv0.1.0-beta.15
13
Fragment library and context drift reviewNEW50how completely this was documenteddepth20/40specificity18/30actionability12/3050 / 100
Adds a rules fragment library backend, fragment-level context drift review, and a 'fragments' mode in the Global Context dialog.
— Named UI mode but no config keys or commandsv0.1.0-rc.1
14
Library workspace for skills and agentsNEW43how completely this was documenteddepth18/40specificity15/30actionability10/3043 / 100
Adds a Library workspace for managing skills, and adds an Agents segment to the Library workspace for managing agents.
Client connection management: health hub and wiring ownershipNEW43how completely this was documenteddepth18/40specificity15/30actionability10/3043 / 100
Adds a per-client health hub in the Connections view and lockfile-backed wiring ownership for client links.
— Brief description, no named config or endpointv0.1.0-rc.1
16
MCP 2026-07-28 dual-stack transport supportNEW41how completely this was documenteddepth15/40specificity18/30actionability8/3041 / 100
Adds support for the MCP 2026-07-28 spec's dual-stack transport.
— Names spec version but no usage detailv0.1.0-rc.1
17
Tools workspace audit filters and access controlsNEW37how completely this was documenteddepth15/40specificity12/30actionability10/3037 / 100
Adds audit filters, annotations, and tool-level access controls to the Tools workspace.
— UI area named, no exact controls detailedv0.1.0-beta.15
18
Model preference support for skills and agentsNEW33how completely this was documenteddepth15/40specificity10/30actionability8/3033 / 100
Adds model preference support for skills and agents, with backend support and surfacing in the Library UI.
— Thin description, no concrete options namedv0.1.0-rc.1
19
Variables least-privilege scoping and trust controlsNEW26how completely this was documenteddepth12/40specificity8/30actionability6/3026 / 100
Adds least-privilege scoping and trust controls for Variables.