Changelog

What's new in SourceVault. Everything below runs on your own hardware, with local models and no source-code egress.

2026-10-25, v1.67.0: MCP over HTTP, the network door for a team server

Until now the MCP server ran only where the client ran: every developer indexed locally, and a team server had no MCP door. This release adds one. A team server now serves MCP over HTTP behind named agent tokens, so one governed install answers every developer's Claude Code or Cursor, with the same tools, policy, redaction and audit chain as before. The pre-release security review of that work tightened repository scope on every door, and that fix ships here too.

Added

Changed

Upgrade notes

2026-10-24, v1.66.0: One-click install for Claude Desktop, and a registry listing

Until now the MCP server reached a client by hand: claude mcp add for Claude Code, a JSON stanza for everything else. Hosts that install MCP bundles, Claude Desktop first among them, now get SourceVault with one click, and the official MCP registry lists it, which is where the directories agent users browse take their entries from.

Added

Upgrade notes

2026-10-24, v1.65.0: A published container image, and one macOS install

The team-server path asked for a source checkout: git clone, then docker compose up --build, on a machine that may have neither git nor the build tools. Every release now publishes a ready image for two platforms, so a server install is a Compose file and a pull. On macOS the installer carried a second channel beside Homebrew that none of the product's own tooling understood; it is retired, and the move to Homebrew is written down.

Added

Changed

Upgrade notes

2026-10-24, v1.64.0: Two lines to a working install

After brew install the user still had seven steps ahead: start the service, start Ollama, pull two models, find a 64-character token in a file whose path differs by platform, paste it into the unlock screen, and only then open a dashboard that, on a fresh machine, could not search until the models had finished downloading. This release makes the install brew install and sourcevault setup, and makes the minutes before the models arrive useful instead of broken.

Added

Fixed

Upgrade notes

2026-10-24, v1.63.0: Is it working?

Only Linux and Windows installs were health-gated. On macOS `brew services start` returns before the server boots, and the installed command line had no way to ask whether the install works: npm run doctor is the pre-install preflight, and it lives in a source checkout. The macOS instructions also had the model pulls before anything had started Ollama, which fails on a fresh Mac.

Added

Changed

Upgrade notes

2026-10-24, v1.62.0: The overview, answered first

v1.61.0 built the overview layer on every install: the repository map at reindex, and a local-model summary per module behind `sourcevault summarize`. Measured afterwards, that layer never reached a caller. For "what are the main modules of this repository and how are they organised" the vector search ranked the summaries first, the heuristic rerank buried them in the thirties under code chunks matching the word "main" in a file name, and ask cited none of them. This release seats them where the question wants them, and only there.

Changed

Upgrade notes

2026-10-23, v1.61.0: The overview, on every install

Chunk retrieval answers "where is X" well and "how does X work overall" badly: a dozen fragments from a dozen files, and no picture of which modules exist or how they relate. The repo map that fixes this existed, but only a source checkout could build it. Now every install has it.

Added

Fixed

Upgrade notes

2026-10-13, v1.60.0: Refusals on the console

Ten refused dashboard requests in twelve milliseconds from one host were invisible on the Gateway view and surfaced only in the quarter report. A security console should show that first.

Added

Upgrade notes

2026-10-13, v1.59.0: The page a reviewer files

A SOC 2 or ISO 27001 reviewer asks a short list of questions about AI coding agents. This release answers them on one page, from the records the install already keeps.

Added

Upgrade notes

2026-10-10, v1.58.0: One question, answered on your terms

SourceVault never phones home, so the only way to learn which half of the product an install uses is to ask. This release asks, once, at the moment the answer is freshest, and makes answering cost one click and no privacy.

Added

Upgrade notes

2026-10-10, v1.57.0: The evidence leaves the box

Two things ship. The Gateway's records now export to a SIEM and roll up into a period report a compliance review can file, and the dashboard comes out of a five-phase UI/UX review with the same features in a quieter, more consistent, more accessible shape.

Added

Changed

