CsMesh 0.11.0

<div align="center">

⚡ csmesh

Structural Code Intelligence Engine for C# & .NET

Answers architectural, call-graph, and dependency questions under a hard token budget.
Built for AI coding agents and developers who are tired of multi-turn "file-hopping" and noisy grep queries.

</div>

$ csmesh trace PaymentController.Post --budget 600

PaymentController.Post  {http:POST /charge}  Api/PaymentController.cs:14-26
  -> CreatePaymentCommandHandler.Handle  [mediatr via Send(CreatePaymentCommand)]  App/CreatePaymentCommand.cs:18-31
    -> IPaymentGateway.Authorize  Infra/Repositories.cs:11
      -> StripeGateway.Authorize  [impl, di-bound]  Infra/Repositories.cs:29-33
    -> IPaymentRepository.Add  Infra/Repositories.cs:7
      -> PaymentRepository.Add  [impl, di-bound]  Infra/Repositories.cs:17-22
        -> AppDbContext.SavePayment  Infra/Repositories.cs:35-40
      -> InMemoryPaymentRepository.Add  [impl]  Infra/Repositories.cs:24-27

📑 Table of Contents

• The Problem: The Hidden Tax of AI Code Exploration
• Dual Mode: CLI and MCP Server Support
• Empirical Benchmarks
• Key Features
• Confidence & Provenance
• Installation
  • Global .NET Tool
  • Standalone Native AOT Binary
• Quick Start
• Supported IDEs & AI Coding Agents
• CLI Reference
• The Recommended Hybrid Workflow: csmesh vs. grep
• Deterministic Exit Codes
• Telemetry & Audit Logging
• Repository Structure
• License

🛑 The Problem: The Hidden Tax of AI Code Exploration

When an AI coding agent or engineer asks a structural question about a decoupled C# codebase—such as:

• "If I modify this interface method, what breaks downstream?"
• "Which concrete class is actually resolved and injected by the DI container at runtime?"
• "Where does this Mediator _mediator.Send() or background queue message end up?"

...standard tooling forces a repetitive, expensive "file-hopping" loop:

[Agent] grep for interface -> finds 12 test fakes, mocks, & docstrings
   ↓ (Turn 1: ~600 tokens)
[Agent] opens File A -> finds interface dispatch, not the implementation
   ↓ (Turn 2: ~800 tokens)
[Agent] greps for DI registration -> sifts through Program.cs and test fixtures
   ↓ (Turn 3: ~1,200 tokens)
[Agent] opens File B -> discovers it sends a MediatR command
   ↓ (Turn 4: ~1,500 tokens)
Context Exhaustion & Slow Responses (~5,000 tokens burned, 4-5 turns wasted)

In layered, enterprise .NET applications, lexical text search (grep, ripgrep) hits a wall. Text search cannot see:

1. Dependency Injection Bindings (AddScoped<IService, Service>())
2. CQRS / MediatR Handler Dispatches (_mediator.Send(cmd))
3. Interface Implementation Ranking (distinguishing production services from mock fakes)
4. Attribute-based & Blazor Endpoint Routing ([HttpGet], [HttpPost], @page "/...")
5. Razor & Blazor Components (types, @code methods, and parameter bindings compiled via Roslyn source generators)

csmesh solves this in a single shell command. It parses your codebase's AST and semantic model via Roslyn into a pre-compiled, frozen symbol graph and answers in milliseconds — and every edge it hands back carries how it was derived and how sure it is, so an answer can be checked instead of trusted.

🔌 Dual Mode: CLI and MCP Server Support

csmesh supports both command-line interface (CLI) and Model Context Protocol (MCP) workflows with a first-class experience, giving developers and AI agents the flexibility to choose what works best:

• ⚡ Fast CLI-First Execution:

  • Zero Idle Context Overhead: Incurs zero token spend until explicitly invoked.
  • Bounded Output (--budget): Every answer is capped at an estimated token count (--budget 300, --budget 600), exiting cleanly with code 2 on overflow instead of polluting conversation history. The estimate is ceil((chars + 1) / 4), not a model tokenizer — close enough to size a reply, not a billing figure.
  • Command Chaining: Chain queries in a single turn (csmesh impl IStore --budget 200 && csmesh blast-radius Order.Submit --budget 400).

