Fuse
Project

Changelog

Where to find the full version history for Fuse.

The complete version history lives in the CHANGELOG.md file at the repository root. This page points to that file and names the most recent notable changes. The changelog records what has shipped; planned work is described separately on the Roadmap.

This page is for anyone checking what changed between versions.

Where the History Lives

The repository CHANGELOG.md file documents every notable change by version, including breaking changes and additions. Read it there rather than here so the history stays in one place alongside the source.

Most Recent Notable Changes

Breaking change (3.0): Fuse is now a Roslyn-backed .NET semantic context engine with a warm, persistent index, not a token-reduction optimizer. The CLI is index, map, localize, resolve, context, review, find, diagnostics, reduce, models, init, mcp, and host; the MCP server exposes eight tools (fuse_index, fuse_map, fuse_localize, fuse_resolve, fuse_context, fuse_review, fuse_find, fuse_reduce) and four resources. The 2.x query-scoping engine and its eleven-tool surface (fuse_toc, fuse_skeleton, fuse_focus, fuse_search, fuse_changes, fuse_ask, fuse_dotnet, fuse_generic, fuse_explain) and the fuse dotnet, fuse wiki, fuse ask, fuse explain, and fuse verify commands are removed.

The persistent index is a single SQLite database at .fuse/fuse.db (schema version 10), built through MSBuild and Roslyn with a syntax-only fallback and re-indexed incrementally per changed file. See Store internals and Operator guide.

The benchmark is now four suites run by a C# eval driver (fuse eval semantics|review|localize|agent); the numbers and figure are regenerated from tests/benchmarks/results. See Benchmarks.

Native AOT distribution is decommissioned. Release binaries are self-contained framework-dependent publishes that bundle the .NET runtime. Install paths are unchanged; see Install.

What This Does Not Cover

This page does not reproduce the version history. The repository CHANGELOG.md file holds it. Planned and unshipped work is on the Roadmap, not in the changelog.

Next

Read the Roadmap for the planned direction, or Contributing to build a change that would appear in a future entry.

On this page