Managed Desktop Tools: Overview
Overview
Managed Desktop Tools lets HYPR AgentPass™ configure and enforce the desktop AI coding tools your developers run on enrolled desktops. It starts with Claude Code, Claude Desktop, Codex and Cursor. In the console, you set it up on Desktops → Desktop configuration → Configuration.
Observation only watches these tools. Managed Desktop Tools drives them. The gateway routes their inference through the gateway where the tool supports it, and provisions your organization's MCP tools. It also connects supported sessions to supervisors, and can block direct traffic to provider hosts.
Managed Desktop Tools builds on Endpoint Guard observation. The enrolled desktops that report AI tool activity also receive and apply the configuration you set here. You must enroll desktops first. See Enrolling Desktops.
See and Govern the AI Tools Already on Your Workstations sequences enrollment, discovery, routing and enforcement end to end.
Opening this area needs Settings: View, which Admin, Operator and Auditor have. Changing it needs Settings: Edit, which Admin has, so other roles see it read-only.
What You Can Do
Once a desktop is enrolled and Configure agents from AgentPass is on, each configured tool applies the configuration the gateway resolves for it:
- Route inference through the gateway. Tools that support it, Claude Code, Claude Desktop and Codex, are pointed at your organization's gateway address. Their traffic is then attributed and governed like any other agent's, and no developer is ever handed a provider key. See Routing and Observation.
- Observe tools that cannot route. Cursor cannot route its inference through the gateway. Instead, its own event hooks report its activity to Desktop Activity, with everything else. See Routing and Observation.
- Provision MCP tools automatically. The MCP servers your gateway publishes reach the managed tools, so a developer's tools already list the tools your organization provides. See Provisioning MCP Tools.
- Connect supervisors to local sessions. On macOS, Endpoint Guard runs managed channels for Claude Code and Codex. They carry supervisor messages and agent replies between the workstation and AgentPass. See Claude and Codex Channels.
- Add AgentPass instructions. For Claude Code and Codex, keep a short AgentPass note in the tool's instructions file, so agents expect approval notices. See Agent Configuration.
- Enforce egress. Per tool, block direct traffic to provider hosts so inference cannot bypass the gateway. You choose what happens to the block when AgentPass can't be reached. See Egress Enforcement.
Apart from channels, each of these is a checkbox on the tool's card, so you choose them per tool. Each tool supports a different set of these capabilities, and each desktop advertises what it can apply on its operating system. The gateway sends a tool only what the tool supports, what the desktop can apply and what you ticked. Cursor, for example, is provisioned with MCP tools and observed through hooks, but never asked to route. See Platform Support for what each operating system applies.
How Configuration Reaches a Desktop
You set your organization's intent in the console, and each enrolled desktop applies it on its next check-in:
- The gateway resolves a configuration for each desktop. It layers your organization's settings on top of the HYPR defaults, adjusted by that desktop's own settings. It delivers the result over the signed channel the desktop already uses to report activity. The configuration carries gateway addresses and hostnames only, never a secret.
- The desktop applies it to each managed tool in a safe order. Routing comes first, then MCP servers and hooks, and egress enforcement last. Before its first change to a tool, a Mac backs up the tool's original settings, and a Windows desktop records each value it changes. Either way, it merges with the developer's own settings instead of replacing them.
- The desktop reports back what it applied, per tool and per capability. Each desktop's Managed configuration shows whether it is in the state you intend. See Managed Desktops.
Configuration arrives as data, not built into the client. Adding coverage for another desktop tool is therefore a configuration change, not a desktop update.
Where to Start
- Enroll your desktops. See Getting Started with Desktops and Enrolling Desktops.
- Make sure a provider connector exists for each tool you want to route. See Connectors.
- Turn on Configure agents from AgentPass, turn on each tool to configure, and choose its capabilities. See Agent Configuration.
- Once the fleet reports its routing as applied, turn on egress enforcement. See Egress Enforcement.
- Check each desktop's Managed configuration, and troubleshoot individual desktops from there. See Managed Desktops.
Related
- Agent Configuration — turn configuration on and choose the tools and capabilities
- Platform Support — what the endpoint client applies on macOS and Windows
- Enrolling Desktops — enroll the desktops this feature builds on