v0.6.1

CsMesh 0.6.1

No graph format change. A 0.6.0 index keeps working, so no re-index is needed.

dotnet tool install now delivers the native binary

Until now the NuGet tool was a framework-dependent build: every run compiled Roslyn through the JIT
from scratch. npx and the install scripts already shipped the Native AOT binary, so only NuGet
users paid for it. CsMesh is now a pointer package, and the .NET 10 SDK picks the native package
for your platform when you install or update.

Measured on the same 29-project solution and machine, in one session, with phase timing on:

	0.6.0 dotnet tool	0.6.1 dotnet tool
impl, warm median	185.6 ms	54.1 ms
trace --depth 2, warm median	204.8 ms	47.8 ms
index --full, warm	12.8–15.3 s	1.8–2.1 s
first launch before Main	1.6 s	about 0.05 s

Native packages: win-x64, win-arm64, linux-x64, linux-arm64, osx-x64, osx-arm64. Any other
platform gets CsMesh.any, the framework-dependent build, so install and update keep working
there. Each native package is about 13 MB, against 4 MB for the old one.

dotnet tool update -g CsMesh

Updating from 0.6.0 was verified on win-x64.

More platforms

Release archives and the npm package now cover win-arm64, linux-arm64 and osx-x64 as well. Before,
npm exited on those platforms.

Phase timing

CSMESH_TIMINGS=1 writes one line per indexing phase to stderr, with the time from process start to
Main. Nothing reaches stdout, so JSON and MCP output are unaffected. Include it when you report a
slow run.

Docs

Every latency and startup figure now names the channel it was measured on.

📦 Installation & Upgrades

Global .NET Tool

dotnet tool update --global CsMesh

Automatic One-Line Install Script

Linux & macOS:

curl -fsSL https://raw.githubusercontent.com/nRafinia/CsMesh/main/install.sh | sh

Windows (PowerShell):

irm https://raw.githubusercontent.com/nRafinia/CsMesh/main/install.ps1 | iex

Quick Setup for AI Assistants

# Install skills and register MCP server in one command:
csmesh install --all
csmesh index