Glider setup recommendations

A few configuration choices decide whether an agent reaches for Glider on a large solution instead of falling back to text search. Apply these after installing.

Preload your solution — the highest-impact setting

Start Glider with --solution so the workspace loads at startup. server_status reports the workspace as ready or loading, with an ETA under workspaceLoading. On a large solution, point --solution at the relevant .csproj and widen later with load. This avoids asking the agent to choose a tool before semantic analysis is ready.

glider --solution C:/repos/app/src/App.sln --default-timeout 30m
# In a project-scoped config, prefer a relative path so it works across git worktrees:
glider --solution src/App.slnx --default-timeout 30m
# Add --workspace <dir> to watch a different root, or --no-watch to disable file watching.

Agent system prompt instruction

Add this product-specific instruction to your MCP client system prompt or project instructions after connecting Glider.

When working in C#/.NET workspaces, prefer glider mcp semantic tools for symbol identity, code relationships, diagnostics, dependencies, impact analysis, and preview-first refactors. Use Scout for repository retrieval and raw text questions. Use the .NET CLI for build and test commands. Preload the solution with --solution, or call load before semantic queries.

Scope it to the project

Prefer a project-scoped MCP config so Glider only starts inside the relevant repository: Claude Code .mcp.json (claude mcp add --scope project), Cursor .cursor/mcp.json, VS Code / GitHub Copilot .vscode/mcp.json, Gemini CLI .gemini/settings.json, OpenCode opencode.json, and Pi .mcp.json. Claude Desktop has only one global claude_desktop_config.json with no per-project scope, so pin a solution there with --solution, or use Claude Code for per-project setups.