The dashboard, phase by phase (#468, #470, #472, #473):

Upgrade notes

2026-10-10, v1.56.1: The ask model is a choice

Three changes to the model manager (#464; v1.56.0 below was a version bump that shipped without them). The dashboard no longer names a model nothing can run, the picker stops reading like a spec sheet, and the model Ask runs on is chosen once, on the server, for every surface.

Added

Changed

Upgrade notes

2026-10-10, v1.56.0: Version bump only

Published with the v1.55.0 feature set: the model-manager pull request was refused by the forge's status checks while the release pull request merged, so this tag carries no product change. The changes it was meant to carry are in v1.56.1 above.

2026-10-09, v1.55.0: The engine is free

The commercial shape changes with this release, and the product follows it: the engine is free forever on one repository, the Gateway is what a license buys, and Team becomes an annual per-seat term. Nothing already installed stops working; several things that used to stop now keep going.

Added

Changed

Upgrade notes

2026-10-07, v1.54.0: The security review ships

A principal-level security review of the whole product, fixed in four phases plus a sweep of the smaller findings (#449, #450). Two themes ran through it: a hostile repository that the operator chooses to index, and trust decided by the bind address instead of by who is actually calling.

Added

Changed

Upgrade notes

2026-08-26, v1.53.1: The plan card names the key

Added

Changed

2026-08-26, v1.53.0: A signing key that can rotate

Added

Changed

2026-08-26, v1.52.1: The API spec catches up

Added

2026-08-26, v1.52.0: Branded HTTPS on WSL and Linux

Added

Fixed

Changed

2026-08-26, v1.51.1: Health checks on TLS installs

Fixed

Changed

2026-08-26, v1.51.0: The relay is governed

Security

Changed

Fixed

2026-08-25, v1.50.0: The trial runs the Gateway

Added

2026-08-25, v1.49.0: Monorepo scale on a laptop, and no vector database to run

Added

Changed

2026-08-21, v1.48.0: A relay that retries and reports

Added

2026-08-21, v1.47.0: The audit chain answers who

Added

Existing shared-secret setups keep working unchanged (they attribute as shared-secret); every previously issued Gateway license gains the identity feature automatically.

2026-08-21, v1.46.0: A calm power screen

Changed

2026-08-21, v1.45.0: The stack follows SourceVault

Added

On Windows/WSL and Linux, Ollama is deliberately not stack-managed - it runs on the Windows side (WSL) or as a root service (Linux), and often serves more than SourceVault.

2026-08-20, v1.44.0: A lighter dashboard

Changed

2026-08-20, v1.43.0: Silent tab updates

Changed

2026-08-20, v1.42.1: The CLI on your PATH

Fixed

2026-08-20, v1.42.0: Update from Settings

Added

Fixed

2026-08-20, v1.41.0: Dashboard, once

Changed

2026-08-20, v1.40.0: An install that asks for nothing

Ten findings from smoke-testing the one-line installers on real hardware across macOS, Linux, and Windows/WSL - every one fixed. The headline: a machine whose dependencies are already present now installs SourceVault without a single password prompt, and on Windows the dashboard survives a reboot without anyone logging in.

Changed

2026-08-20, v1.39.0: Browse on one edge, read on the other

Changed

2026-08-20, v1.38.0: The file explorer grows up

Changed

Fixed

2026-08-20, v1.37.0: See inside your repositories

Added

2026-08-20, v1.36.0: Ask while you ask

Changed

Also in this release: the re-published retrieval benchmark (docs/BENCHMARK.md) - 472 questions across five public corpora, zero errors, results tables newest-first (#326).

2026-08-20, v1.35.0: Every question gets its own tab

Changed

Previously every new ask joined the active thread by default, which made tabs act like collections - and archiving one appeared to take several results with it. (Nothing was ever deleted: the other questions stayed in History; only the shared tab closed.)

2026-08-20, v1.34.0: Results you can put away

Three history-management gaps reported from live use, one theme: actions that looked like they did nothing.

Changed

Fixed

2026-08-20, v1.33.0: The dashboard reads like a feed, and updates in one click

Two quality-of-life fixes for the dashboard, both reported from live use.

Changed

Fixed

2026-08-20, v1.32.0: The branded dashboard drops its port

One feature, small and visible: after sourcevault tls-setup, the dashboard URL is now https://dashboard.sourcevault.ai/dashboard/ - no port suffix.

Changed

Fixed

Upgrade notes

2026-08-20, v1.31.0: Retrieval that finds the code you named, and a branded HTTPS dashboard

Every change in this release was measured on a benchmark that tripled in size first: the four retrieval question sets now hold 96 questions each (384 total, #303), adversarially adjudicated, with documentation-, test- and config-seeking questions covered for the first time. Each retrieval improvement below shipped only after a paired replay across all 384 questions showed gains with no losses; two further candidates (a wider vector fetch window, a retuned rank-fusion constant) measured as nulls and were closed without shipping.

Added

Changed

Upgrade notes

2026-08-19, v1.30.0: The audit release — fail-first fixes and per-repo collections only

A full-codebase audit (docs/CODEBASE_AUDIT.md) and the RAG modularization plan (docs/RAG_MODULARIZATION_PLAN.md) were executed end to end this release: fourteen stacked pull requests (#285–#298) plus follow-ups (#299–#301). Everything below is the operator-visible part; the internal restructuring — clients.js, ask.js, history.js and indexer.js each split behind their existing import paths — changes no behavior and is recorded in the two documents.

Security

Changed

Fixed

Upgrade notes

2026-08-12, v1.29.0: Sessions you can revoke, and retrieval that stays put

Security

Fixed

Changed

Upgrade notes

2026-08-10, v1.28.0: A faster dashboard, and signed requests that expire

Fixed

Security

Upgrade notes. One breaking change, and one automatic reindex.

*Signed requests.* If you call /api/search-codebase, /api/read-file, or /api/history-search from something you wrote yourself, it must now send x-code-search-signature-timestamp and -nonce alongside the signature, and sign timestamp.nonce.body rather than the body alone. The clients shipped with SourceVault, including the Hermes plugin, were updated and need nothing. Requests without the new headers are answered 401 timestamp_required. The /task and /result relay endpoints still accept the old form, because Hermes and OpenClaw sign those; set SOURCEVAULT_HMAC_REQUIRE_TIMESTAMP=1 to require it there too once they have been updated.

*Embedding model.* The first index run after upgrading records which model built each index. If you later change OLLAMA_EMBED_MODEL, CODE_EMBED_URL, or CODE_EMBED_DIMS, the next incremental run rebuilds that repository once rather than mixing two models' vectors, and searches against a mismatched index are refused until it is rebuilt. Existing indexes carry no recorded model and are left alone until something changes.

2026-08-10, v1.27.0: Sign in to GitLab without pasting a token

Added

Fixed

Security

The GitLab flow has never run against a live GitLab instance. No OAuth app is registered and nobody maintaining SourceVault uses GitLab. Protocol handling is well tested, but no test says whether a given GitLab version accepts the scopes as asked or whether the token authenticates a real clone. If you are first to enable it, expect to debug it. The token path is unaffected.

Upgrade notes. Nothing required. GitLab OAuth stays off until configured. Register an application in GitLab (User settings → Applications) with the device flow enabled, set SOURCEVAULT_GITLAB_CLIENT_ID, restart. Existing connections and every token login are unchanged. Bitbucket and Forgejo keep using tokens: neither implements the device grant, verified against a live Forgejo instance.

2026-08-07, v1.26.0: Sign in to GitHub without pasting a token

Added

Access tokens are not going away, and for some setups they remain the better choice. GitHub's OAuth apps only offer coarse repository access: the scope that reaches private repositories also grants write access, which is broader than a fine-grained token limited to read. If you want SourceVault to hold the narrowest possible access to your code, keep using a fine-grained personal access token — both options stay side by side in the sign-in dialog, and this release does not change any connection you already have.

Upgrade notes. OAuth sign-in is off until it is configured, and upgrading alone does not switch it on; the sign-in dialog looks exactly as it does today until then. Turning it on takes two steps: register a GitHub OAuth app (GitHub → Settings → Developer settings → OAuth Apps) with device flow enabled, then set SOURCEVAULT_GITHUB_CLIENT_ID to its client ID and restart. Full steps are in docs/DASHBOARD.md. GitLab, Bitbucket, Forgejo, and custom remotes are unchanged and continue to use tokens.

2026-08-07, v1.25.1: Fixes a v1.25.0 reindex that emptied a repository's index

Fixed

If you already hit this. Upgrade and reindex the affected repository once: the reindex now rebuilds it. Nothing was lost from your working copy, and no chunk content was destroyed; the index simply had not been written to the new store yet. Repositories you have not reindexed since upgrading were never affected.

2026-08-07, v1.25.0: Large repositories stop breaking search

Fixed

Upgrade notes. Nothing to do, and nothing to migrate by hand. A repository moves to its own store the next time it is indexed; until then it is read the old way and behaves exactly as before. That means a large repository keeps hitting the failure above until you reindex it once, which is worth scheduling deliberately for a very large corpus rather than letting it happen during a working day.

2026-08-07, v1.24.0: Locking keeps your place, and an edited repository stops nagging

Changed

Fixed

2026-08-07, v1.23.0: SourceVault can serve its own HTTPS

Added

TLS stays off unless you configure it, and a local install should leave it that way: browsers already treat http://localhost as a secure origin, so the dashboard installs as an app and shows no warning without any certificate at all. A misconfigured certificate stops the server from starting rather than quietly falling back to unencrypted traffic.

Security

Upgrade notes. If you run SourceVault behind a TLS-terminating reverse proxy and have not set SOURCEVAULT_TRUST_PROXY, your dashboard cookies were being marked Secure by accident and will stop being. Set SOURCEVAULT_TRUST_PROXY to the number of proxy hops in front of the app (usually 1). That setting was always required for this deployment (it also governs whether rate limits and audit records attribute a request to the real client or to the proxy), so this is worth setting regardless. The server writes a single forwarded_proto_untrusted warning at the point it notices, rather than failing.

2026-08-07, v1.22.0: Deselecting a repository stops searching it

Fixed

2026-08-07, v1.21.0: Settings becomes a page

Changed

Fixed

2026-08-07, v1.20.0: Three more themes, and a drawer that stays where you put it

Added

Fixed

Changed

2026-08-07, v1.19.0: Choose how the dashboard looks

Added

Security

Fixed

2026-08-06, v1.18.0: The dashboard notices every index

Added

Fixed

2026-08-06, v1.17.0: Reindexing only pays for what changed

Changed

Fixed

Upgrade notes. If you deliberately index files larger than 2 MB, set SOURCEVAULT_INDEX_MAX_FILE_BYTES before your next reindex; otherwise their existing chunks are removed as the index refreshes. If you have tooling that rewrites files while restoring their original size and timestamp, SOURCEVAULT_INDEX_ALWAYS_HASH=1 keeps the previous read-and-hash behaviour.

2026-08-05, v1.16.1: Secret redaction covers compound key names

Fixed

Upgrade notes. If you rely on Sentinel's DLP pass, upgrade. Redaction happens at read time rather than at index time, so upgrading is sufficient: no reindex is required, and previously served content is not retroactively affected. Reads after the upgrade are scanned by the corrected rule.

2026-08-05, v1.16.0: Indexing that can't spin forever

Added

Fixed

No operator action is required for this upgrade.

2026-08-05, v1.15.0: Any git host, and sign-in that meets you at the door

Added

Changed

No operator action is required for this upgrade.

2026-08-05, v1.14.0: Self-hosted Forgejo and Gitea join the provider list

Added

Fixed

No operator action is required for this upgrade.

2026-08-05, v1.13.2: Dashboard stops failing silently on vanished history

Fixed

No operator action is required for this upgrade.

2026-08-05, v1.13.1: Fresh benchmark numbers and self-announcing releases

Added

Changed

No operator action is required for this upgrade; there are no runtime code changes.

2026-08-04, v1.13.0: Lite mode runs without Ollama or a GPU

Added

No operator action is required for this upgrade. Lite mode is opt-in; existing full-stack installs behave identically.

2026-08-04, v1.12.0: The SourceVault Gateway

Added

Changed

No operator action is required for this upgrade. Existing licenses, policies, and MCP client configurations work unchanged.

2026-08-03, v1.11.2: Same-day ip-address advisories and pin updates

Fixed

Changed

No operator action is required for this upgrade.

2026-08-03, v1.11.1: Security bumps and the Forgejo-native pipeline

Fixed

Changed

No operator action is required for this upgrade.

2026-08-03, v1.11.0: The trial clock survives a wiped state dir

Changed

Upgrade notes

2026-07-31, v1.10.1: Dependency updates and release housekeeping

Fixed

2026-07-24, v1.10.0: The dashboard can tap you on the shoulder

Added

Fixed

2026-07-24, v1.9.0: Choose your history backend from the dashboard

Added

2026-07-23, v1.8.0: History search reaches the machine API and the Hermes plugin

Added

2026-07-23, v1.7.0: Opt-in full git history

Added

Fixed

2026-07-23, v1.6.0: Keyword search stops scanning the whole repo

Changed

Added

2026-07-23, v1.5.1: Dependency security updates and clearer docs

Fixed

Changed

2026-07-08, v1.5.0: Source provenance recorded at add time

Changed

2026-07-08, v1.4.2: Local sources index and classify correctly

Fixed

2026-07-08, v1.4.1: Dashboard health fix for uncommitted local sources

Fixed

2026-07-08, v1.4.0: Local folders and files

Added

Changed

Upgrade notes

2026-07-07, v1.3.5: Version at a glance

Added

2026-07-07, v1.3.4: Upgrades apply themselves

Fixed

Upgrade notes

2026-07-07, v1.3.3: The dashboard becomes a workspace

Changed

Fixed

Upgrade notes

2026-07-07, v1.3.2: Support surfaces, in the product

Added

Changed

2026-07-07, v1.3.1: Self-serve Starter → Pro upgrade

Added

Fixed

2026-07-06, v1.3.0: Sentinel, enforced dashboard auth, async task relay

Added

Security

Fixed

Changed

Upgrade notes

2026-07-03, v1.2.0: production hardening — sanitized errors, rate-limited machine API, Vite 8, non-root Docker

Security

Fixed

Changed

Upgrade notes

2026-07-02, v1.1.6: sourcevault app Dock launcher

Added

2026-07-02, v1.1.5: install the dashboard as an app + self-healing upgrades

Added

Fixed

Changed

2026-07-02, v1.1.4: branded dashboard URL

Added

Fixed

2026-07-02, v1.1.3: enforce the advertised trial repo cap

Fixed

2026-07-02, v1.1.2: version everywhere support needs it

Added

2026-07-02, Auto-release on version bump + browser smoke tests

Pipeline

2026-07-02, v1.1.1: fix dashboard CSRF cookie path

Fixed

2026-07-02, 7-day trial for unlicensed installs

Licensing

2026-07-02, One-command macOS install via Homebrew

Platform

Release engineering

2026-07-02, Security hardening, observability, and deploy polish

Security

Observability

Deployment & PWA

2026-06-20, Plan limits + macOS support

Platform

Licensing

2026-06-19, Docker Compose deployment + installable PWA dashboard

Deployment

Dashboard

2026-06-19, Webhook-driven reindexing and chunk-level dedup

Indexing

2026-06-18, Ask survives a browser refresh

Dashboard

2026-06-18, Indexing at scale, retrieval quality, and live progress

A focused push to make large-repo indexing reliable and fast, surface what indexing is doing in the dashboard, and close a retrieval-recall bug. Shipped across PRs #35–#48 (roadmap tracked in issue #44).

Retrieval quality

Indexing reliability & performance

Dashboard