• 🤖 Native Model Context Protocol (MCP) Server:

  • Interactive Agent Experience: Run csmesh serve to expose query tools over standard JSON-RPC (stdio) to MCP-compatible clients like Claude Desktop, Cursor, Antigravity, VS Code, Windsurf, and Cline.
  • One-Command Setup: Register csmesh into IDE configurations with csmesh install --mcp (locally) or csmesh install --mcp --global (machine-wide).
  • Token-Efficient Tool Responses: Returns dense, structured plaintext designed for LLM comprehension without wasteful, unbounded JSON dumps.

📊 Empirical Benchmarks

To quantify the real-world performance gains, csmesh was benchmarked against the standard AI agent workflow (Ripgrep / rg + sequential file reads) across a private 29-project .NET solution (1,945 symbols, 5,328 edges, measured 2026-09-23 on csmesh 0.7.0).

The evaluation measured four critical dimensions:

1. Query & Execution Latency: Raw tool execution time and total agent turnaround time.
2. Agent Round-Trips: Number of iterative tool calls and model reasoning turns required to reach the answer.
3. Context Spend & Token Consumption: Prompt tokens spent on search noise vs. dense architectural facts.
4. Semantic Accuracy: Ability to distinguish runtime DI bindings, production code, and test doubles.

Scenario-by-Scenario Benchmark Summary

Symbol names above are placeholders; the numbers were measured on the real codebase with symbols of the same shape. Median of 20 warm runs (graph pre-indexed and held in the OS file cache) on a NativeAOT win-x64 build of csmesh 0.6.0, 2026-09-21, on a 13th Gen Intel Core i7-13620H (10 cores / 16 threads, 48 GB RAM, NVMe SSD). Token counts use csmesh's own estimator at roughly four characters per token.

Deep-Dive Real-World Scenarios

Times below are the same 2026-09-21 medians as the table above, measured on the NativeAOT win-x64 channel; the framework-dependent dotnet tool channel pays JIT warm-up and is slower.

1. Interface Implementation & Runtime DI Resolution

• With csmesh impl IOrderRepository --budget 300 (27.6 ms, NativeAOT win-x64): Identifies all 3 concrete implementations in a single glance: tags SqlOrderRepository with [di:scoped] along with the exact file and line where it was bound in the IoC container, while clearly marking SpyOrderRepository and InMemoryOrderRepository as test doubles.
• Without csmesh:
  • Turn 1: Run rg ":\s*IOrderRepository\b" to find inheriting classes (returns multiple classes, but cannot indicate which one is registered in production).
  • Turn 2: Run rg "AddScoped.*IOrderRepository" to discover registration logic.
  • Turn 3: Open the DI module or test fixture to verify which instance actually executes at runtime.

2. Forward Call Chain Tracing Across Interface Boundaries

• With csmesh trace OrderEndpoints.CreateOrderAsync --depth 2 (27.8 ms, NativeAOT win-x64): Follows execution seamlessly across decoupled interface abstractions. Traces IAuthorizationService.AuthorizeAsync directly to its concrete implementation AuthorizationService.AuthorizeAsync, continuing downstream to AuditLogger.LogAsync and AppDbContext.SaveChangesAsync.
• Without csmesh: The agent must open the endpoint file (~100 lines), observe the interface call, search for the interface declaration, grep for implementations, open the implementation source, and repeat this cycle until reaching the persistence layer—burning 5 to 7 turns and 30+ seconds of reasoning time.

3. Blast Radius & Change Impact Analysis

• With csmesh blast-radius OrderRepository.UpdateAsync --budget 800 (27.4 ms, NativeAOT win-x64): Computes the reverse transitive dependency graph: reveals that modifying UpdateAsync impacts 18 internal members, 1 public HTTP route (OrderEndpoints.CreateOrderAsync), and 14 tests across 4 separate projects—clearly categorizing test callers vs. production entrypoints.
• Without csmesh: Running rg "\bUpdateAsync\b" returns dozens of raw matching lines across interfaces, mocks, comments, and unrelated classes. Text search cannot determine which root endpoints ultimately depend on this method without exhaustive manual back-tracing.

