GliderTrace setup options

Workspace and worktrees

The installation guide sets --workspace. This directory defines trusted paths and the default artifact location.

Without --workspace, GliderTrace uses its launch directory. The argument --workspace . is equivalent.

Use trace_status to check workspace roots and runner policies. Restart the server to correct its root before executing a command.

Project scope determines which client loads a configuration. The path arguments determine which files the server can access.

The default absolute paths select one fixed checkout. Update those paths in each worktree; avoid committing machine-specific paths.

For portable relative paths, set the server launch directory to the worktree root. Relative paths resolve from that directory, not the configuration file.

Git does not copy ignored configuration files into new worktrees. Copy local files when needed, and use one server process per active worktree.

Compare git rev-parse --show-toplevel with trace_status before you query or change code. Correct a mismatched path and reconnect.

Agent instructions

Add this instruction to your project instructions after the connection works. Use CLAUDE.md for Claude Code or AGENTS.md for Codex.

For another client, use its documented project instruction file.

Use GliderTrace for .NET restores, builds, tests, workspace commands, and stored runtime evidence. Before any run, call trace_status and confirm the intended repository or worktree appears in the workspace roots. Changing directories does not retarget GliderTrace. If the root is missing, restart GliderTrace with --workspace. Use trace_add_workspace only when runtime workspaces are enabled and the user requested that root.

Updates and expired packages

Packages expire one month after release. Update the executable, then restart each client or separately managed server.

Use the same installation method for updates. Check the version again, then restart the server. Package expiry is separate from the license.

dotnet tool update --global glider-trace
glider-trace --version

If the connection fails

Executable not found: run glider-trace --version in your terminal. Restart the client after installation so it receives the updated PATH.

Check that the .dotnet/tools directory is on PATH. If necessary, use the full executable path in your client configuration.

If a plugin uses npx, complete its package download with the same user and npm cache as the client. Reconnect afterward.

A cached npx package can still require a registry check. A tool timeout does not extend the initial connection timeout.

Connection refused or server missing: check the client configuration location, JSON or TOML syntax, project trust, and server logs.

Timeout: wait for initial workspace preparation. Increase the client startup or tool timeout only if its documentation supports that setting.

Wrong workspace or failed load: check trace_status, correct the path in the connection entry, and restart the server.

If a server with this name already exists, edit its entry. Do not append another entry with the same name.

HTTP and shared servers

Use HTTP only when you need a separately managed server. Start it in your project directory and keep the terminal open. For Glider, replace src/App.slnx with your solution or project path.

glider-trace --transport http --port 5003 --workspace . --default-timeout 30m

The server keeps its own workspace when a client changes directories. Use separate ports for simultaneous workspaces.

Keep this connection on localhost. Remote access requires separate authentication and network controls.

Replace the local server entry with this HTTP entry. Keep other client settings and servers.

.mcp.json

{
  "mcpServers": {
    "glider-trace": {
      "type": "http",
      "url": "http://localhost:5003/mcp"
    }
  }
}

Plugins as an alternative

The Claude Code and Codex plugins bundle a product skill and a stdio server configuration. Install the executable first.

Use the plugin instead of the manual MCP entry. Check its workspace with the status tool before use.

In Claude Code:

/plugin marketplace add glidermcp/glidermcp
/plugin install glider-trace@glidermcp

In Codex, add the marketplace, then choose the product in the Plugin Directory or /plugins browser.

codex plugin marketplace add glidermcp/glidermcp