h-dv/code-index
Watch
4
0
Fork
You've already forked code-index
 0
Code Issues 46 Pull requests Projects Releases 98 Packages Wiki Activity Actions
98 releases 102 tags
  • v0.30.0 878fec1497

    code-index v0.30.0
    All checks were successful
    CI / cargo fmt (push) Successful in 49s
    Details
    CI / OSS corpus tier-3 scale (nightly) (push) Has been skipped
    Details
    CI / Grammar rebuild from source (nightly) (push) Has been skipped
    Details
    CI / cargo doc (intra-doc links) (push) Successful in 4m53s
    Details
    CI / cargo check (MSRV 1.98) (push) Successful in 6m12s
    Details
    CI / cargo deny (push) Successful in 6m16s
    Details
    CI / cargo test (abi, 32-bit + wasm32) (push) Successful in 6m29s
    Details
    CI / cargo clippy (push) Successful in 6m40s
    Details
    CI / cargo check (windows-gnu) (push) Successful in 6m47s
    Details
    CI / OSS corpus (tier 1) (push) Successful in 30m28s
    Details
    CI / cargo test (push) Successful in 41m8s
    Details
    CI (Windows) / fmt + clippy + build + test (windows) (push) Successful in 57m32s
    Details
    CI / cargo test (daemon transport) (push) Successful in 20m23s
    Details
    CI / Plugin path cost + pool throughput (nightly) (push) Has been skipped
    Details
    Release Build / Generate Version (push) Successful in 22s
    Details
    Release Build / Required CI green (push) Successful in 1m6s
    Details
    Release Build / Build linux-aarch64 (push) Successful in 12m58s
    Details
    Release Build / Build linux-x86_64 (push) Successful in 15m30s
    Details
    Release Build / Build linux-x86_64-musl (push) Successful in 16m18s
    Details
    Release Build / Pack the XAML reference package (push) Successful in 2m7s
    Details
    Release Build / Pack the Ruby language package (push) Successful in 2m14s
    Details
    Release Build / Pack the Svelte language package (push) Successful in 2m26s
    Details
    Release Build / Pack the TimeLine package (push) Successful in 2m38s
    Details
    Release Build / Build windows-x86_64 (push) Successful in 21m57s
    Details
    Release Build / Windows archive smoke (msvc) (push) Successful in 8s
    Details
    Release Build / Create Forgejo Release (push) Successful in 5m47s
    Details
    Stable

    buildagent released this 2026-09-17 12:49:42 +02:00 | 210 commits to master since this release

    code-index v0.30.0

    Build: v0.30.0+835

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

    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.30.0 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).

    ACTION REQUIRED: run code-index rules in every project

    Your agent instruction files are stale, and this release is what makes
    that fixable.

    I040 measured that "prefer code-index over shell search OR FILE READS"
    is a rule wrong in part — read_code("path:10-50") is one call exactly
    like sed -n — and that an agent given a rule wrong in part discards it
    WHOLE, taking the search half down with it. The mission rewrote the MCP
    server's own instructions and never touched the generator that writes
    AGENTS.md, .cursorrules, .windsurfrules, .clinerules,
    .github/copilot-instructions.md, .gemini/rules/ and
    .cursor/rules/. Those kept the harmful copy for four releases.

    It stayed invisible because rules could only ever be WRITTEN by
    code-index init, a first-run command. Nothing refreshed them, so every
    existing project is frozen on whatever shipped the day it was
    initialised.

    code-index rules            # refresh them
code-index rules --check    # exit 1 if stale; for CI

    CLAUDE.md and any shared file carrying your own guidance is left
    alone.

    New: ask the index from a shell

    code-index query --list