4. Multi-Hop Path Finding

• With csmesh path OrderEndpoints.CreateOrderAsync OrderRepository.UpdateAsync (29.7 ms, NativeAOT win-x64):

  OrderEndpoints.CreateOrderAsync
    -> OrderService.ProcessOrderAsync
      -> IOrderRepository.UpdateAsync
        -> SqlOrderRepository.UpdateAsync [impl, di-bound]
  

  Resolves the exact 4-hop invocation path through services and DI container registrations in 29.7 ms—a task fundamentally beyond the capabilities of text search.

Core Takeaways

1. Semantic Intelligence vs. Lexical Speed: While ripgrep searches text in 30–50 ms, its output is lexical, not semantic. csmesh answers in ~25–30 ms (median of 20 warm runs on the NativeAOT win-x64 channel, measured 2026-09-21 on csmesh 0.6.0), but returns definitive, actionable architectural conclusions rather than raw strings.
2. Eliminating the Agent Turn Latency Bottleneck: In AI agent interactions, the dominant latency cost is LLM inference and reasoning per turn (often 5–15 seconds per round-trip). By collapsing 4 to 8 file-hunting turns into 1 single shell command, csmesh cuts total agent task completion time by over 80%.
3. Context Window Hygiene: Replacing full source file dumps with compact graph edges saves ~93–94% of token spend in the two measured scenarios that have a token baseline (DI binding and call-chain trace), preserving the model's context window for actual implementation rather than navigation. The other scenarios were measured as csmesh token counts only, against qualitative baselines.

✨ Key Features

• 🚀 Native AOT & .NET 10 Ready: No JIT warm-up, no runtime to install, and lookup tables frozen once at load (System.Collections.Frozen) so a query walks the graph instead of rebuilding indexes. Median query on the measured 29-project solution: ~28 ms (median of 20 warm runs, NativeAOT win-x64, csmesh 0.6.0, 2026-09-21), dominated by graph load, not by the walk.
• 🎨 Blazor & Razor Component Intelligence: Indexes Blazor components, @code methods, component parameters, and Razor Pages / MVC views. Automatically discovers @page "/..." routes as HTTP entrypoints and accurately maps line numbers back to .razor and .cshtml source files via Roslyn #line directives.
• 🛡️ Output Budget (--budget N): A hard cap on estimated output tokens. Prevents agent context exhaustion by exiting with actionable tips when a query is too broad.
• 💉 DI & IoC Container Intelligence: Reads service registrations in every form they take — two-argument, typeof pairs, keyed, factory lambdas, and alias registrations such as sp => sp.GetRequiredService<Concrete>() — and ranks the class the container actually returns ahead of the ones nobody registered.
• 📨 MediatR & CQRS Linking: Resolves _mediator.Send(...) and Publish(...) calls to their concrete request handlers across decoupled project boundaries.
• 💥 Blast Radius & Impact Analysis: Computes the reverse call graph to surface all direct/indirect callers, affected controllers, and background consumers before modifying a symbol.
• 🧩 Nested Type & Member Resolution: Resolves members declared inside nested types seamlessly (e.g. Container.Compute automatically resolves Container.Inner.Compute), avoiding lookup misses without shadowing direct matches.
• 🌐 Universal AI Agent Integration: Installs native prompt rules and skills for 12+ AI tools (Claude Code, Cursor, Antigravity, OpenCode, Windsurf, Cline, Copilot, MiMo Code, etc.) with both local and --global machine-wide support.
• 🔄 Incremental Re-indexing: Node identity is a compiler symbol key, not an array position, so an edit re-binds only the files that moved and every edge into them survives. Queries re-bind changed files before answering by default; a [STALE] row means that heal could not run, and the note says why. --no-heal answers from the current graph instead. Falls back to a full pass when an edit touches something that binds across files.
• 🧭 Entry by Description, Not by Name: csmesh where <term> searches names, namespaces, file paths and route templates, then ranks by how many entrypoints reach each hit — so the handler outranks the DTO that shares its name.

