Skip to content

Release notes

The scope, main changes, and known issues of v1.0.0-rc.2.

Here’s a summary of v1.0.0-rc.2. For every change with its issue and pull request, see the change-by-change release notes.

Cortrix v1.0.0-rc.2 is a pre-release for local evaluation and integration testing. It isn’t a production-readiness claim. Before you upgrade from RC1, read Upgrade and Compatibility and status.

Highlights

  • License change: Cortrix-authored RC2 material is available under the Apache License 2.0. The historical v1.0.0-rc.1 release remains under AGPL-3.0-only.
  • More reliable asynchronous ingestion: task identity is scoped to the namespace, and terminal-state transitions, cancellation races, cleanup scheduling, and retry de-duplication are all stronger.
  • Reranking can be turned off per request: for duplicate detection and similar-item lookups, set rerank=false on the query.
  • MCP works with modern and legacy clients: the local MCP server supports the modern stdio discovery path while keeping the legacy initialization handshake, and it passes session and trace identity to the Cortrix server.
  • Hardening in several places: parser output handling, sparse-vector decoding, configuration validation, memory-scope validation, and operation-log error reporting.
  • Deployment defaults are unchanged: Docker Compose still listens only on the loopback address by default, with a new explicit publish-address option for isolated test networks.

FiQA retrieval accuracy

With the non-LLM cross-encoder reranking configuration, the RC2 benchmark results on FiQA are higher than the July baseline:

MetricJuly resultAugust resultRelative change
nDCG@100.25260.3125+23.7%
Recall@100.36350.4523+24.4%

These are retrieval-accuracy measurements, not server performance measurements. The two runs differ in build, configuration, and execution environment, so the comparison doesn’t isolate the improvement to any single code change.

For the scope and limits of the measurements, see Benchmark evidence.

Compatibility notes

  • Setting rerank=false on an individual query is the verified way to turn reranking off. The namespace-level reranker_config.enabled isn’t wired into the query path yet.
  • Local stdio is the current public MCP transport.

Known issues

IssueTracking
Enrichment backfill still has open follow-ups in scheduling and transport retries#62, #78
HyPE LLM-call metrics aren’t connected to the production enrichment path yet#69
The LAN publish-address option doesn’t yet give you a complete authenticated setup without editing configuration by hand#71
Ingestion into a single namespace is constrained by serialized durability and index updates#73
Cross-encoder reranking is on by default, even for tasks where turning it off is the better choice#75
Uploading a changed version of a file, or changing a watched file, can leave the previous version’s passages in query results; the issue lists workarounds#157
The server can crash with a segmentation fault while it exits, for example after a start that can’t bind its port while document tasks are queued; make sure the port is free before you start it#196
A failed task’s progress always reports retryable_if_fail: true, even when resubmitting it will fail the same way; cap your retries#199

Release artifacts

GitHub provides source archives for the tag automatically. RC2 doesn’t promise a separately published container image or prebuilt binary unless the GitHub pre-release page explicitly attaches one. To use Cortrix, build it from source. See the Quickstart.

Full changelog

Next steps