code-index query change_impact '{"symbol_ids":[900392]}'
code-index query search_text '{"query":"TODO"}' | jq .

    All 23 tools, JSON in and JSON out, with the disclosure envelope intact.
    Arguments come from the command line or from stdin with -.

    Every query tool used to exist only over MCP, so no hook, pre-commit, CI
    step or human could ask the index anything. Instructions are portable —
    one rule set, eight agent conventions — and enforcement was not, because
    a check has to run inside the runtime and no runtime speaks MCP.

    Exit codes are the contract: 0 answered, 1 the tool refused, 2 nothing
    was asked (no such tool, or arguments that are not a JSON object). The
    last two are separate on purpose: a hook that blocked a commit because a
    binary was missing, the same way it blocks one because the index found a
    problem, would be worse than no hook.

    New: a hook that tells you what depends on what you just changed

    code-index rules --hooks

    Installs a Claude Code PostToolUse hook. After an edit to a code file it
    asks which PUBLIC symbols in that file now differ and what depends on
    them:

    You changed `merge_rules` — public, and 12 symbol(s) depend on it.
  crates/cli/src/rules.rs :: write_agent_rules
  crates/cli/src/main.rs  :: cmd_rules
  …

    It is mostly a decision about when to stay quiet: a non-code file,
    nothing public changed, nothing depends on it, or the same finding
    already reported this session — all silent. A hook that speaks on every
    edit is one an agent learns to skip.

    Registered without disturbing anything else in .claude/settings.json,
    and a settings file that will not parse is refused rather than replaced.

    Fewer, larger calls

    query on search_text and search_symbols now takes a STRING OR A
    LIST — up to 8 searches in one call, each with its own batches entry.

    Measured over 702 real tool responses: the reply envelope is a FIXED
    ~1,130 characters per call and does not move with result count, so its
    share runs from 74% of a one-row answer down to 14% of a sixteen-row
    one. The lever was never shrinking disclosures — every mechanism for
    that was already built and deliberate — it was making fewer calls.

    Refusals rather than truncation: over the cap, an empty list, an empty
    entry and a cursor beside a batch are all refused, because a truncated
    batch answers nine questions with eight answers and the missing one
    reads as "found nothing".

    search_text names the symbol each hit sits inside

    search_text({query: "…", enclosing_symbol: true})

    "Nine call sites" is not something a reviewer can act on; "seven in
    render_activation, two in a test helper" is. Off by default.

    Windows

    A native Windows installer and updater (install.ps1), with the gates
    that make it real, plus three defects only a real Windows host could
    show.

    Svelte

    de.h-dv.svelte 0.1.0 — single-file components: markup, mustaches,
    {#snippet} and {@render}, on a new TAG_SYMBOL_BASENAME ABI input.

    Faster

    • a one-shot code-index query attaches to a running daemon or answers
      in-process, and never STARTS one. It was paying
      DAEMON_STARTUP_CEILING — fifteen minutes' worth of budget — for a
      question it answers in milliseconds. Measured on a Windows runner:
      ~10 minutes per invocation, now ~0.3s. The CI lane it was quietly
      consuming went from 2h53m to 56m.
    • read_file_claim's diagnostics subquery is pinned to the file_id
      index: 0.098s to 0.002s on 888 files, on a path that runs once per
      changed file.

    Disclosure

    code-index plugin now names the derived_names answer on the screen
    the operator approves, instead of leaving a granted capability
    unmentioned.

    Upgrading

    curl -fsSL https://git.h-dv.de/h-dv/code-index/raw/branch/master/install.sh | sh
# or, Windows:
iwr -useb https://git.h-dv.de/h-dv/code-index/raw/branch/master/install.ps1 | iex

    Then, in each project:

    code-index rules

    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.30.0-linux-x86_64.tar.gz
    Linux x86_64 (static/musl) code-index-v0.30.0-linux-x86_64-musl.tar.gz
    Linux ARM64 code-index-v0.30.0-linux-aarch64.tar.gz
    Windows x64 code-index-v0.30.0-windows-x86_64.zip

    XAML plugin package

    de.h-dv.xaml-0.2.0.cip makes .xaml files carry symbols and references instead of being text-only: x:Class and Click= handlers bind into the paired C# code-behind, x:Name becomes 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 — enable is the grant.

    Download de.h-dv.xaml-0.2.0.cips too and keep the .cips beside 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 list shows it, marked [BUILTIN], and code-index plugin trust remove sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72c withdraws 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 --sha256 pins; de.h-dv.xaml-0.2.0.cip.digest.txt carries it and the extraction identity. A digest that changes between releases means the package changed — re-pin, and read the notes.

    Only .xaml is claimed by this package. The TimeLine package below claims .dataset, .xsql, .shd and .lgd, and the Svelte package below claims .svelte; all other markup remains text-only (searchable, no symbols).

    TimeLine plugin package

    de.h-dv.timeline-0.1.0.cip makes the four TimeLine definition formats carry symbols and references instead of being text-only: .dataset and .xsql through one language, .shd and .lgd through another, both out of a single sandboxed extractor. References resolve INSIDE a definition file; nothing in v1 crosses into the C# that loads 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 — enable is the grant.

    Download de.h-dv.timeline-0.1.0.cips too and keep the .cips beside the .cip. The same signature rules apply as for the XAML package above, and the same key signs both.

    code-index plugin install de.h-dv.timeline-0.1.0.cip --sha256 sha256:150ceb22ed9757a660d5a2bf58b80c81b60043cc419e5da5dde559d5d6fc9c9f
code-index plugin check   sha256:150ceb22ed9757a660d5a2bf58b80c81b60043cc419e5da5dde559d5d6fc9c9f
code-index plugin enable  sha256:150ceb22ed9757a660d5a2bf58b80c81b60043cc419e5da5dde559d5d6fc9c9f \
    --capabilities same_file_candidate,exported_candidate

    No --bridges, and that is the package saying so: it declares none, so there is nothing to grant. The digest above is the one this release packed and it is what --sha256 pins; de.h-dv.timeline-0.1.0.cip.digest.txt carries it and the extraction identity.

    The 5 fixtures shipped inside it are synthetic and modelled on the worked examples in the two format specifications. They carry no customer definition.

    Ruby plugin package

    de.h-dv.ruby-0.6.0.cip is the compiled-in Ruby extractor as an EXTERNAL, sandboxed package: tree-sitter-ruby loaded at runtime, the extractor compiled to wasm32-unknown-unknown and byte-reproducible from crates/guest/ruby/, and the same symbols, references, visibility and Rails association names the built-in produces.

    It claims .rbx, not .rb. The compiled-in Ruby plugin owns .rb, .rake, .gemspec, Rakefile and Gemfile, and a package may not claim a file a built-in claims. So installing this changes NOTHING about how your .rb files are indexed — it is the migration proof for running a full language out of a package, published so it can be read and run rather than described. Do not install it expecting to replace built-in Ruby support.

    It is NOT installed by installing code-index. Packages are installed into a user-controlled store and approved per project, and installing grants nothing — enable is the grant.

    Download de.h-dv.ruby-0.6.0.cips too and keep the .cips beside the .cip. The same signature rules apply as for the packages above, and one key signs every package in this release.

    code-index plugin install de.h-dv.ruby-0.6.0.cip --sha256 sha256:a6b8d7787cecb49c225ff3dda9016c96babc00c4cf59242a2d774c8b06672048
code-index plugin check   sha256:a6b8d7787cecb49c225ff3dda9016c96babc00c4cf59242a2d774c8b06672048 --derived-names
code-index plugin enable  sha256:a6b8d7787cecb49c225ff3dda9016c96babc00c4cf59242a2d774c8b06672048 --derived-names \
    --capabilities same_file_candidate,exported_candidate,reachability_anchor,qualified_candidate,type_position_candidate,member_candidate

    --derived-names is required on check as well as on enable, and without it check REPORTS FAILED. Rails' has_many :posts emits a type reference named Post at the span of the literal :posts, so the name was not copied out of the source it points at; validation is all-or-nothing per file, so the authority is what admits the whole file rather than the one row. Withhold it and you keep the package with every Rails file refused — that is a supported answer, not a broken install.

    No --bridges: Ruby resolves inside its own language, so the package declares none. The six capabilities above are exactly what its manifest requests and enable refuses a grant wider than the request; grant fewer and the index stays searchable but resolves less, because every candidate pool a reference could be admitted to is one of them.

    The digest above is the one this release packed and it is what --sha256 pins; de.h-dv.ruby-0.6.0.cip.digest.txt carries it and the extraction identity.

    The 5 fixtures shipped inside it were generated from the COMPILED-IN Ruby extractor, by a different author from the port they grade, and plugin check compares the package's facts against them exhaustively.

    Svelte plugin package

    de.h-dv.svelte-0.1.0.cip makes .svelte files carry symbols and references instead of being text-only: the TEMPLATE half of a single-file component — markup, mustaches, {#snippet} declarations and {@render} uses — out of one sandboxed extractor over the tree-sitter-svelte-ng grammar.

    It claims .svelte and NOTHING ELSE. .svelte.ts and .svelte.js are deliberately not claimed and this package declares no [[displaces]]: those files are Svelte 5 runes modules, valid TypeScript and valid JavaScript, which the built-in plugins already index correctly. Claiming them would take files away from a producer that reads them in order to read them worse.

    It is NOT installed by installing code-index. Packages are installed into a user-controlled store and approved per project, and installing grants nothing — enable is the grant.

    Download de.h-dv.svelte-0.1.0.cips too and keep the .cips beside the .cip. The same signature rules apply as for the packages above, and one key signs every package in this release.

    code-index plugin install de.h-dv.svelte-0.1.0.cip --sha256 sha256:4b10a478532d67f3694995373e1a64d397611af5c4f2615c085b006628b3322f
code-index plugin check   sha256:4b10a478532d67f3694995373e1a64d397611af5c4f2615c085b006628b3322f
code-index plugin enable  sha256:4b10a478532d67f3694995373e1a64d397611af5c4f2615c085b006628b3322f \
    --capabilities same_file_candidate

    One capability, and that is the package asking for exactly what it can use. Every symbol this version emits is a {#snippet}, whose visibility is file: reachable by name anywhere in its own component and nowhere else. exported_candidate would admit an empty set, so it is not requested — and enable refuses a grant wider than the manifest asks for, so the line above cannot be padded. No --bridges: this package declares none.

    The digest above is the one this release packed and it is what --sha256 pins; de.h-dv.svelte-0.1.0.cip.digest.txt carries it and the extraction identity.

    The 4 fixtures shipped inside it are synthetic: one positive control in which every rule fires, two that are bait for all of them with an empty expectation, and one malformed source. None carries anybody's component.

    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 package above. 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.

    You may anchor it yourself instead — code-index plugin trust add code-index-publisher.pub --fingerprint sha256:1cb03259a8c870b6db02360abd9351e17e67724d1f8c3509d85c4bf6b06fa72c --name 'a label you choose', with code-index-publisher.pub from this release's assets. Your file replaces the compiled-in entry, and the --name is 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-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