🔬 Confidence & Provenance

Not every edge deserves the same trust, and a tool that flattens that distinction is one an agent learns to double-check anyway. AddScoped<IStore, SqlStore>() is read straight off the compiler's symbol table. A Scrutor assembly scan says a family of types is wired, not which pair. Both belong in the graph; only one is a fact.

So every edge carries three fields:

Anything below the threshold prints its score and origin inline rather than blending in:

$ csmesh impl IStore --budget 300
IStore  -- 2 implementation(s)
  SqlStore  [di:scoped, ?0.75 assembly-scan]  src/Data/SqlStore.cs:12-40  @ src/Api/Startup.cs:41
  InMemoryStore  [test]  tests/Fakes/InMemoryStore.cs:8-20

And what csmesh could not resolve is an answer too, not a silence:

csmesh unresolved --kind di   # registrations that produced no edge, with the reason each failed
csmesh silence IStore         # why a symbol has no callers: unbound sites, out-of-scope types
csmesh doctor                 # index health, reference count, stale generated sources, version drift

The graph is a semantic reconstruction of what the code most likely does at runtime, built from Roslyn plus project structure plus known framework conventions. Each in-scope project is compiled on its own, so a project whose references did not all resolve still answers — and doctor tells you how much of it stands on solid ground.

📦 Installation

⚡ Automatic One-Line Install (Recommended)

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

The install scripts download the prebuilt Native AOT binary for your OS and architecture — win-x64, win-arm64, linux-x64, linux-arm64, osx-arm64, osx-x64 — and fall back to the .NET global tool when no asset matches.

1. As a Global .NET Tool

# Install from NuGet.org
dotnet tool install --global CsMesh

# Or build and install locally from source
dotnet pack -c Release
dotnet tool install --global --add-source ./src/CsMesh/bin/Release CsMesh

# Or update an existing installation
dotnet tool update --global CsMesh

From 0.6.1 the tool package is RID-specific: on win-x64, win-arm64, linux-x64, linux-arm64, osx-arm64 and osx-x64, dotnet tool install fetches the Native AOT binary. On any other platform it falls back to the framework-dependent build.

2. Via npm / npx

Bash
# Run directly without global installation
npx @nrafinia/csmesh --help

# Or install globally across Windows, macOS, and Linux
npm install -g @nrafinia/csmesh

npx and npm install -g download the prebuilt Native AOT binary for your platform (the six RIDs listed above) from the GitHub release, so no .NET runtime is needed.

3. As a Standalone Native AOT Binary (Zero Runtime Dependency)

You can compile a single, standalone binary with zero dependencies on the .NET SDK:

# Windows (win-x64)
dotnet publish src/CsMesh/CsMesh.csproj -c Release -r win-x64 -p:PublishAot=true

# Linux (linux-x64) - run via Linux or WSL
dotnet publish src/CsMesh/CsMesh.csproj -c Release -r linux-x64 -p:PublishAot=true

# macOS (osx-arm64)
dotnet publish src/CsMesh/CsMesh.csproj -c Release -r osx-arm64 -p:PublishAot=true

The resulting binary in bin/Release/net10.0/<rid>/publish/ runs on machines without .NET installed and, on the measured NativeAOT win-x64 channel, answers a warm query in ~28 ms median (csmesh 0.6.0, 2026-09-21).

🚀 Quick Start

Run these commands inside any C# / .NET repository (.sln, .slnx, .csproj):

1. Index the Repository

csmesh index
# indexed 28 files -> 161 nodes, 380 edges in 0.1s

dotnet restore
csmesh index

dotnet build --no-incremental -p:EmitCompilerGeneratedFiles=true
csmesh index

2. Configure Your AI Coding Assistants

# Install skill and rule files in the current repository:
csmesh install

# Or install both skill files and MCP server integration:
csmesh install --all

