-
code-index v0.27.0
StableAll checks were successfulCI / cargo fmt (push) Successful in 47sCI / OSS corpus tier-3 scale (nightly) (push) Has been skippedCI / Grammar rebuild from source (nightly) (push) Has been skippedCI / cargo doc (intra-doc links) (push) Successful in 4m53sCI / cargo test (abi, 32-bit + wasm32) (push) Successful in 5m18sCI / cargo deny (push) Successful in 5m15sCI / cargo clippy (push) Successful in 5m47sCI / cargo check (windows-gnu) (push) Successful in 6m12sCI / cargo check (MSRV 1.98) (push) Successful in 5m51sCI / OSS corpus (tier 1) (push) Successful in 25m24sCI / cargo test (push) Successful in 30m14sCI (Windows) / fmt + clippy + build + test (windows) (push) Successful in 40m59sCI / cargo test (daemon transport) (push) Successful in 12m54sCI / Plugin path cost + pool throughput (nightly) (push) Has been skippedRelease Build / Generate Version (push) Successful in 27sRelease Build / Required CI green (push) Successful in 1m1sRelease Build / Build linux-aarch64 (push) Successful in 12m25sRelease Build / Build linux-x86_64 (push) Successful in 15m33sRelease Build / Build linux-x86_64-musl (push) Successful in 15m42sRelease Build / Pack the XAML reference package (push) Successful in 50sRelease Build / Build windows-x86_64 (push) Successful in 20m23sRelease Build / Windows archive smoke (msvc) (push) Successful in 8sRelease Build / Create Forgejo Release (push) Successful in 2m54sreleased this
2026-09-08 20:57:30 +02:00 | 1905 commits to master since this releasecode-index v0.27.0
Build: v0.27.0+679
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), andcode-index(CLI: init, index, watch, doctor, link, plugin).The runtime plugin architecture becomes usable end to end; the Windows archive is
rebuilt on a linkage where a guest trap is actually intercepted rather than
fatal; and a round of dogfooding against this release candidate fixed eleven
findings — ten places where a tool reported a state it had not measured, and one
operator-facing measurement that had gone stale.A second package,
de.h-dv.timeline, exists in this tree and is graded by CI —
itsextractor.wasmis rebuilt from source and byte-compared on every run — but
it is NOT published as a release asset here. The only.cipthis release
ships is the XAML reference package. An operator who wants the TimeLine package
must pack it themselves from the source tree; a signed asset for it is planned
for the next release.Two further findings from that round are filed and NOT fixed here — an index that
cannot see a git worktree's own edits, and a corpus bless writer with no arm for a
record whose measurement reproduced while its conditions moved.149 commits since v0.26.1.
Upgrading: existing conformance verdicts must be re-run
This release records the WASM engine identity with the execution knobs it pins
(epoch,fuel,stack,rsimd,rsimd_det,multimem,backtrace), not the
wasmtime version alone. Those knobs decide how a package actually runs, so a C1
verdict recorded without them is not provably transferable to this host — and every
verdict recorded by v0.26.1 or earlier was recorded without them.On any machine that already holds conformance verdicts,
code-index plugin doctor
reports them as not current and WARNs, andplugin statusshowsnot run here.
Nothing is broken and no package changed; the record is simply less precise than
the check now requires. A fresh install is unaffected — it has no prior verdict.Remedy, once per installed package:
code-index plugin check <digest>plugin doctornames this case explicitly ("recorded before this host began
pinning engine knobs — samewasmtime <version>") rather than reporting it as
another engine, so the wording does not send you looking for a wasmtime change
that did not happen.Upgrading: the first run after this release re-parses your code files
A schema migration widens the recorded annotation region so a position inside a
symbol's documentation resolves to the symbol it documents. That lower bound comes
out of the parser and cannot be derived from stored rows, so the migration
invalidates everycoderow and the next index pass re-parses them.Nothing is lost and no action is needed. The daemon answers throughout, and
project_overviewdiscloses the window while it runs —state: "reconciling"with
aSCHEMA-UPGRADE REBUILDdetail naming how many files still carry the
invalidation sentinel. Counters read during that window describe rows being
replaced, and the payload says so rather than letting you read them as settled.Text and metadata rows (Markdown, TOML, SQL, and the rest) are deliberately NOT
invalidated — they carry no extraction, so re-hashing them would cost time and
change nothing.Cost is proportional to code files, not to repository size on disk. A full
re-parse of a large index has been measured at about ninety minutes; a few hundred
files is seconds.The Windows archive is built natively now, and a guest trap is actually caught
Until this release the Windows archive was CROSS-BUILT on Linux for
x86_64-pc-windows-gnuand linked against the legacymsvcrtC runtime. On
that linkage a WASM guest trap was not intercepted: instead of
host.worker_trappedin milliseconds, the worker took 33 seconds and then
died withabi.frame_truncated, leaving the host with a dead worker and no
usable diagnosis. Every other platform we ship intercepts the same trap
immediately and keeps the worker alive.The archive is now built natively on Windows with the MSVC toolchain, on the
same runner that already smoke-tests it. Measured on the shipping
configuration, one variable at a time:linkage trap verdict worker MSVC, static CRT (shipped now) 67.6 ms host.worker_trappedsurvives gnu + msvcrt (shipped through v0.26.1) 33,293 ms abi.frame_truncateddead Those timings are first-request figures and include worker spawn; steady-state
repeat traps on the surviving configurations measured around 10 ms. The claim
worth taking from the table is not the millisecond count — it is that the trap
is intercepted at all and the worker is still alive to answer the next request.The archive name does not change, and neither does anything else you may
have pinned: release archives are named<os>-<arch>, never by target triple,
so the Windows asset iscode-index-<tag>-windows-x86_64before and after.It depends on no redistributable. The C runtime is linked statically, so the
binaries import only DLLs present on a stock Windows 10 or later install. That
is checked rather than assumed: a plain MSVC build importsvcruntime140.dll,
which ships with the Visual C++ Redistributable and is not on a clean machine,
and the release now REFUSES to publish an archive importing anything outside the
stock set. Trading a trap bug for "the program can't start because
VCRUNTIME140.dll is missing" would have been the worse regression, on the one
path where the user has no toolchain.What this does not claim. The root cause is the C runtime, not the
toolchain. Agnubuild against UCRT also intercepts the trap and keeps the
worker, and the one wasmtime build flag that looked like a suspect
(__USE_MINGW_SETJMP_NON_SEH, which wasmtime defines for every
target_env = "gnu"Windows build) is present in the working configuration too,
so it cannot be the cause on its own. With that held constant the CRT is the
only variable that moved. We ship MSVC because it is a supported configuration
on a runner we already have — not because the gnu toolchain is at fault. UCRT on
the gnu target does work, but it needs a UCRT-CONFIGURED mingw toolchain,
headers andlibmingwexincluded; swapping only the CRT import library is not
enough and fails at wasmtime's ownsetjmp. Measured, with every attempt and
its exact failure, in #231.Upgrading: the XAML package is 0.2.0 and its digest has MOVED
de.h-dv.xamlis now 0.2.0, published asde.h-dv.xaml-0.2.0.cip, and its
digest has moved to
sha256:7b572f5cc32ffcd5af550900a451bbef37e255804776d7e3e3e71d2dd7d0aa79.Re-pin it:
code-index plugin install de.h-dv.xaml-0.2.0.cip \ --sha256 sha256:7b572f5cc32ffcd5af550900a451bbef37e255804776d7e3e3e71d2dd7d0aa79An operator who does not re-pin gets a bare
digest_mismatchand no other
explanation. Theextraction_identitymoved too, so every project with this
package enabled re-extracts its.xamlfiles once — which is the point: files
that were reportedextract.truncated_treeare now indexed whole.Why it moved. The extractor's walk budget cut real markup at roughly 64-80 KB
of source, depending on density — measured on a 14,056-file production repository
where about fifty files were affected, including every theme dictionary. Symbols
past the cut were missing fromfile_outline,search_symbols,find_references
andchange_impact, disclosed per file but easy to miss.All three budgets are now derived from the largest file the indexer will hand any
extractor (2 MiB) rather than from the corpus of the day: the walk budget is 16 MiB
of serialized tree, the output budgets 48,000 facts and 2 MiB of fact bytes. At
2 MiB of dense markup the extractor emits 29,845 facts and reports nothing. Both
truncation codes still fire, still mean different things, and are still
distinguishable throughindex_coverage.The instrument, not just the fix
The bug itself is one line of linkage. What let it ship in every release
carrying a Windows archive is that the tested binary and the shipped binary
were different builds, and nothing compared them. CI built its own gnu
binaries natively and ran the plugin smoke against those; the archive users
downloaded was cross-built and, until this cycle, had never executed a wasm
guest at all.So the durable part of this change is not the CRT:
- the archive is smoked with its own shipped bytes before publication, and
the release job waits on that; - the smoke refuses to grade an artifact whose linkage does not match what
the build leg declared — the refusal that turned this investigation into a
finding instead of a confident wrong number, and it has correctly blocked
publication twice; - linkage is now reported on two axes, toolchain and C runtime, because
after this change both toolchains can import the sameapi-ms-win-crt-*set
and a two-valued verdict would start lying in the opposite direction; - CI's own Windows smoke builds the same linkage as the shipped archive, so
the two cannot drift apart again.
Plugins
A package can now be located, verified, installed, conformance-checked, enabled
with an explicit capability grant, rolled back, disabled, removed and garbage
collected, with every mutating command disclosing what it is about to do first.- A package may displace a builtin's claim, with consent recorded in
[[displaces]]and the operator told what it costs. An undeclared intersection
is still refused. - The package lifecycle is a committed number, ratcheted one rung at a time
rather than asserted. - A refused package reaches an agent as a reason code, not as silence.
- Reproducible guest wasm, byte-comparable from any directory.
- A migrating daemon is distinguishable from a wedged one, and a wedged
project has an exit.
The architecture is proven on a real language rather than on markup alone: the
full-language migration parity gate (#84) is closed.Honesty fixes found by dogfooding this candidate
Eleven findings, filed and fixed against the release candidate itself.
doctorno longer renders "could not measure" as a verdict.PRAGMA integrity_checkreturning "unable to validate … : database is locked" said the
check did not run and was reported as corruption — hardest exactly when an
operator was most likely to run it, mid-reconcile. The opposite direction was
also wrong: an error mid-iteration reported an all-clear.doctor's freshness check counted never-indexable files as staleness — 35 of 35
on this repository — producing a permanent WARN that hid real drift. It now
splits the disk side by the same classifierindex_coverageuses, and asks the
project's own extractor set, so the two surfaces give the same verdict.context_packshipped over-budget responses withbudget_exceeded: false. Six
of eleven budgets were over; the block attached above the router was outside the
arithmetic. The flag and the number are now one measurement of the bytes shipped.changed_symbolsreported a bareref_count: 0for symbol kinds this index
measures as having no use channel, where four other surfaces disclosed it. The
counter and its basis are now a single value, so no surface can render one
without the other.direct_callersgained a basis of its own.review_diff's same-package counterevidence was unreachable in every workspace
and monorepo layout, because the root segment was stripped only when leading.- A declaration's leading DOCUMENTATION block is now part of it, in the six
languages that mark one.get_symbolon a///line answeredsymbol_not_found
while the same query on a#[test]line one file over resolved, and a commit
whose entire deliverable in a file was a correction to a recorded measurement
reportedsymbols: []. Python and Ruby are excluded with reasons and tests:
Python's docstring is already inside the span, and Ruby marks no comment as
documentation — RDoc reads the same#syntax as# frozen_string_literal: true. partial_sourcesnow answers the sentence that cites it. The list of partial
files was suppressed whenever a reply named none of them, so every reply carried
a disclosure pointing at a field that was not there. An empty list is now the
measurement that this reply names none.- One helper decides AND words the engine-drift distinction, across the three
surfaces that render it. A verdict recorded before this host began pinning
engine knobs is no longer reported as another engine. search_text(whole_word=true)graded a different query from the one the daemon
ran. Boolean and prefix expressions were matched as literal source characters and
the resultingtotal: 0was described as exact; ASCII-only matching lost Unicode
case folding, socafémissed a standaloneCAFÉwhilefixmatched inside
préfixé; and the census restated the matching rules a second time, sototal,
matches_in_fileand the returned line numbers could describe different
predicates. One compiled matcher now serves admission, census and line numbers,
and an expression the post-filter cannot honour is refused with a reason instead
of answered with a confident zero. Whole-word pagination also minted unstamped
cursors, bypassing the stale-generation rejection.- The promotion-lock ceiling
plugin enablediscloses to operators was wrong at
the 100k shape. Re-measured, with the cause established by removal rather than by
reading, and the rollup census it pays for is now graded.
One reported defect was refuted rather than fixed, and the counterexample is
pinned so it cannot be quietly re-implemented: a builtin'sauto-generated
exclusion is NOT package-independent, because a consented[[displaces]]covers
exactly the files the builtin excluded.Honest limits
The plugin ABI and the
.cippackage format are EXPERIMENTAL and may change
incompatibly in any release. A package is pinned to one thing — the host fact-ABI
major it brackets in[abi].host_min/host_max— and to nothing else. No
compatibility is promised or implied by this project's semantic version, in either
direction.Epic #75 is not closed by this release. #80's final end-to-end gate has steps
1–11 implemented and green and step 13 done, and step 12 has moved: the Windows
archive is now BUILT natively and executed by a job whose verdict gates
publication, so the platform is no longer cross-built and graded elsewhere.
aarch64 remains UNMET by decision — there is no runner — and that is
declared rather than silently skipped. #41 and #45 remain open.The TimeLine package's ACROSS-DIRECTORY reproducibility is unmeasured.
de.h-dv.timeline'sextractor.wasmis rebuilt from source and byte-compared
wherever the suite runs, CI included — an absent wasm32 target is a failure
there, not a skip. What is NOT measured is the across-directory leg: cargo
derives-C metadatafrom an absolute path, so proving it needs a comparison
between two checkouts, which no singlecargo testcan perform. That state is
"not measured", which is not the same as "measured and bad".Packing determinism is verified separately and independently: the same
checked-in bytes produce
sha256:150ceb22ed9757a660d5a2bf58b80c81b60043cc419e5da5dde559d5d6fc9c9fon two
different machines, directories and host binary builds.Package conformance is bounded evidence, not proof of semantic correctness.
C1 stages a package alone with no capability grant; passing it says the package
runs and responds within budget on its own fixtures.The promotion-lock constant is a flat rate over a cost that climbs with scale.
It is sized to over-predict, which is the direction it is allowed to be wrong in,
and at small generations it over-predicts by more than twice.lock_estimateis
labelled PREDICTED at every call site.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.27.0-linux-x86_64.tar.gz Linux x86_64 (static/musl) code-index-v0.27.0-linux-x86_64-musl.tar.gz Linux ARM64 code-index-v0.27.0-linux-aarch64.tar.gz Windows x64 code-index-v0.27.0-windows-x86_64.zip XAML plugin package
de.h-dv.xaml-0.2.0.cipmakes.xamlfiles carry symbols and references instead of being text-only:x:ClassandClick=handlers bind into the paired C# code-behind,x:Namebecomes a searchable declaration, and{Binding …}stays unresolved because no bridge can reach it.It is NOT installed by installing code-index. Packages are installed into a user-controlled store and approved per project, and installing grants nothing —
enableis the grant.Download
de.h-dv.xaml-0.2.0.cipstoo and keep the.cipsbeside the.cip. Packages are signed and an unsigned one is refused (signature_missing) with no flag that accepts it. You do NOT need to anchor us first: this release's publisher key is compiled into the binary, so the install below works on a machine that has anchored nobody.code-index plugin trust listshows it, marked[BUILTIN], andcode-index plugin trust remove sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72cwithdraws it — see About that key.code-index plugin install de.h-dv.xaml-0.2.0.cip --sha256 sha256:7b572f5cc32ffcd5af550900a451bbef37e255804776d7e3e3e71d2dd7d0aa79 code-index plugin check sha256:7b572f5cc32ffcd5af550900a451bbef37e255804776d7e3e3e71d2dd7d0aa79 code-index plugin enable sha256:7b572f5cc32ffcd5af550900a451bbef37e255804776d7e3e3e71d2dd7d0aa79 \ --capabilities bridge_source \ --bridges 'de.h-dv.xaml/xaml:type->csharp:class,de.h-dv.xaml/xaml:call->csharp:method'The digest above is the one this release packed and it is what
--sha256pins;de.h-dv.xaml-0.2.0.cip.digest.txtcarries it and the extraction identity. A digest that changes between releases means the package changed — re-pin, and read the notes.Only
.xamlis claimed..datasetand other markup remain text-only (searchable, no symbols).About that key
sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72cis 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. 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, carryingdenied = true; the key stops verifying at the next load,plugin trust listshows 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 intests/packages/first-party.fingerprint, and a build that predates the rotation will not trust it.You may anchor it yourself instead —
code-index plugin trust add code-index-publisher.pub --fingerprint sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72c --name 'a label you choose', withcode-index-publisher.pubfrom this release's assets. Your file replaces the compiled-in entry, and the--nameis a label YOU choose: nothing in the package, the key file or the signature can name its own publisher.macOS is not currently built. No
x86_64-apple-darwinoraarch64-apple-darwinarchive 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
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- the archive is smoked with its own shipped bytes before publication, and
-
code-index v0.26.1
StableAll checks were successfulCI / cargo fmt (push) Successful in 46sCI / Grammar rebuild from source (weekly) (push) Has been skippedCI / OSS corpus tier-3 scale (weekly) (push) Has been skippedCI / cargo test (abi, 32-bit + wasm32) (push) Successful in 3m58sCI / cargo doc (intra-doc links) (push) Successful in 4m22sCI / cargo clippy (push) Successful in 5m1sCI / cargo check (MSRV 1.98) (push) Successful in 5m27sCI / cargo check (windows-gnu) (push) Successful in 5m39sCI / cargo deny (push) Successful in 5m55sCI / OSS corpus (tier 1) (push) Successful in 15m20sCI / cargo test (push) Successful in 17m51sCI / cargo test (daemon transport) (push) Successful in 6m32sCI / Plugin path cost + pool throughput (weekly) (push) Has been skippedCI (Windows) / fmt + clippy + build + test (windows) (push) Successful in 35m57sRelease Build / Generate Version (push) Successful in 27sRelease Build / Required CI green (push) Successful in 48sRelease Build / Build linux-aarch64 (push) Successful in 12m36sRelease Build / Build windows-x86_64 (push) Successful in 13m27sRelease Build / Build linux-x86_64 (push) Successful in 15m22sRelease Build / Build linux-x86_64-musl (push) Successful in 15m56sRelease Build / Pack the XAML reference package (push) Successful in 52sRelease Build / Create Forgejo Release (push) Successful in 2m52sreleased this
2026-09-04 10:05:07 +02:00 | 2054 commits to master since this releasecode-index v0.26.1
Build: v0.26.1+574
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(sandboxed worker for plugin packages, spawned by the daemon), andcode-index(CLI: init, index, watch, doctor, link, plugin).Every fix here is the same shape: a state the product could observe but
had no way to report, so it reported the neighbouring state instead. All
three were found by dogfooding v0.26.0 against this repository.Mistyped arguments now answer like every other argument error
An MCP tool called with a wrong argument NAME has always answered with a
structured error naming every accepted argument. A wrong argument TYPE
did not: it fell through to the framework's own text —failed to deserialize parameters: invalid type: string "...", expected a sequenceno error code, no hint, and not JSON at all, so a client that parses one
could not parse the other. That is exactly the mistake a caller makes:
passing a single value where a LIST is wanted, for arguments like
task_terms,symbol_ids,handlesandpathswhose names read like
they take one.A MISSING required argument had the same problem, one shape further
along:find_callerswith no arguments answered
failed to deserialize parameters: missing field \symbol_id``.All three now answer in one envelope, read off the SAME published schema
at the SAME boundary — so every registered tool and every declared
argument is covered by construction, including the element types inside
a list, and a tool added tomorrow is covered the day it is registered.The three are ordered by how much of your call is knowable, and the
order is deliberate rather than incidental:- an UNDECLARED argument, which has no declared type to be wrong
against and no bearing on what is required — and a misspelled
required argument is both defects at once, where naming both sides
beats naming one; - a MISSING required argument, because no amount of fixing types
makes an incomplete call run; - a WRONG TYPE, once the call is complete.
Presence is not value: a required argument supplied as
nullis
present, and is graded as a type. The two gates do not overlap.The leash actually holds on Windows
code-index's test harness ties every daemon it spawns to the process
that spawned it, so none outlives its fixture. On Windows that tie did
NOTHING —attachreturned an inert handle andkill_grouphad an
empty body — and the suite that would have caught it was Unix-only, so
the Windows leg reportedrunning 0 tests. No implementation and no
coverage, neither able to fail.Windows now gets a real Job Object: the job is created BEFORE the child,
the child is started suspended and assigned while it is still frozen —
so a grandchild it has not spawned yet cannot escape — and
KILL_ON_JOB_CLOSEmakes the operating system the killer, which is
stricter than the Unix side, where a nanny process exists only because a
Dropdoes not run when the holder is killed outright.A leash that CANNOT be established now says so, carrying what the OS
reported, instead of being indistinguishable from one that was never
asked for. The same conflation was fixed on Unix, where a child that
leads no process group was also silently reported as "inert".This matters to you only if you run the test suite; it is why a Windows
CI run could leave daemons behind.An admission that no rule proved says which it was
The file watcher admits a path when nothing proves it should be skipped.
There are two ways to reach that: the ignore rules were consulted and
allowed it, or the path's relation to the project root could not be
parsed at all, so no rule was ever applied. Those were the same number.They are now distinguishable. The verdict is UNCHANGED — an unparseable
path is still admitted, deliberately, because reporting it as
"deliberately excluded" would be its own lie — and a test now pins that
so a future "repair" cannot quietly invert it.Also
The release pipeline could not publish its own notes. Two defects, both
of which produce a release whose changelog is not what its author wrote:actions/checkoutresolves a tag to the COMMIT it points at, so the
annotation is absent in the runner even when the remote holds a real
tag object. The tag ref is now re-fetched before the notes are read.git tag -Fruns git's default cleanup, which strips every line
beginning with#— deleting every markdown heading from a notes
file, silently. The pipeline now refuses notes with no heading and
names--cleanup=verbatimas the repair.
v0.25.0 shipped an internal narrative about zombie processes as its
changelog because of the first of these. v0.26.0 caught it and refused
to publish rather than publish the wrong text.Upgrading
No action required, and no index schema change.
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.26.1-linux-x86_64.tar.gz Linux x86_64 (static/musl) code-index-v0.26.1-linux-x86_64-musl.tar.gz Linux ARM64 code-index-v0.26.1-linux-aarch64.tar.gz Windows x64 code-index-v0.26.1-windows-x86_64.zip XAML plugin package
de.h-dv.xaml-0.1.0.cipmakes.xamlfiles carry symbols and references instead of being text-only:x:ClassandClick=handlers bind into the paired C# code-behind,x:Namebecomes a searchable declaration, and{Binding …}stays unresolved because no bridge can reach it.It is NOT installed by installing code-index. Packages are installed into a user-controlled store and approved per project, and installing grants nothing —
enableis the grant.Download
de.h-dv.xaml-0.1.0.cipstoo and keep the.cipsbeside the.cip. Packages are signed and an unsigned one is refused (signature_missing) with no flag that accepts it. You do NOT need to anchor us first: this release's publisher key is compiled into the binary, so the install below works on a machine that has anchored nobody.code-index plugin trust listshows it, marked[BUILTIN], andcode-index plugin trust remove sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72cwithdraws it — see About that key.code-index plugin install de.h-dv.xaml-0.1.0.cip --sha256 sha256:584fe7183b234e7133fa7d257cc8a8d687f38bfb43d235cfda657ba13b1186dd code-index plugin check sha256:584fe7183b234e7133fa7d257cc8a8d687f38bfb43d235cfda657ba13b1186dd code-index plugin enable sha256:584fe7183b234e7133fa7d257cc8a8d687f38bfb43d235cfda657ba13b1186dd \ --capabilities bridge_source \ --bridges 'de.h-dv.xaml/xaml:type->csharp:class,de.h-dv.xaml/xaml:call->csharp:method'The digest above is the one this release packed and it is what
--sha256pins;de.h-dv.xaml-0.1.0.cip.digest.txtcarries it and the extraction identity. A digest that changes between releases means the package changed — re-pin, and read the notes.Only
.xamlis claimed..datasetand other markup remain text-only (searchable, no symbols).About that key
sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72cis 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. 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, carryingdenied = true; the key stops verifying at the next load,plugin trust listshows 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 intests/packages/first-party.fingerprint, and a build that predates the rotation will not trust it.You may anchor it yourself instead —
code-index plugin trust add code-index-publisher.pub --fingerprint sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72c --name 'a label you choose', withcode-index-publisher.pubfrom this release's assets. Your file replaces the compiled-in entry, and the--nameis a label YOU choose: nothing in the package, the key file or the signature can name its own publisher.macOS is not currently built. No
x86_64-apple-darwinoraarch64-apple-darwinarchive 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
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- an UNDECLARED argument, which has no declared type to be wrong
-
code-index v0.26.0
StableAll checks were successfulCI / cargo fmt (push) Successful in 46sCI / OSS corpus tier-3 scale (weekly) (push) Has been skippedCI / Grammar rebuild from source (weekly) (push) Has been skippedCI / cargo test (abi, 32-bit + wasm32) (push) Successful in 4m21sCI / cargo doc (intra-doc links) (push) Successful in 4m26sCI / cargo deny (push) Successful in 5m26sCI / cargo check (MSRV 1.98) (push) Successful in 5m35sCI / cargo clippy (push) Successful in 5m51sCI / cargo check (windows-gnu) (push) Successful in 5m54sCI / OSS corpus (tier 1) (push) Successful in 15m50sCI / cargo test (push) Successful in 18m22sCI / cargo test (daemon transport) (push) Successful in 6m44sCI / Plugin path cost + pool throughput (weekly) (push) Has been skippedCI (Windows) / fmt + clippy + build + test (windows) (push) Successful in 38m3sRelease Build / Generate Version (push) Successful in 19sRelease Build / Required CI green (push) Successful in 58sRelease Build / Build linux-aarch64 (push) Successful in 13m2sRelease Build / Build windows-x86_64 (push) Successful in 13m48sRelease Build / Build linux-x86_64 (push) Successful in 15m59sRelease Build / Build linux-x86_64-musl (push) Successful in 16m26sRelease Build / Pack the XAML reference package (push) Successful in 50sRelease Build / Create Forgejo Release (push) Successful in 2m56sreleased this
2026-09-04 08:43:11 +02:00 | 2056 commits to master since this releasecode-index v0.26.0
Build: v0.26.0+571
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(sandboxed worker for plugin packages, spawned by the daemon), andcode-index(CLI: init, index, watch, doctor, link, plugin).Activation on demand
A project holds
.xamlfiles. You installed and enabled that package
for a DIFFERENT project last week. Until now this one handed you
text-only rows and said nothing about it.code-index now detects that case and tells you: a package in your store
whose manifest claims an extension this project actually holds files
for, and whose digest this project has not approved. The census is the
same populationsymbol_blind_extensionsreports, so the two cannot
disagree with each other.Where you have ALREADY approved that exact digest in another project,
the row is enabled without asking, and the grant written is the
INTERSECTION of what you granted there with what the package requests
here — never wider. Where there is no such basis it is OFFERED, not
enabled: the first grant of a package stays a human decision, on every
machine. A.cipfound inside the repository never auto-enables, because
cloning a repository must not activate code.A disable outranks the offer.
plugin disablenow writes a
tombstone, and nothing in the machinery above can clear it — so a
package you turned off here stays off, and theundo_commandthe
disclosure names actually holds. (Nothing re-granted a disabled row in
v0.25.0 either: there was no automatic enable at all. The tombstone is
what makes the new behaviour safe, not a repair to the old one.)The daemon leaves an account of itself
A daemon spawned by the MCP server runs with stdout and stderr on the
floor, so for the whole life of any startup defect there was nothing to
read. It now writesdaemon.logbeside its lockfile — bounded, with one
rotated backup — and the client's "did not become ready" error names the
path. The capability token is never written to it.Windows: your approval records move, by themselves
Read this if you run code-index on Windows. The key that names an
approval record was derived fromcanonicalize()'s output when the
project directory resolved, and from the raw path when it did not —
two different spellings of one project, because a record stores the
plain root whilecanonicalizereturns the\\?\form.That was not theoretical. The key IS the record's filename, so any
moment a project directory was not resolvable — a disconnected network
share, an unmounted volume, a detached disk — the lookup computed a
different key, found nothing, and every grant that project held appeared
to have vanished. They came back when the share reconnected.The key is corrected, and records already on your disk are MIGRATED to
it on the first read or write. Nothing is asked of you and no grant is
lost: if the store cannot be written to, the record is still read at its
old name. Other platforms are unaffected — their two spellings were
always identical, so no file moves there.For package authors
A guest can now map a kind NAME to a kind id without a new host call.
Guests run with an EMPTY IMPORT LIST — that emptiness is what makes
fork,openandconnectinexpressible — so a guest cannot ask "what
number isfunction_item?". It now asserts and the host checks: the
guest exports one immutablekind_table_digest, and the worker
enumerates the grammar it just loaded, in the same process that writes
those ids, refusing on mismatch with exit 24 and printing the number the
guest should have carried. The zero-import property is measured by
counting the module's imports, not asserted in prose.attr_start_linenow has a wire representation, andis_extensionis
deliberately still dropped: admitting it means authorising a package
into the C# extension-method binding pool, which is a capability
decision rather than a mapping one, and it is left as one.When a store holds more than one approved, resolvable digest of the same
package id, only one of them can be live. Which one that is, and which
digests it displaced, are now reported — previously the others simply
did not run and nothing said so.Also
read_codewith a mistyped range —path:60,200, a comma for the
hyphen — answeredinternal_errorand advised you to check whether
the daemon or index DB was down. It now answersinvalid_targetand
gives the syntax.
Upgrading
No action required, on any platform.
No index schema change — nothing is re-indexed and no migration runs
over your database;git diff v0.25.0..v0.26.0touches no migration.
The only thing that moves is the Windows approval record, on first use,
and that is idempotent.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.26.0-linux-x86_64.tar.gz Linux x86_64 (static/musl) code-index-v0.26.0-linux-x86_64-musl.tar.gz Linux ARM64 code-index-v0.26.0-linux-aarch64.tar.gz Windows x64 code-index-v0.26.0-windows-x86_64.zip XAML plugin package
de.h-dv.xaml-0.1.0.cipmakes.xamlfiles carry symbols and references instead of being text-only:x:ClassandClick=handlers bind into the paired C# code-behind,x:Namebecomes a searchable declaration, and{Binding …}stays unresolved because no bridge can reach it.It is NOT installed by installing code-index. Packages are installed into a user-controlled store and approved per project, and installing grants nothing —
enableis the grant.Download
de.h-dv.xaml-0.1.0.cipstoo and keep the.cipsbeside the.cip. Packages are signed and an unsigned one is refused (signature_missing) with no flag that accepts it. You do NOT need to anchor us first: this release's publisher key is compiled into the binary, so the install below works on a machine that has anchored nobody.code-index plugin trust listshows it, marked[BUILTIN], andcode-index plugin trust remove sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72cwithdraws it — see About that key.code-index plugin install de.h-dv.xaml-0.1.0.cip --sha256 sha256:584fe7183b234e7133fa7d257cc8a8d687f38bfb43d235cfda657ba13b1186dd code-index plugin check sha256:584fe7183b234e7133fa7d257cc8a8d687f38bfb43d235cfda657ba13b1186dd code-index plugin enable sha256:584fe7183b234e7133fa7d257cc8a8d687f38bfb43d235cfda657ba13b1186dd \ --capabilities bridge_source \ --bridges 'de.h-dv.xaml/xaml:type->csharp:class,de.h-dv.xaml/xaml:call->csharp:method'The digest above is the one this release packed and it is what
--sha256pins;de.h-dv.xaml-0.1.0.cip.digest.txtcarries it and the extraction identity. A digest that changes between releases means the package changed — re-pin, and read the notes.Only
.xamlis claimed..datasetand other markup remain text-only (searchable, no symbols).About that key
sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72cis 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. 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, carryingdenied = true; the key stops verifying at the next load,plugin trust listshows 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 intests/packages/first-party.fingerprint, and a build that predates the rotation will not trust it.You may anchor it yourself instead —
code-index plugin trust add code-index-publisher.pub --fingerprint sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72c --name 'a label you choose', withcode-index-publisher.pubfrom this release's assets. Your file replaces the compiled-in entry, and the--nameis a label YOU choose: nothing in the package, the key file or the signature can name its own publisher.macOS is not currently built. No
x86_64-apple-darwinoraarch64-apple-darwinarchive 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
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-
code-index v0.25.0
StableAll checks were successfulCI / cargo fmt (push) Successful in 45sCI / Grammar rebuild from source (weekly) (push) Has been skippedCI / OSS corpus tier-3 scale (weekly) (push) Has been skippedCI / cargo doc (intra-doc links) (push) Successful in 4m22sCI / cargo test (abi, 32-bit + wasm32) (push) Successful in 4m28sCI / cargo clippy (push) Successful in 5m24sCI / cargo check (MSRV 1.98) (push) Successful in 5m28sCI / cargo check (windows-gnu) (push) Successful in 5m35sCI / cargo deny (push) Successful in 6m15sCI / OSS corpus (tier 1) (push) Successful in 15m10sCI / cargo test (push) Successful in 16m52sCI / cargo test (daemon transport) (push) Successful in 6m11sCI / Plugin path cost + pool throughput (weekly) (push) Has been skippedCI (Windows) / fmt + clippy + build + test (windows) (push) Successful in 32m42sRelease Build / Generate Version (push) Successful in 18sRelease Build / Required CI green (push) Successful in 56sRelease Build / Build linux-aarch64 (push) Successful in 12m55sRelease Build / Build windows-x86_64 (push) Successful in 13m5sRelease Build / Build linux-x86_64 (push) Successful in 15m41sRelease Build / Build linux-x86_64-musl (push) Successful in 15m44sRelease Build / Pack the XAML reference package (push) Successful in 52sRelease Build / Create Forgejo Release (push) Successful in 2m49sreleased this
2026-09-03 08:43:46 +02:00 | 2062 commits to master since this releasecode-index v0.25.0
Build: v0.25.0+556
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(sandboxed worker for plugin packages, spawned by the daemon), andcode-index(CLI: init, index, watch, doctor, link, plugin).Our key ships in the binary, and an agent can ask to install a plugin.
Installing a package we publish takes one command
v0.24.1 made packages verifiable and, in doing so, made anchoring a
publisher the FIRST thing a new operator had to do — atrust add
with a fingerprint fetched through a second channel, before an install
that would otherwise refuse. Correct, and the wrong first impression:
the ceremony that protects you from a stranger was charged to you for
a package that arrived inside the same archive as the program.The first-party key is now compiled into the binaries.
plugin trust listshows it as[BUILTIN].plugin add de.h-dv.xaml-0.1.0.cipworks on a machine with an empty trust store.It extends no trust you had not already extended — forging that anchor
means forging the binary you are running — and anchoring a THIRD-PARTY
publisher is still the deliberate act it was.It is revocable, offline, like any other key.
plugin trust remove <fingerprint>on a built-in WRITES a denial into your trust directory
rather than deleting a file that is not there, and the key stops
verifying at the next load. Which mechanic runs is decided from the
compiled-in bytes and never from a file's ownbuiltinflag, so a
hand-edited anchor can neither turn the withdrawal into a no-op nor
let a delete quietly restore trust.The fingerprint stays
sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72c.
It is compiled in, committed intests/packages/first-party.fingerprint,
printed in these notes, and a gate compares all three — plus one that
asserts the SHIPPED BINARY lists it, so drift is caught in the artifact
and not only in the tree.plugin_addover MCPThe CLI half shipped in v0.24.1; this is the other half, and its
security property is different. On a terminal the human is the caller.
Over MCP the caller is an agent that reads the repository — the
untrusted party.So there is no approving argument. Inventing one is refused by the
unknown-argument gate rather than dropped silently. Agrantis a
REQUEST; only the elicitation is an answer. A client declaring no
elicitation capability getsconfirmation_unavailable— no fallback
and no auto-approve, because a tool that proceeds when there is nobody
to ask is worse than one that does not exist. Decline, cancel and
timeout all leave the user root and the project byte-identical.The daemon says when it has not looked yet
project_overviewcould answer from the database while the live
package set was still being discovered, and the reply was
indistinguishable from a healthy project's: an active generation, a
covered file, and the two package fields simply MISSING because both
are omitted when absent. Measured at 9 failures in 10 runs under load.The daemon binding its listener before discovery finishes is the
design. Not saying so was the defect.package_set_consultedis now
on the block:falsemeans nobody has looked yet — ask again — and
carries the prose explaining it;truemeans an absent package field
is a MEASUREMENT; absent still means a daemon that does not report it.index_hosthad the same shape one level down: a worker binary that
disappeared between twostats produced a silent builtins-only pass
wearing a line that read as a measurement, in the one state the pass
policy exists to refuse. It re-measures and re-applies that policy now
rather than deciding a second time.Three binaries stopped shipping a wasm compiler
nm -Con the release's own build found 441 cranelift symbols in
code-index,code-index-daemonandcode-index-mcp. Cargo unifies
features across the packages selected in ONE invocation, and
code-index-plugin-hostneedstree-sitter'swasmfeature. The
release builds in two invocations now; shared dependencies compile
twice, which is the price of three binaries not carrying a JIT.Getting the package
code-index plugin add de.h-dv.xaml-0.1.0.cipNo
trust addfirst. Keep the.cipsbeside the.cip.A signature says these bytes are the ones we signed. It does not say
they are safe.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.25.0-linux-x86_64.tar.gz Linux x86_64 (static/musl) code-index-v0.25.0-linux-x86_64-musl.tar.gz Linux ARM64 code-index-v0.25.0-linux-aarch64.tar.gz Windows x64 code-index-v0.25.0-windows-x86_64.zip XAML plugin package
de.h-dv.xaml-0.1.0.cipmakes.xamlfiles carry symbols and references instead of being text-only:x:ClassandClick=handlers bind into the paired C# code-behind,x:Namebecomes a searchable declaration, and{Binding …}stays unresolved because no bridge can reach it.It is NOT installed by installing code-index. Packages are installed into a user-controlled store and approved per project, and installing grants nothing —
enableis the grant.Download
de.h-dv.xaml-0.1.0.cipstoo and keep the.cipsbeside the.cip. Packages are signed and an unsigned one is refused (signature_missing) with no flag that accepts it. You do NOT need to anchor us first: this release's publisher key is compiled into the binary, so the install below works on a machine that has anchored nobody.code-index plugin trust listshows it, marked[BUILTIN], andcode-index plugin trust remove sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72cwithdraws it — see About that key.code-index plugin install de.h-dv.xaml-0.1.0.cip --sha256 sha256:584fe7183b234e7133fa7d257cc8a8d687f38bfb43d235cfda657ba13b1186dd code-index plugin check sha256:584fe7183b234e7133fa7d257cc8a8d687f38bfb43d235cfda657ba13b1186dd code-index plugin enable sha256:584fe7183b234e7133fa7d257cc8a8d687f38bfb43d235cfda657ba13b1186dd \ --capabilities bridge_source \ --bridges 'de.h-dv.xaml/xaml:type->csharp:class,de.h-dv.xaml/xaml:call->csharp:method'The digest above is the one this release packed and it is what
--sha256pins;de.h-dv.xaml-0.1.0.cip.digest.txtcarries it and the extraction identity. A digest that changes between releases means the package changed — re-pin, and read the notes.Only
.xamlis claimed..datasetand other markup remain text-only (searchable, no symbols).About that key
sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72cis 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. 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, carryingdenied = true; the key stops verifying at the next load,plugin trust listshows 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 intests/packages/first-party.fingerprint, and a build that predates the rotation will not trust it.You may anchor it yourself instead —
code-index plugin trust add code-index-publisher.pub --fingerprint sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72c --name 'a label you choose', withcode-index-publisher.pubfrom this release's assets. Your file replaces the compiled-in entry, and the--nameis a label YOU choose: nothing in the package, the key file or the signature can name its own publisher.macOS is not currently built. No
x86_64-apple-darwinoraarch64-apple-darwinarchive 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
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-
Source code (ZIP)
-
code-index v0.24.1
StableAll checks were successfulCI / cargo fmt (push) Successful in 46sCI / OSS corpus tier-3 scale (weekly) (push) Has been skippedCI / Grammar rebuild from source (weekly) (push) Has been skippedCI / cargo test (abi, 32-bit + wasm32) (push) Successful in 4m13sCI / cargo doc (intra-doc links) (push) Successful in 5m7sCI / cargo check (MSRV 1.98) (push) Successful in 5m15sCI / cargo clippy (push) Successful in 5m16sCI / cargo check (windows-gnu) (push) Successful in 5m51sCI / cargo deny (push) Successful in 6m45sCI / OSS corpus (tier 1) (push) Successful in 15m35sCI / cargo test (push) Successful in 16m48sCI / cargo test (daemon transport) (push) Successful in 5m18sCI / Plugin path cost + pool throughput (weekly) (push) Has been skippedCI (Windows) / fmt + clippy + build + test (windows) (push) Successful in 32m36sRelease Build / Generate Version (push) Successful in 17sRelease Build / Required CI green (push) Successful in 1m0sRelease Build / Build linux-aarch64 (push) Successful in 12m59sRelease Build / Build windows-x86_64 (push) Successful in 13m6sRelease Build / Build linux-x86_64 (push) Successful in 15m56sRelease Build / Build linux-x86_64-musl (push) Successful in 16m21sRelease Build / Pack the XAML reference package (push) Successful in 46sRelease Build / Create Forgejo Release (push) Successful in 3m1sreleased this
2026-09-02 18:04:41 +02:00 | 2067 commits to master since this releasecode-index v0.24.1
Build: v0.24.1+546
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(sandboxed worker for plugin packages, spawned by the daemon), andcode-index(CLI: init, index, watch, doctor, link, plugin).Signed packages, and the one command that installs one.
v0.24.0 published a
.cipfor the first time. This release makes it
verifiable — and, unavoidably, makes v0.24.0's copy permanently
uninstallable: it was published unsigned, and no later release can
retroactively sign bytes that are already out. Take the package from
this release instead.Signing
Ed25519 over the package digest, in a detached
.cips. Signing the
digest rather than the container means the signature check and the
digest check are the same check, so no path exists where a signature
verifies over bytes the digest did not cover.The store verifies at BOTH doors.
Store::getmatters as much as
install, because trust is not a constant:plugin trust removemeans
stop running what that key signed, and that can only take effect where
the signature is re-examined against the current trust set.Unsigned is refused, with no
--allow-unsigned— a named downgrade is
the state everyone ends up in. The escape hatch is three local
commands and the refusal names them.ed25519-compact's verify does not cover the small-order key family;
measured, an order-8 key with a zero scalar verifies roughly three
messages in four. The parser screens keys itself, and the test asserts
both that we refuse and that the library alone would not — so the
workaround can be retired on evidence rather than on faith.One command
plugin addreplaces four commands and a hand-assembled bridge
string. Nothing is written before the answer: it verifies, measures
the reindex domain, and shows one block naming the publisher from your
own trust label and all three effects — installs bytes, RUNS the
package sandboxed against its own fixtures, grants for this project
only. Bare Enter is no.--yesrequires an explicit--grant, and that clause is the whole
difference between a pre-filled answer and a delegation.Honesty
A zero now says which of three things it is: measured, structurally
unmeasurable, or filtered away by an argument the reply now names. And
an agent asking why a plugin stopped working can tell "lost its
signature" from "never installed" — two states with different repairs,
which is why they do not share a code.Getting the package
code-index plugin trust add code-index-publisher.pub \ --fingerprint sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72c \ --name '<your label for us>' code-index plugin add de.h-dv.xaml-0.1.0.cipAnchoring is a decision about a PUBLISHER, not a package, and it is
the one step that should happen at a keyboard. The fingerprint above
is published here and committed in the repository precisely so it
reaches you by a channel other than the key file: a fingerprint you
compute from the file in front of you agrees with itself and proves
nothing.A signature says these bytes are the ones we signed. It does not say
they are safe.Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_01K1zj5VcFJvJt3pQxe9259KDownloads
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.24.1-linux-x86_64.tar.gz Linux x86_64 (static/musl) code-index-v0.24.1-linux-x86_64-musl.tar.gz Linux ARM64 code-index-v0.24.1-linux-aarch64.tar.gz Windows x64 code-index-v0.24.1-windows-x86_64.zip XAML plugin package
de.h-dv.xaml-0.1.0.cipmakes.xamlfiles carry symbols and references instead of being text-only:x:ClassandClick=handlers bind into the paired C# code-behind,x:Namebecomes a searchable declaration, and{Binding …}stays unresolved because no bridge can reach it.It is NOT installed by installing code-index. Packages are installed into a user-controlled store and approved per project, and installing grants nothing —
enableis the grant.Download
de.h-dv.xaml-0.1.0.cipsandcode-index-publisher.pubtoo, and keep the.cipsbeside the.cip. Packages are signed and an unsigned one is refused (signature_missing) with no flag that accepts it, so anchoring the publisher is the FIRST command and not an optional one — an install run before it refuses withsignature_untrusted:code-index plugin trust add code-index-publisher.pub --fingerprint sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72c --name 'h-dv (first party)' code-index plugin install de.h-dv.xaml-0.1.0.cip --sha256 sha256:584fe7183b234e7133fa7d257cc8a8d687f38bfb43d235cfda657ba13b1186dd code-index plugin check sha256:584fe7183b234e7133fa7d257cc8a8d687f38bfb43d235cfda657ba13b1186dd code-index plugin enable sha256:584fe7183b234e7133fa7d257cc8a8d687f38bfb43d235cfda657ba13b1186dd \n --capabilities bridge_source \n --bridges 'de.h-dv.xaml/xaml:type->csharp:class,de.h-dv.xaml/xaml:call->csharp:method'The digest above is the one this release packed and it is what
--sha256pins;de.h-dv.xaml-0.1.0.cip.digest.txtcarries it and the extraction identity. A digest that changes between releases means the package changed — re-pin, and read the notes.Only
.xamlis claimed..datasetand other markup remain text-only (searchable, no symbols).About that key
sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72cis a long-lived Ed25519 key held as a secret in this project's CI, used to sign released packages automatically. Anchoring it means trusting 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. There is no expiry — deliberately, because offline installations must not break on a timer — so withdrawal is manual and on your side:code-index plugin trust remove sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72c. If this key is ever rotated or withdrawn, the new fingerprint is published in the release notes and intests/packages/first-party.fingerprint, and every machine has to runplugin trust addagain.An anchor is machine-wide and it is yours: the
--nameabove is a label YOU choose, and nothing in the package, the key file or the signature can name its own publisher.macOS is not currently built. No
x86_64-apple-darwinoraarch64-apple-darwinarchive 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
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-
Source code (ZIP)
-
code-index v0.24.0
StableSome checks failedCI / cargo fmt (push) Successful in 47sCI / OSS corpus tier-3 scale (weekly) (push) Has been skippedCI / Grammar rebuild from source (weekly) (push) Has been skippedCI / cargo test (abi, 32-bit + wasm32) (push) Successful in 4m3sCI / cargo doc (intra-doc links) (push) Successful in 4m24sCI / cargo clippy (push) Successful in 5m11sCI / cargo check (MSRV 1.98) (push) Successful in 5m20sCI / cargo check (windows-gnu) (push) Successful in 5m46sCI / cargo deny (push) Successful in 5m57sCI / OSS corpus (tier 1) (push) Successful in 15m47sCI / cargo test (push) Successful in 16m55sCI / cargo test (daemon transport) (push) Successful in 5m20sCI / Plugin path cost + pool throughput (weekly) (push) Has been skippedCI (Windows) / fmt + clippy + build + test (windows) (push) Successful in 35m5sRelease Build / Generate Version (push) Successful in 26sRelease Build / Required CI green (push) Successful in 47sRelease Build / Build linux-x86_64-musl (push) Failing after 19sRelease Build / Build linux-aarch64 (push) Successful in 11m18sRelease Build / Build windows-x86_64 (push) Successful in 12m2sRelease Build / Build linux-x86_64 (push) Successful in 14m7sRelease Build / Pack the XAML reference package (push) Successful in 51sRelease Build / Create Forgejo Release (push) Successful in 2m17sreleased this
2026-09-02 09:33:19 +02:00 | 2077 commits to master since this releasecode-index v0.24.0
Build: v0.24.0+538
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(sandboxed worker for plugin packages, spawned by the daemon), andcode-index(CLI: init, index, watch, doctor, link, plugin).Epic #75's runtime plugin architecture, phase 4 (#80), plus the review
round that followed it and the fixes that round demanded.The customer-facing change is that the XAML plugin can now be
obtained: the reference package is packed in CI by the shipped binary
and published beside the archives with its digest. No release has ever
carried one.Security, all of it found by asking what the shipped binary actually
contains: eighteendebug_assert!s guarded invariants that do not
exist under--release, and two of them mattered — the binary
installed a seccomp filter that ALLOWEDsocket, and it minted
builtin language ids that reachgrant_all.derived_nameis now an
authority a project grants rather than one every package holds, with a
detection bit so a fabricated edge can be enumerated after the fact.
Three package-path guards became refusals.Honesty:
plugin rollbackrefuses instead of exiting zero on a
rollback it did not perform;context_pack'swith_sourceis
measured rather than derived behind an assertion release deletes;
refs_resolvedreports the rows the resolver actually changed.Gates the round added because it needed them: a rustdoc gate (backlog
131 -> 0, five genuinely broken citations inside it), a README gate
that caught this very version bump, a fork lock covering whole test
targets, and three cost bounds on the plugin path — which nothing
could see before, because the corpus ratchet counts SQLite opcodes and
the corpus installs no packages.Measured, since the direction rests on it: a language plugin's wire
cost is additive at ~3.5-4% of a real file, and a plugin fleet runs at
0.97-1.09x of builtins at machine width.Verified: fmt, clippy (host + windows-gnu), rustdoc at zero warnings,
cargo check --locked, MSRV 1.98, 2448 tests, daemon transport leg,
precision_gate 7/7 phantom_count 0, release_gate, corpus ratchet with
baseline.json unmoved at 534084b856c22566c48e386bc41ed67e and never
blessed.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.24.0-linux-x86_64.tar.gz Linux x86_64 (static/musl) not published for this release Linux ARM64 code-index-v0.24.0-linux-aarch64.tar.gz Windows x64 code-index-v0.24.0-windows-x86_64.zip No static (musl) archive was published for v0.24.0. That leg is best-effort: it either failed to build or its
code-index-plugin-hostfailed the release plugin smoke/timeout/trap test, and an archive whose plugin host has not been proved on its own target is not one this project ships. Use the glibc archive.XAML plugin package
de.h-dv.xaml-0.1.0.cipmakes.xamlfiles carry symbols and references instead of being text-only:x:ClassandClick=handlers bind into the paired C# code-behind,x:Namebecomes a searchable declaration, and{Binding …}stays unresolved because no bridge can reach it.It is NOT installed by installing code-index. Packages are installed into a user-controlled store and approved per project, and installing grants nothing —
enableis the grant:code-index plugin install de.h-dv.xaml-0.1.0.cip --sha256 sha256:584fe7183b234e7133fa7d257cc8a8d687f38bfb43d235cfda657ba13b1186dd code-index plugin check sha256:584fe7183b234e7133fa7d257cc8a8d687f38bfb43d235cfda657ba13b1186dd code-index plugin enable sha256:584fe7183b234e7133fa7d257cc8a8d687f38bfb43d235cfda657ba13b1186dd \n --capabilities bridge_source \n --bridges 'de.h-dv.xaml/xaml:type->csharp:class,de.h-dv.xaml/xaml:call->csharp:method'The digest above is the one this release packed and it is what
--sha256pins;de.h-dv.xaml-0.1.0.cip.digest.txtcarries it and the extraction identity. A digest that changes between releases means the package changed — re-pin, and read the notes.Only
.xamlis claimed..datasetand other markup remain text-only (searchable, no symbols).macOS is not currently built. No
x86_64-apple-darwinoraarch64-apple-darwinarchive 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
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-
Source code (ZIP)
-
code-index v0.23.1
StableAll checks were successfulCI / cargo fmt (push) Successful in 46sCI / Grammar rebuild from source (weekly) (push) Has been skippedCI / OSS corpus tier-3 scale (weekly) (push) Has been skippedCI / cargo test (abi, 32-bit + wasm32) (push) Successful in 3m22sCI / cargo clippy (push) Successful in 4m14sCI / cargo check (windows-gnu) (push) Successful in 4m47sCI / cargo check (MSRV 1.98) (push) Successful in 4m47sCI / cargo deny (push) Successful in 5m20sCI / OSS corpus (tier 1) (push) Successful in 14m36sCI / cargo test (push) Successful in 16m9sCI / cargo test (daemon transport) (push) Successful in 5m7sCI (Windows) / fmt + clippy + build + test (windows) (push) Successful in 31m34sRelease Build / Generate Version (push) Successful in 18sRelease Build / Required CI green (push) Successful in 57sRelease Build / Build linux-aarch64 (push) Successful in 12m27sRelease Build / Build windows-x86_64 (push) Successful in 13m0sRelease Build / Build linux-x86_64-musl (push) Successful in 15m18sRelease Build / Build linux-x86_64 (push) Successful in 15m28sRelease Build / Create Forgejo Release (push) Successful in 2m20sreleased this
2026-09-01 15:52:21 +02:00 | 2096 commits to master since this releasecode-index v0.23.1
Build: v0.23.1+528
Three-binary release:
code-index-mcp(MCP stdio bridge — the usual entry),code-index-daemon(long-lived watcher + RPC server, auto-spawned), andcode-index(CLI: init, index, watch, doctor, link).Every fix from this session verified live against the freshly built and
installed 0.23.1 daemon: entry_points_total/truncated, the tier-1Q work
budget, runtime_quarantined_packages as null rather than zero,
extraction_diagnostics as [] rather than null, freshness_evidence
content_hash, and the search_text false negative that started the
pre-release review.AND A CORRECTION. B1c, B16, B18, B23, I24 and B27 all record that
search_text gives no per-file occurrence disclosure. It does: every hit
carries matches_in_file { count, lines[] }, and a live probe returns
count 18 for server.rs WITH all eighteen line numbers — exactly the
figure an agent measured by hand with grep and reported as unobtainable.git log -S puts that field in
eae7e09, 'fix: our own tools stop
reporting limits as findings', contained in v0.23.0 only. So six agents
were measuring the INSTALLED v0.22.3 daemon rather than the branch they
were writing code in. Row B22 predicted exactly this and it happened six
times anyway, because nobody applied it.What survives is narrower and still worth fixing: total is a FILE count
that reads as an occurrence count.By contrast the receiver-shape recall miss is REAL on the new build —
ClaimTable::route resolves 0 of 11 field-access call sites while its
sibling resolves — so that one stands. Same tool, same session,
opposite verdicts, each earned by measurement.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.23.1-linux-x86_64.tar.gz Linux x86_64 (static/musl) code-index-v0.23.1-linux-x86_64-musl.tar.gz Linux ARM64 code-index-v0.23.1-linux-aarch64.tar.gz Windows x64 code-index-v0.23.1-windows-x86_64.zip macOS is not currently built. No
x86_64-apple-darwinoraarch64-apple-darwinarchive 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
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-
Source code (ZIP)
-
code-index v0.22.3
StableAll checks were successfulCI / cargo fmt (push) Successful in 15sCI / OSS corpus tier-3 scale (weekly) (push) Has been skippedCI / cargo clippy (push) Successful in 2m33sCI / cargo check (windows-gnu) (push) Successful in 2m45sCI / cargo check (MSRV 1.88) (push) Successful in 2m47sCI / cargo deny (push) Successful in 3m27sCI / cargo test (push) Successful in 5m21sCI / OSS corpus (tier 1) (push) Successful in 10m17sCI / cargo test (daemon transport) (push) Successful in 3m1sCI (Windows) / fmt + clippy + build + test (windows) (push) Successful in 16m27sRelease Build / Generate Version (push) Successful in 16sRelease Build / Required CI green (push) Successful in 43sRelease Build / Build linux-x86_64-musl (push) Successful in 9m17sRelease Build / Build linux-x86_64 (push) Successful in 9m27sRelease Build / Build linux-aarch64 (push) Successful in 9m35sRelease Build / Build windows-x86_64 (push) Successful in 9m59sRelease Build / Create Forgejo Release (push) Successful in 1m52sreleased this
2026-08-26 13:40:42 +02:00 | 2270 commits to master since this releasecode-index v0.22.3
Build: v0.22.3+371
Three-binary release:
code-index-mcp(MCP stdio bridge — the usual entry),code-index-daemon(long-lived watcher + RPC server, auto-spawned), andcode-index(CLI: init, index, watch, doctor, link).Downloads
These four platforms are built and published for every release.
Platform Archive Linux x86_64 (glibc) code-index-v0.22.3-linux-x86_64.tar.gz Linux x86_64 (static/musl) code-index-v0.22.3-linux-x86_64-musl.tar.gz Linux ARM64 code-index-v0.22.3-linux-aarch64.tar.gz Windows x64 code-index-v0.22.3-windows-x86_64.zip macOS is not currently built. No
x86_64-apple-darwinoraarch64-apple-darwinarchive 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
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-
Source code (ZIP)
-
code-index v0.22.2
StableAll checks were successfulCI / cargo fmt (push) Successful in 16sCI / OSS corpus tier-3 scale (weekly) (push) Has been skippedCI / cargo clippy (push) Successful in 2m39sCI / cargo check (windows-gnu) (push) Successful in 2m58sCI / cargo check (MSRV 1.88) (push) Successful in 2m59sCI / cargo deny (push) Successful in 4m30sCI / OSS corpus (tier 1) (push) Successful in 9m40sCI / cargo test (push) Successful in 5m19sCI / cargo test (daemon transport) (push) Successful in 2m53sCI (Windows) / fmt + clippy + build + test (windows) (push) Successful in 15m35sRelease Build / Generate Version (push) Successful in 15sRelease Build / Required CI green (push) Successful in 50sRelease Build / Build linux-x86_64 (push) Successful in 5m28sRelease Build / Build linux-x86_64-musl (push) Successful in 5m32sRelease Build / Build windows-x86_64 (push) Successful in 5m38sRelease Build / Build linux-aarch64 (push) Successful in 5m53sRelease Build / Create Forgejo Release (push) Successful in 1m51sreleased this
2026-08-26 11:01:58 +02:00 | 2273 commits to master since this releasecode-index v0.22.2
Build: v0.22.2+366
Three-binary release:
code-index-mcp(MCP stdio bridge — the usual entry),code-index-daemon(long-lived watcher + RPC server, auto-spawned), andcode-index(CLI: init, index, watch, doctor, link).Downloads
These four platforms are built and published for every release.
Platform Archive Linux x86_64 (glibc) code-index-v0.22.2-linux-x86_64.tar.gz Linux x86_64 (static/musl) code-index-v0.22.2-linux-x86_64-musl.tar.gz Linux ARM64 code-index-v0.22.2-linux-aarch64.tar.gz Windows x64 code-index-v0.22.2-windows-x86_64.zip macOS is not currently built. No
x86_64-apple-darwinoraarch64-apple-darwinarchive 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
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-
Source code (ZIP)
-
code-index v0.22.1
StableAll checks were successfulRelease Build / Generate Version (push) Successful in 17sCI / cargo fmt (push) Successful in 36sCI / OSS corpus tier-3 scale (weekly) (push) Has been skippedCI / cargo clippy (push) Successful in 2m23sCI / cargo check (windows-gnu) (push) Successful in 2m44sCI / cargo check (MSRV 1.88) (push) Successful in 2m45sCI / cargo deny (push) Successful in 3m58sCI / cargo test (push) Successful in 5m17sCI / OSS corpus (tier 1) (push) Successful in 9m36sCI / cargo test (daemon transport) (push) Successful in 2m46sCI (Windows) / fmt + clippy + build + test (windows) (push) Successful in 15m16sRelease Build / Required CI green (push) Successful in 16m29sRelease Build / Build linux-x86_64 (push) Successful in 5m11sRelease Build / Build linux-x86_64-musl (push) Successful in 5m39sRelease Build / Build linux-aarch64 (push) Successful in 6m4sRelease Build / Build windows-x86_64 (push) Successful in 6m12sRelease Build / Create Forgejo Release (push) Successful in 1m51sreleased this
2026-08-26 09:17:06 +02:00 | 2276 commits to master since this releasecode-index v0.22.1
Build: v0.22.1+363
Three-binary release:
code-index-mcp(MCP stdio bridge — the usual entry),code-index-daemon(long-lived watcher + RPC server, auto-spawned), andcode-index(CLI: init, index, watch, doctor, link).Downloads
These four platforms are built and published for every release.
Platform Archive Linux x86_64 (glibc) code-index-v0.22.1-linux-x86_64.tar.gz Linux x86_64 (static/musl) code-index-v0.22.1-linux-x86_64-musl.tar.gz Linux ARM64 code-index-v0.22.1-linux-aarch64.tar.gz Windows x64 code-index-v0.22.1-windows-x86_64.zip macOS is not currently built. No
x86_64-apple-darwinoraarch64-apple-darwinarchive 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
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-
Source code (ZIP)