Install
Install the Fuse global tool from NuGet, or grab a self-contained binary if you do not have the .NET SDK.
Fuse is a developer tool for .NET developers, so the recommended install is the .NET global tool. If you do not have the .NET SDK, there is a self-contained binary that needs nothing else.
Recommended: the .NET global tool
dotnet tool install -g FuseVerify it:
fuse --helpUpdate later with:
dotnet tool update -g FuseRequirements: the .NET SDK 10.0 or later. Git change scoping also needs the
git executable on your PATH.
Run without installing
The .NET 10 SDK can run Fuse on demand without a global install:
dnx Fuse -- serveWithout the .NET SDK
These give you a single self-contained binary (Native AOT, no runtime required). Linux x64 and Windows x64 are published; on macOS use the .NET global tool above.
Install script
# Linux
curl -fsSL https://fuse.codes/install.sh | sh# Windows
irm https://fuse.codes/install.ps1 | iexEach script downloads the latest release binary, verifies its checksum, and puts
fuse on your PATH. Set FUSE_VERSION to pin a version or FUSE_INSTALL_DIR to
choose the location.
WinGet (Windows)
winget install Litenova.FuseDownload a binary
Grab fuse-<version>-win-x64.zip or fuse-<version>-linux-x64.tar.gz from the
GitHub Releases page,
verify it against SHA256SUMS.txt, extract, and put fuse on your PATH.
Build from source
On Windows, the bundled script builds, packs, and installs the tool locally:
install.batOn any OS:
dotnet pack src/Host/Fuse.Cli/Fuse.Cli.csproj -c Release
dotnet tool install -g Fuse --add-source src/Host/Fuse.Cli/nupkgNext
Run your first fusion in the Quickstart, or wire Fuse into an agent on the Connect to your AI page.
Why Fuse, and how it compares
The problem agentic coding tools hit on large codebases, what generic packers and RAG indexers do and where they fall short, and what Fuse does differently.
Quickstart
Run Fuse against a .NET project, read the output it produces, and find the generated file, in about 30 seconds.