# Or install machine-wide into your user profile (~/.claude, ~/.cursor, ~/.gemini, etc.):
csmesh install --global

3. Ask Structural Questions

# I have words, not a symbol name.
csmesh where discount

# What does this method call down the line?
csmesh trace OrderService.SubmitOrder --budget 600

# Which concrete implementation runs for this interface in DI?
csmesh impl IPaymentGateway --budget 600

# What breaks if I change this method or property?
csmesh blast-radius Order.Status --budget 800

# Where are all the API routes and hosted workers?
csmesh entrypoints orders

🤖 Supported IDEs & AI Coding Agents

csmesh install sets up native prompt instructions and skills across all major coding tools:

📖 CLI Reference

Global Options

Default budgets: impl 600, path 500, where/trace 600, unresolved 700, silence 300, entrypoints 800, map 850, context 900, export 1500, everything else 800.

Commands

csmesh map

Where the weight is: which projects lean on which, where the entrypoints cluster, and the handful of members everything runs through. The first command to run in a repository you do not know — ls answers "where are the files", which is the wrong axis.

csmesh map
csmesh map --under src/Application --budget 400

csmesh export [<symbol>]

Renders the graph as a Mermaid or DOT diagram: the project graph (default), the namespace graph (--level namespace), or the neighbourhood around a symbol (--depth, --direction in|out|both). The symbol is resolved exactly as trace resolves it, overload selector included. Test-tagged nodes and TypeUse edges are withheld by default and named in the counts. Node ids are the first 8 hex digits of SHA-256 of each node's stable identity, so a diagram committed to a design doc does not renumber when an unrelated symbol is added.

csmesh export
csmesh export --level namespace --format dot
csmesh export OrderService.Process --depth 2 --direction out
csmesh export --level namespace --out docs/deps.mmd

Without --out the render goes to stdout under the budget: overflow exits 2 and names both remedies (--out, a coarser --level). With --out the whole render is written by temp file and rename, and stdout carries only a budgeted summary (path, format, level, node/edge counts, withheld counts). The path must stay inside the repository root and under an existing directory — otherwise exit 64; a write failure is exit 70.

csmesh where <term> (alias: find)

Finds the symbols a word belongs to, ranked by how many entrypoints reach them. Start here when the task is described in words rather than symbol names; the last line is the next command, already filled in. --unranked drops the ranking and the next hint and lists every match in stable Node.Key order, for diffing two runs or reading the full match set.

csmesh where discount
csmesh where checkout refund --under src/Application
csmesh where discount --unranked
csmesh find "POST /orders"

csmesh index

Builds or refreshes the Roslyn symbol graph stored in .csmesh/graph.json. Incremental by default: only the files that changed since the last index are re-bound, and their symbols keep their existing identity so every edge into them survives the edit. Falls back to a full pass when an edit touches something that binds across files — an interface declaration, a handler, a container registration. The .csmesh/ directory is added to .git/info/exclude when it is created, so it never shows up as untracked in a work repository.

csmesh index
csmesh index --full          # force a full re-index of every in-scope project
csmesh index --all           # include projects no solution file builds
csmesh index --repo ./src

csmesh trace <Type.Member>

Follows execution pathways through method calls, interface dispatch, MediatR, and constructor invocations.

csmesh trace PaymentController.Post --budget 600
csmesh trace OrderService.Submit --depth 3

csmesh impl <IInterface>

Finds all implementations of an interface, ranking DI-bound registrations first.

csmesh impl IPaymentGateway --budget 600
csmesh impl IOrderRepository

csmesh blast-radius <Type.Member> (alias: blast)

Discovers direct callers, transitive callers, and reachable entrypoints affected by modifying a member.

csmesh blast-radius Order.Status --budget 800
csmesh blast PaymentService.Process --depth 2

--writes answers the narrower question "where is this written, not read". It returns only the sites whose edge carries the Write role, and takes one reverse interface hop so a write through an interface-typed reference is included and marked [via-interface].

csmesh blast-radius Order.Status --writes

