navlyn 0.9.2

Navlyn

日本語

Navlyn gives coding agents compiler-resolved facts about .NET code when binding or relationships are uncertain. It focuses on C# and supports some Visual Basic scenarios. It can select a bound overload, read a referenced DLL's implementation, find callers, or investigate a change.

For occasional semantic questions, an agent can call the installed navlyn CLI when needed. A running MCP server is not required. Use navlyn-mcp for repeated semantic calls that benefit from a shared workspace. Both return local JSON facts; ordinary reads, search and clear local edits use normal tools. See routing and CLI integration.

Start with your environment

• Use Navlyn in VS Code with GitHub Copilot
• Use Navlyn in GitHub Copilot CLI
• Use Navlyn in Codex
• Use Navlyn in Claude Code
• Look up a type in a terminal

To help Codex choose when to use Navlyn, see install the Codex routing skill.

Try it in a terminal

You need a .NET 10 SDK that can load the repository you want to inspect. Install the tools from NuGet:

dotnet tool install --global navlyn --version 0.9.2

Open a new terminal at the root of the repository you want to inspect and check that Navlyn can select a workspace:

navlyn doctor --workspace auto

If auto cannot choose one workspace, pass the intended .slnx, .sln, .csproj, or .vbproj path. The 10-minute guide shows an isolated installation and walks through one type lookup.

For repository selection, see workspace configuration. Complete command and result details are in the CLI reference and MCP reference.

The Navlyn commands run locally and do not upload code. They do not edit code, run tests, or prove runtime behavior. Navlyn uses MSBuild to load projects, so run it only on repositories you trust. See limitations and safety notes for details.

Navlyn v0.9.2 requires a .NET 10 SDK and ships only net10.0 tool assets. See the runtime support policy.

Navlyn is released under the MIT License. See LICENSE.