• v0.41.50 3d0a584c15

    code-index v0.41.50
    All checks were successful
    Pilot plugin compatibility / Pilot scope (push) Successful in 11s
    CI (Windows) / changes (what this run must test) (push) Successful in 15s
    CI (Windows) / fmt + clippy + build + test (windows) (push) Has been skipped
    CI / changes (what this run must test) (push) Successful in 18s
    Package CI / changes (which packages this run must test) (push) Successful in 18s
    Package CI / package suites (clippy) (push) Has been skipped
    Package CI / package (javascript) (push) Successful in 1s
    Package CI / package (csharp) (push) Successful in 2s
    Package CI / package (ruby) (push) Successful in 2s
    Package CI / package (php) (push) Successful in 2s
    Package CI / package (python) (push) Successful in 1s
    Package CI / package (svelte) (push) Successful in 3s
    Package CI / package (timeline) (push) Successful in 2s
    Package CI / package (typescript) (push) Successful in 2s
    Package CI / package-corpus (xaml) (push) Successful in 3s
    Package CI / package (rust) (push) Successful in 3s
    Package CI / package-corpus (vue) (push) Successful in 4s
    Package CI / package (xaml) (push) Successful in 1s
    Package CI / package (vue) (push) Successful in 2s
    Package CI / package-corpus (javascript) (push) Successful in 4s
    CI / cargo fmt (push) Successful in 26s
    Package CI / package-corpus (python) (push) Successful in 3s
    Package CI / package-corpus (rust) (push) Successful in 2s
    CI / cargo clippy (push) Has been skipped
    Package CI / package-corpus (ruby) (push) Successful in 3s
    CI / cargo check (MSRV 1.99.1) (push) Has been skipped
    CI / cargo check (windows-gnu) (push) Has been skipped
    CI / cargo test (abi, 32-bit + wasm32) (push) Has been skipped
    CI / cargo deny (push) Has been skipped
    CI / CI lane wall-clock headroom (push) Has been skipped
    CI / guest crates (fmt, clippy, doc) (push) Has been skipped
    CI / cargo doc (intra-doc links) (push) Has been skipped
    CI / OSS corpus (tier 1) (push) Has been skipped
    Package CI / package-corpus (php) (push) Successful in 3s
    CI / OSS corpus tier-3 scale (nightly) (push) Has been skipped
    CI / Grammar rebuild from source (nightly) (push) Has been skipped
    CI / cargo test (push) Has been skipped
    Package CI / package-corpus (typescript) (push) Successful in 3s
    Package CI / package-corpus (csharp) (push) Successful in 5s
    Package CI / package-corpus (svelte) (push) Successful in 3s
    CI / cargo test (daemon transport) (push) Has been skipped
    Package CI / package overhead budgets (nightly, one package at a time) (push) Has been skipped
    CI / Plugin path cost + pool throughput (nightly) (push) Has been skipped
    Package CI / package-corpus (timeline) (push) Successful in 3s
    Pilot plugin compatibility / Fetch the pinned runtime once (push) Successful in 17s
    Pilot plugin compatibility / Pilot compatibility (csharp) (push) Successful in 9s
    Pilot plugin compatibility / Pilot compatibility (timeline) (push) Successful in 11s
    Pilot plugin compatibility / Pilot compatibility result (push) Successful in 1s
    Release Build / Generate Version (push) Successful in 7s
    Release Build / Required CI green (push) Successful in 28s
    Release Build / Build linux-aarch64 (push) Successful in 12m18s
    Release Build / Build linux-x86_64-musl (push) Successful in 18m47s
    Release Build / Build linux-x86_64 (push) Successful in 20m9s
    Release Build / Build windows-x86_64 (push) Successful in 24m42s
    Release Build / Assemble the release archives (push) Successful in 42s
    Release Build / Windows archive smoke (msvc) (push) Successful in 1m18s
    Release Build / Create Forgejo Release (push) Successful in 26s
    Release Build / Seed the package channel (push) Successful in 12s
    Stable

    buildagent released this 2026-11-12 11:08:20 +01:00 | 142 commits to master since this release

    code-index v0.41.50

    Build: v0.41.50+2578

    Installer: install.sh and checksum. Both come from this release commit. To pin the installed binaries too, run it with --tag v0.41.50.

    Windows installer: install.ps1 and checksum, from the same release commit. It installs AND updates — the same code does both — verifies the archive against its published .sha256 before unpacking, refuses hostile archive members (absolute paths, .. escapes, symlinks and reparse points, which Expand-Archive does not protect you from), and grants nothing when it installs a package: the bytes go into the machine's store and the approving line is PRINTED for you to run from inside a project. -Help lists the flags; -Tag v0.41.50 pins the binaries.

    Four-binary release: code-index-mcp (MCP stdio bridge — the usual entry), code-index-daemon (long-lived watcher + RPC server, auto-spawned), code-index-plugin-host (bounded worker for plugin packages, spawned by the daemon), and code-index (CLI: init, index, watch, doctor, link, plugin).

    Changed behaviour

    • code-index query with an invalid .code-index.toml prints the structured refusal (index_unavailable, reason invalid_configuration) as one JSON document on stdout and exits 1. It printed nothing and exited 2.
    • Malformed argument values answer with one code, invalid_argument_value, wherever the published schema states what is accepted. It replaces invalid_max_depth, invalid_token_budget, invalid_direction, invalid_role_filter, invalid_ref_kind, invalid_resolution, invalid_response_format, empty_seeds, too_many_seeds and invalid_arguments; scripts that match on those codes need the new one. Codes that state a rule the schema cannot express keep their names (for example unsupported_glob_syntax, invalid_range, revision_symbol_unsupported).

    MCP arguments (#570)

    • One policy per argument now drives the published schema, the runtime check and the error text. Schemas state enums (response_format, envelope, direction, role_filter, resolution, ref_kind, category), static defaults, strict ranges and list sizes; a clamped argument states x-applied-range instead of a rejecting maximum. Handlers accept every spelling they accepted before; a test replays 38 calls recorded against v0.41.49.
    • The four malformed-argument codes (unknown_argument, missing_required_argument, invalid_argument_type, invalid_argument_value) have the same fields: error, tool, query (the argument), received, accepted (the argument's schema fragment), default when there is a static one, and a one-sentence hint. Values that previously ended as a free-text deserialization error (a negative limit, an unknown search_text.category) are refused in this shape. Every other error body is unchanged from v0.41.49; a test compares nineteen of them with bodies recorded from v0.41.49.
    • change_impact with limit: 0 adds witness_paths_total, the number of witness chains the count-only reply withholds. test_role_files is still listed in full, as in v0.41.49.
    • A clamped value is echoed: arguments_applied.<argument>: {requested, applied}, for example search_text.context_tokens.
    • response_format: "concise" is accepted by list_files, get_dependencies and resolution_gaps.
    • limit on changed_symbols and review_diff is still refused; the refusal now says that a page is bounded by the response budget and continued with cursor.
    • docs/mcp-arguments.md is the reference for every tool argument (default, bounds, values, tool families and their exemptions); a test compares it with the published schema in both directions.
    • tools/list is 59,167 bytes (59,311 in v0.41.49); a test holds it at or below the release's size.

    Resolution (#566)

    • A qualified reference is no longer bound across files on name evidence alone when the file's own imports or module declarations contradict the candidate; where the module evidence names one candidate, the reference is now bound to it. Against v0.41.49 on the nine pinned repositories: 19 binds removed, 228 added, 1 retargeted, 133 with a changed rule tag only. Every removal and the retarget were read and were wrong before. Every candidate addition was audited: 228 are correct, and the one wrong one was removed by a rule fix before the merge. A second, blind audit of 65 rows by a different worker agrees on every row.
    • By repository (removed / added): rust-analyzer 15 / 194, rust-ripgrep 0 / 18, ts-zod 0 / 13, js-express 2 / 3, php-guzzle 2 / 0; the other four are unchanged.
    • 33 wrong binds that this change does not touch are known and listed on #566 (31 inherited, 2 found as audit controls).
    • Every package-supplied input of the new rules (imports, references, symbols, module identities) passes a capability grant before it can route or refuse a bind. A package without reachability_anchor cannot disambiguate a reference through its imports; a test holds that.

    Fixes

    • Incomplete extraction (#545, host side): project_overview (extraction_diagnostics.files and the parse_error_files sample), resolution_gaps.partial_source_census, index_coverage.extraction_diagnostics, list_files and evidence_gaps on ordinary replies read one census. A file the host refused (fact.string_too_long, host.deadline_exceeded, host.memory_ceiling_exceeded, content_refused) is now counted by all of them; before, the census and the coverage diagnostics reported none for such a file. A partially extracted file keeps its symbol count in list_files, marked symbols_are_floor: true with its diagnostic codes.
    • A source file that an extractor claims but that is not valid UTF-8 is recorded as content_refused instead of being absent from the index. Undecodable metadata files are skipped as before. changed_symbols and review_diff report such a file as not_indexed: true, not as pending.
    • read_code with rev reads a path whose directory no longer exists in the working tree (#568).
    • Every JSON resource carries application/json in resources/list and on the content block of resources/read (#569).
    • search_text with a path_glob that names one permanently excluded file answers empty_population.basis: "refused" with the coverage verdict, reason and remedy, instead of advising to drop the filter (#521).
    • The daemon no longer stops answering path_claims when a package activation changes while a claim is being computed (for example while a publisher is withdrawn). The call re-acquired a lock it already held and could wait forever behind the activation; it now answers from one snapshot. v0.41.49 and earlier have the defect.
    • code-index query: when two first queries start at the same moment, the one that had chosen a local read and then found the other's daemon alive no longer answers a negative lookup from its read-only snapshot as if the index were ready. It hands off to the daemon and answers index_incomplete until the daemon has caught up. v0.41.49 and earlier could answer symbol_not_found over an index still being reconciled (with the lagging files disclosed).
    • install.sh --check and install.ps1 -Check also report a code-index found on PATH outside the selected prefix, with its version (#572).
    • The release notes' build line names the core tag of the run, also on a promotion run (#572).

    Cost

    • A cold index costs +0.7 % to +1.7 % more SQLite VM steps than v0.41.49 on seven of the nine pinned repositories and less on two (ts-zod −14.0 %, rust-analyzer −2.5 %). Full-scan steps are +0.7 % to +2.0 %. Two costs were attributed per statement and removed before the baselines were blessed: five module-evidence statements rescanned their group and anchor tables (full scans +7.7 % to +10 % on three repositories) and now probe by file key; one capability check changed a query plan (26× the steps of that statement on rust-ripgrep) and is now probed last.
    • The incomplete-extraction census is computed once per content revision and cached. On a synthetic index of 200,000 contributions: 25–29 ms for the first call after a change, about 0.05 ms afterwards; the release's narrower statement took 0.09 ms on every call.

    Remaining scope

    • #575: one search_text query with a very long literal (hundreds of kilobytes) can keep the server busy for seconds on Linux and for minutes on Windows. A length bound in the argument policy is planned.
    • #545: clamping oversized strings, the depth-limit diagnostic, the member-chain re-walk and lossy decoding are guest-side and need a release of every language package. The requested bytes of a host.memory_ceiling_exceeded refusal are still not reported; that needs a change to the worker/supervisor protocol.
    • #570: the path_glob and lang output filters on the reference, dependency and diff tools (eleven cells, listed as planned exemptions in docs/mcp-arguments.md), additive aliases, a limit on the diff tools, and the same registry for configuration keys, environment variables, CLI flags and durations.

    Qualification

    • One full gate run on the integrated tree with an empty package store: 43 steps (format, lints for Linux and the Windows GNU target, docs, the workspace and daemon suites with their timing profiles, precision gate, the corpus suites, all eleven package legs, scale, tier 3, the nightly-only benchmarks, acceptance of the shipped build). 40 passed at once. The three that did not were attributed and their steps re-run green:
      • Agent task benchmark: recall fell on rust-ripgrep and python-flask because a change in this train emptied change_impact's test_role_files at limit: 0. That change is withdrawn; recall is 38/38 and 33/33 again.
      • Tier-3 record: the drift equals the audited bind account (rust-analyzer +179 resolved, 120 retagged; py-django 6 retagged). Re-recorded with that account as the reason.
      • JavaScript package parity: the declared unbound-by-scope count on js-express is 41, was 42. One write (app.request.querystring = function …) that the builtin bound to an unrelated local is now refused by the host; the package never bound it.
    • After those fixes: both MCP suite legs 1,082 passed each; fast gates, format, lints and docs clean.
    • CI found four failures in its first two rounds. Two were defects that are also in v0.41.49 and are fixed above (the path_claims lock, the one-shot read beside a live daemon). One was a Windows-only path assumption in a new test. One was a new test whose 400,000-character search_text literal did not answer within 30 s on Windows: the cost of a long literal grows quadratically in SQLite's FTS5 phrase construction (#575, in every release, not fixed here); the test now uses the shortest literal that reaches the same refusal.
    • CI round 3 on the released commit is green in all four workflows: Linux 5,634 tests passed, Windows 5,406 passed; the package and pilot-plugin workflows passed.
    • Windows is qualified by CI only.

    Downloads

    Four platforms are built for every release. The table below says which ones THIS release published.

    Platform Archive
    Linux x86_64 (glibc) code-index-v0.41.50-linux-x86_64.tar.gz
    Linux x86_64 (static/musl) code-index-v0.41.50-linux-x86_64-musl.tar.gz
    Linux ARM64 code-index-v0.41.50-linux-aarch64.tar.gz
    Windows x64 code-index-v0.41.50-windows-x86_64.zip

    First-party language packages

    Every archive carries code-index-packages/: the first-party language packages at the versions the package channel had published when this release was cut — de.h-dv.csharp-0.1.11 de.h-dv.javascript-0.1.6 de.h-dv.php-0.1.6 de.h-dv.python-0.1.5 de.h-dv.ruby-0.10.2 de.h-dv.rust-0.1.8 de.h-dv.typescript-0.1.7 — each signed by the key below and verified at the install door. code-index languages enable <lang> adopts the bundled package offline. A package is released by its own pkg/<id>/v<version> tag, whose release carries its .cip, .cips and digest, and code-index plugin update <id> reads the package channel, so a package fix reaches you without a new core release.

    These release binaries contain no native language parsers. Under auto, enabled languages use their approved packages. First start adopts bundled packages verified against this build's own publisher keys; existing approvals and enablement remain authoritative. If your project explicitly pins a language to builtin, switch it with code-index languages owner <lang> auto; an unavailable builtin is refused rather than silently ignored. To enable languages explicitly:

    code-index languages enable csharp
    code-index languages enable javascript
    code-index languages enable php
    code-index languages enable python
    code-index languages enable ruby
    code-index languages enable rust
    code-index languages enable typescript
    

    About that key

    sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72c is a long-lived Ed25519 key held as a secret in this project's CI, used to sign released packages automatically, and it is compiled into the binaries in this release. It signs every first-party package. That trusts this project's release pipeline, not only its maintainers: anyone who can run a release workflow here can produce a package that verifies under it. It adds nothing you had not already granted — the bytes are inside the program you are running, so forging that anchor means forging the binary — but you are entitled to know it is there before a package installs rather than after.

    There is no expiry — deliberately, because offline installations must not break on a timer — and withdrawal is on your side and works: code-index plugin trust remove sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72c. A compiled-in key has no file to delete, so that writes one instead, carrying denied = true; the key stops verifying at the next load, plugin trust list shows it marked [DENIED], and deleting that file (the command prints its path) is the only undo. If the key is ever rotated, the new fingerprint is published here and in tests/packages/first-party.fingerprint, and a build that predates the rotation will not trust it.

    macOS is not currently built. No x86_64-apple-darwin or aarch64-apple-darwin archive is published — macOS users should build from source (cargo build --release). This is a deliberate deferral, tracked in #59; no date is promised.

    Wire into Claude Code

    { "mcpServers": { "code-index": { "command": "/usr/local/bin/code-index-mcp", "args": ["--root", "/path/to/your/project"] } } }
    

    SHA256 checksums (.sha256 files) available for every archive.

    Downloads