A member-access edge carries a role: Read, Write, Subscribe (an event +=/-=, which never counts as a write), or Read|Write for a compound assignment, ++/-- or a ref. --writes selects the edges with Write. Two things are deliberately not recorded: writes to a target with no source declaration (a property setter inherited from a package has no node to point at), and attribute named arguments, which are metadata rather than a body access.

csmesh entrypoints [filter]

Finds HTTP endpoints ([HttpGet], [HttpPost], Blazor @page), message handlers, consumers, and background services.

csmesh entrypoints
csmesh entrypoints payments
csmesh entrypoints "POST /orders"

csmesh context <Type.Member>

Everything structural about one symbol in a single call: signature, members, callers, callees, implementations and the entrypoints above it. Replaces a trace plus an impl plus a blast-radius.

csmesh context OrderService --budget 900
csmesh context IPaymentGateway.Authorize --depth 2

csmesh path <From> <To> (alias: why)

The shortest route between two symbols, across DI bindings and MediatR dispatch. Answers "how does this controller ever reach that repository".

csmesh path PaymentController.Post SqlOrderStore.Save
csmesh why OrderController.Post CreateOrderHandler.Handle --budget 500

csmesh cycles

Circular dependencies between types, namespaces or projects. Reports one concrete loop per component rather than an unordered set.

csmesh cycles
csmesh cycles --project
csmesh cycles --namespace --under src/Domain

csmesh diff [ref]

The symbols a git change touched, and what they reach. Defaults to the working tree against HEAD.

csmesh diff
csmesh diff --staged
csmesh diff origin/main --budget 800

csmesh changes

Bindings, dispatches and implementations that appeared or vanished since the previous index — the structural change, not the textual one. Warns when a DI binding or a MediatR dispatch no longer resolves, which the compiler will not catch and mocked unit tests will not fail on.

csmesh changes
csmesh changes --calls --budget 1200

csmesh review [base]

The same structural comparison as changes, but against a named git revision instead of whatever the last index happened to see — the question a pull request or a CI gate actually asks. Defaults to the merge base with the remote's default branch, cached per commit so a second run is fast. --accept writes the current findings to .csmesh/accepted.txt; accepted findings stop being reported, and dead entries are pruned automatically once the base moves past them. Exits 5 when something unaccepted remains, so a pipeline can gate on it without parsing prose. When the index predates HEAD the comparison is refused rather than guessed at — exit 4, or 64 for --accept, since findings from the wrong current side must not be written to the baseline.

The base revision is checked out into a clean worktree, but it is compiled against this working tree's built reference set — the runtime pack plus the working tree's bin/ DLLs — not the checkout's empty bin/. Indexing it against its own tree would leave every package type unbound, drop the DI/MediatR/route edges those types produced and shift symbol keys, and review would report a false 5 on a tree that did not change. The cache is keyed on that reference set, so a base built by an older binary or against a changed bin/ is rebuilt rather than reused. When a reference input changed in the range (*.csproj, *.props, *.targets, *.sln, *.slnx, Directory.Packages.props, packages.lock.json, global.json), review still reports normally and adds one warning line on stderr — a reference_inputs_changed field in --json — because the graph cannot see a dependency change as an edge.

csmesh review                        # vs. the merge base with the default branch
csmesh review origin/main --calls
csmesh review --accept               # bless the current state as the new baseline

csmesh silence <symbol> [<target>] (alias: why-not)

Why a query came back empty. Exit 1 from any other command means the graph had nothing; it does not say whether the symbol was mistyped, lives in a package, was never bound because the solution was not built, or is reached only through a container scan. Those call for four different next actions. Given a selector whose name resolves but whose parameter list matches no overload, it lists the overloads that exist, each with its selector, and still exits 1.

csmesh silence IPaymentGateway
csmesh why-not OrderController.Post SqlOrderStore.Save

csmesh unresolved

Where the indexer failed, grouped by reason. Run this when an answer is thinner than expected.

csmesh unresolved
csmesh unresolved --kind di

csmesh usage

Displays local invocation analytics, token spend, caller attribution, and latency percentiles.

