Files and locations
AITrax writes to a set of paths under your home directory. This page lists every client-side path and what it contains. Server-side paths are out of scope here.
Knowing these paths helps when diagnosing setup problems or reporting an issue. For a faster enumeration of what setup actually wrote on your machine, see Read the path inventory from the command line.
System paths
System paths are written by aitrax setup system.
The following table lists the core system paths:
| Path | Contents | OS |
|---|---|---|
~/.codetogether/tracker/aitrax | Native binary (core build, handles daily tracking) | macOS and Linux |
%USERPROFILE%\.codetogether\tracker\aitrax.exe | Native binary (core build, handles daily tracking) | Windows |
~/.codetogether/tracker/aitrax-full | Full build (owns setup, token redemption, and diagnostics) | macOS and Linux |
%USERPROFILE%\.codetogether\tracker\aitrax-full.exe | Full build (owns setup, token redemption, and diagnostics) | Windows |
~/.codetogether/tracker/aitrax.json | User-level configuration: server URL and endpoint | All |
~/.codetogether/tracker/repos.json | Registry of the repositories configured for tracking on this machine | All |
~/.codetogether/aitrax.jsonl | Local audit log recording binary download, spawn, and handshake failures | All |
The audit log is the most useful attachment when reporting a tracking problem, because it records failure paths that produce no visible error in the IDE. It rotates by size.
$ ls ~/.codetogether/tracker/
aitrax aitrax-full aitrax-full.etag aitrax.json repos.json
User-level integration files
aitrax setup system writes configuration for each AI tool that is installed. Only the
tools that are present on the workstation receive entries; a missing entry for a tool you
do not use is correct, not a failure.
- macOS and Linux
- Windows
The following table lists the user-level integration files aitrax setup system writes
on macOS and Linux:
| Tool | Path | Contents |
|---|---|---|
| Claude Code | ~/.claude/settings.json | Managed hooks entries (SessionStart/SessionEnd) and OTEL env block |
| Claude Code CLI | ~/.claude.json | User-level mcpServers.aitrax entry |
| Cursor | ~/.cursor/mcp.json | User-level mcpServers.aitrax entry |
| VS Code Copilot | ~/Library/Application Support/Code/User/mcp.json (macOS) | User-level servers.aitrax entry |
| VS Code Copilot | ~/.config/Code/User/mcp.json (Linux) | User-level servers.aitrax entry |
| VS Code Copilot OTEL | ~/Library/Application Support/Code/User/settings.json (macOS) | github.copilot.chat.otel.* Copilot OTEL settings |
| VS Code Copilot OTEL | ~/.config/Code/User/settings.json (Linux) | github.copilot.chat.otel.* Copilot OTEL settings |
| JetBrains Copilot | ~/.config/github-copilot/intellij/mcp.json | User-level servers.aitrax entry |
| Copilot CLI MCP | ~/.copilot/mcp-config.json | User-level mcpServers.aitrax entry |
| Copilot CLI hooks | ~/.copilot/hooks/aitrax.json | User-level hook entries |
| Codex | ~/.codex/config.toml | mcp_servers.aitrax entry and, when no [otel] table exists, an OTEL log exporter |
| Kiro | ~/.kiro/settings/mcp.json | User-level mcpServers.aitrax entry |
| OpenCode | ~/.config/opencode/opencode.json | mcpServers.aitrax entry and correlation plugin reference |
| Copilot CLI OTEL env | .bashrc, .zshrc, .profile | Managed shell block with COPILOT_OTEL_* export settings |
The following table lists the user-level integration files aitrax setup system writes
on Windows:
| Tool | Path | Contents |
|---|---|---|
| Claude Code | %USERPROFILE%\.claude\settings.json | Managed hooks entries (SessionStart/SessionEnd) and OTEL env block |
| Claude Code CLI | %USERPROFILE%\.claude.json | User-level mcpServers.aitrax entry |
| Cursor | %USERPROFILE%\.cursor\mcp.json | User-level mcpServers.aitrax entry |
| VS Code Copilot | %APPDATA%\Code\User\mcp.json | User-level servers.aitrax entry |
| VS Code Copilot OTEL | %APPDATA%\Code\User\settings.json | github.copilot.chat.otel.* Copilot OTEL settings |
| JetBrains Copilot | %LOCALAPPDATA%\github-copilot\intellij\mcp.json | User-level servers.aitrax entry |
| Visual Studio | %USERPROFILE%\.mcp.json | Top-level servers.aitrax entry |
| Copilot CLI MCP | %USERPROFILE%\.copilot\mcp-config.json | User-level mcpServers.aitrax entry |
| Copilot CLI hooks | %USERPROFILE%\.copilot\hooks\aitrax.json | User-level hook entries |
| Codex | %USERPROFILE%\.codex\config.toml | mcp_servers.aitrax entry and, when no [otel] table exists, an OTEL log exporter |
| Kiro | %USERPROFILE%\.kiro\settings\mcp.json | User-level mcpServers.aitrax entry |
| OpenCode | %USERPROFILE%\.config\opencode\opencode.json | mcpServers.aitrax entry and correlation plugin reference |
| Copilot CLI OTEL env | PowerShell 5.1 and 7+ user profiles | Managed shell block with COPILOT_OTEL_* environment settings |
If a tool is configured to use a non-default home directory (for example, Codex respects
$CODEX_HOME/%CODEX_HOME%, and Copilot CLI respects $COPILOT_HOME/%COPILOT_HOME%),
the path resolves relative to that override rather than the user home.
Read the path inventory from the command line
To see exactly which of the paths from this page setup owns on your machine — and therefore what uninstall would remove — run:
aitrax uninstall system --dry-run
This reports planned removals without changing anything. It reflects the actual state of the machine rather than a fixed list, so it stays correct even as tools are added or removed. The following output is an illustrative shape — paths and byte-for-byte formatting will differ on a real machine — not a captured transcript:
$ aitrax uninstall system --dry-run
Would remove (system):
/Users/dev/.codetogether/tracker/aitrax
/Users/dev/.codetogether/tracker/aitrax-full
/Users/dev/.codetogether/tracker/aitrax.json
[...]
Related
- Verify your installation — confirming setup is complete and data is arriving.
- Remove AITrax tracking — removing what is listed here.
- AITrax CLI reference — the commands that report on and manage these paths.