Endpoint Configuration Locations
This page shows where Endpoint Guard applies managed-tool configuration on a workstation. Each tool keeps its settings in a different place on each operating system. Some tools also have an enterprise location, where the developer cannot override the configuration.
The client writes these files for you. Knowing the locations helps you plan a managed rollout, and answer a developer who asks what changed on their machine.
This page is background for administrators and IT teams. Managed workstations apply this configuration automatically, and nothing here requires manual editing on a developer's machine.
User and Enterprise Locations
Each tool supports up to two kinds of location:
- User locations are in the developer's home directory. A tool is configured there by default. The client merges into them, so the developer's other settings survive.
- Enterprise locations are system-level paths, deployed through your device-management (MDM) tooling. The tool gives configuration in an enterprise location precedence, and a developer cannot override it. This is how you enforce a setting fleet-wide.
The client applies each setting in one location, not both, and records which one it used:
- On macOS, it uses an enterprise file that already exists and that it can write. Otherwise it uses the user location.
- On Windows, an enterprise folder that exists, and that only administrators can change, is enough. The client creates the file in it. Otherwise it uses the user location, when the tool's user file already exists.
How the Client Preserves a Developer's Settings
The client follows three rules when it changes a tool's configuration:
- Record before the first change. On macOS, the client saves a copy of a tool's file before it first changes it. The copy stays unchanged from then on, and is what Restore this desktop's tools to their settings before AgentPass puts back. A file that did not exist is recorded as absent, so restoring removes it. On Windows, the client records each value it changes, with the value it replaced, and restoring puts those values back. A file left with no settings is removed.
- Merge, never overwrite. Routing settings are written to a single key. MCP servers are added to the tool's existing server list. Cursor hooks are appended to each event, alongside the developer's own. A file the client cannot parse is left alone, and reported as a failure.
- Remove only what was added. A workstation stands down when Configure agents from AgentPass is off, or configuration is turned off for that desktop. The client then removes the settings, servers and hooks it added, and leaves everything else in place. The same applies to one tool or capability you turn off. A value the developer had set before, such as a routing address, is put back.
Per-Tool Locations by Operating System
Each tool's configuration lives in the following places. User paths use the developer's home directory, shown as ~. Enterprise paths are absolute.
Claude Code
Routing is applied through the ANTHROPIC_BASE_URL setting:
- Without an enterprise settings file, the client sets it as an environment variable for the developer. On macOS, it reaches Claude Code sessions started after the change. The macOS client also writes the setting into the
envblock of~/.claude/settings.json, which Claude Code reads at every start, so Claude Code is routed even when an app that was already open starts it. On Windows, it takes effect at the developer's next sign-in. - With an enterprise
managed-settings.json, the client writes the setting into that file'senvblock instead, so a developer cannot override it.
MCP servers are written to the user-level Claude Code configuration. The locations are:
| Location | Path |
|---|---|
| User (MCP servers) | ~/.claude.json |
| Enterprise (macOS) | /Library/Application Support/ClaudeCode/managed-settings.json |
| Enterprise (Windows) | C:\Program Files\ClaudeCode\managed-settings.json |
For Claude Code on Windows, the current enterprise location is C:\Program Files\ClaudeCode\. The older C:\ProgramData\ClaudeCode location is deprecated.
Codex
Codex is configured through ~/.codex/config.toml. Routing uses openai_base_url, and MCP servers use the mcp_servers section. The client edits the file in place, and keeps the developer's comments, ordering and other settings. On Windows, the client configures Codex once this file exists.
On macOS, the client also routes the Codex that Xcode runs. It sets openai_base_url in ~/Library/Developer/Xcode/CodingAssistant/codex/config.toml as well as in ~/.codex/config.toml.
On macOS, when the CODEX_HOME environment variable is set, the client follows it instead of ~/.codex. Codex has no separate system-wide location.
Cursor
Cursor is configured for MCP servers and for observation hooks. Its enterprise hooks location differs per operating system:
| Location | Path |
|---|---|
| User (MCP servers) | ~/.cursor/mcp.json |
| User (hooks) | ~/.cursor/hooks.json |
| Enterprise hooks (macOS) | /Library/Application Support/Cursor/hooks.json |
| Enterprise hooks (Windows) | C:\ProgramData\Cursor\hooks.json |
Cursor reads its hooks from every location it supports, and runs all matching hooks. Managed hooks are therefore merged into the hooks file, alongside a developer's own. The managed hooks report to Endpoint Guard only, and never block an action.
Claude Desktop
On macOS, the client configures Claude Desktop through its managed-preferences domain, com.anthropic.claudefordesktop, at /Library/Managed Preferences/com.anthropic.claudefordesktop.plist. It sets the routing to the gateway and the managed MCP servers there, and applies egress blocks to the app.
On Windows, the console applies egress blocks to Claude Desktop. See Supported Platforms and Components.
Enforcing Routing Fleet-Wide
By default, routing is applied in a user location that a developer could change. To make Claude Code's routing mandatory, give the client an enterprise location through your device-management tooling:
- On macOS, deploy
/Library/Application Support/ClaudeCode/managed-settings.jsonas a file owned by root, in a folder owned by root that nobody else can write. The content can be just{}. - On Windows, the folder
C:\Program Files\ClaudeCode\is enough. The Endpoint Guard installer creates it.
The client then writes your gateway address into that file, and Claude Code gives it precedence over anything the developer sets.
Combine routing with Egress Enforcement, so a routed tool also cannot reach its provider directly.
If your organization builds its own endpoint client instead of deploying Endpoint Guard, contact your HYPR representative for the endpoint-client integration guide. It describes the configuration-profile and enforcement interfaces in detail.
Related
- Routing and Observation: how routing is applied to each tool
- Egress Enforcement: how direct traffic is blocked per tool
- Supported Platforms and Components: what each operating system's client applies