csmesh usage           # Summary for last 7 days
csmesh usage --days 30 # Summary for last 30 days
csmesh usage --tail 10 # Last 10 raw invocations

csmesh doctor

Diagnoses index freshness, dirty files, caller attribution, and agent skill configurations. It warns when a project's compilation reports CS8795 — a source generator whose output is not on disk — naming the project, the count, and the EmitCompilerGeneratedFiles=true build that fixes it. It also warns when a PackageReference names an in-scope project's package id: that project's types are not bound through the package, and a ProjectReference is the fix. It also names the solution files that were found but did not fully decide scope, showing how many of their project paths matched on disk and why one could not be read, and states when the scope fell back to the ProjectReference closure.

csmesh doctor

csmesh install [OPTIONS]

Installs agent skill and rule files and optional MCP server integrations for AI assistants.

csmesh install                      # Install skill and rule files for current repo
csmesh install --mcp                # Register csmesh as an MCP server
csmesh install --all                # Install skills and MCP server
csmesh install --global             # Install globally across all user agents
csmesh install -g --agent cursor   # Install globally for Cursor only

csmesh uninstall [OPTIONS]

Safely removes agent skill/rule files, cleans up generated blocks, and unregisters MCP server integrations.

csmesh uninstall                    # Remove skill and rule files from current repo
csmesh uninstall --mcp              # Unregister MCP server
csmesh uninstall --all              # Remove skills and MCP server
csmesh uninstall --global           # Remove globally across user config
csmesh uninstall -g --agent cursor # Remove globally for Cursor only

csmesh serve

Exposes csmesh query tools to AI agents as a Model Context Protocol (MCP) server over stdio.

csmesh serve
csmesh serve --repo ./src

⚖️ The Recommended Hybrid Workflow: csmesh vs. grep

A symbol graph is not a replacement for text search or reading code; it is a replacement for blindly hunting for code. The most effective engineers and agents combine both tools:

                  ┌─────────────────────────────────────┐
                  │          What are you asking?       │
                  └──────────────────┬──────────────────┘
                                     │
           ┌─────────────────────────┴─────────────────────────┐
           ▼                                                   ▼
┌──────────────────────┐                           ┌──────────────────────┐
│ Structural / Graph   │                           │  Lexical / Textual   │
├──────────────────────┤                           ├──────────────────────┤
│ • Call hierarchies   │                           │ • String literals    │
│ • Who calls whom     │                           │ • Error messages     │
│ • Interface dispatch │                           │ • Config keys & YAML │
│ • Impact analysis    │                           │ • Docker / scripts   │
│ • Entrypoint routing │                           │ • Enum constants     │
└──────────┬───────────┘                           └──────────┬───────────┘
           ▼                                                   ▼
       csmesh                                            grep / ripgrep
           │                                                   │
           └─────────────────────────┬─────────────────────────┘
                                     ▼
                    ┌─────────────────────────────────┐
                    │      Direct File Inspection     │
                    │ (Evaluate if/else, error flow)  │
                    └─────────────────────────────────┘

🎯 Deterministic Exit Codes

csmesh uses strict, deterministic exit codes so automated agents can branch reliably without fuzzy text parsing:

📊 Telemetry & Audit Logging

Every invocation records an audit log entry in .csmesh/usage.jsonl (local to the repository, never sent to external servers). Keys are snake_case; schema_version is 2 for the current record format, and a line written before the field existed reads as 1:

{"schema_version":2,"ts":"2026-09-03T15:15:42Z","caller":"claude-code","caller_via":"env:CLAUDECODE","tty":false,"cmd":"trace","args":"PaymentController.Post --budget 600","budget":600,"exit":0,"ms":84,"out_tokens":125,"would_be_tokens":125,"reserved_tokens":0,"files_referenced":3,"nodes":160,"edges":380}

Caller detection automatically attributes queries based on environment variables and process trees (claude-code, cursor, windsurf, cline, antigravity, terminal-human).

To disable telemetry entirely, pass --no-telemetry or set CSMESH_NO_TELEMETRY=1.

📄 License

This project is licensed under the MIT License.