Install GliderTrace

Choose your client and operating system. Follow the three stages below to connect one local workspace.

Operating system

1. Prepare

Requires .NET 10 SDK. Run this in your terminal. The launcher downloads and caches the latest stable package. A global installation is optional.

dotnet tool exec "glider-trace@*" --no-http-cache --verbosity quiet -- --version

The configuration below checks for the latest stable package at each server start. Restart the server to use an update.

Future packages will expire 90 days after release. Existing versions retain their original expiry. Keep the installed product updated. Update instructions →

2. Connect

Project directory

Use the absolute path to your project directory. The server stays tied to this workspace.

Paths stay in this page. They are not saved or sent to analytics.

Example configuration. Enter your project path before you use it.

Merge this entry into the file below. Keep existing settings and other servers. Replace an existing entry with this name instead of duplicating it.

.codex/config.toml

[mcp_servers.glider-trace]
command = "dotnet"
args = ["tool", "exec", "glider-trace@*", "--no-http-cache", "--verbosity", "quiet", "--", "--workspace", "/path/to/MyApp", "--default-timeout", "30m"]
cwd = "/path/to/MyApp"
startup_timeout_sec = 120
tool_timeout_sec = 1800

Project configuration loads only for trusted projects. The same file applies to the CLI, IDE extension, and Codex app.

3. Verify

Trust the project in Codex, then restart its session. Check the configured server in /mcp or the app MCP settings.

Ask your agent

Use GliderTrace trace_status to show the workspace roots and runner policies. Confirm that my project is the intended workspace. Do not execute a command yet.

The status includes your workspace and the available runner policies. Run a test only when you choose the next task.