Skip to main content
Unlisted page
This page is unlisted. Search engines will not index it, and only users having a direct link can access it.
Version: 11.3.0

Managed Desktop Tools: Overview

Overview​

Managed Desktop Tools lets HYPR AgentPass™ configure and enforce the desktop AI coding tools your developers run on enrolled workstations. It starts with Claude Code, Claude Desktop, Codex and Cursor.

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 Agent Observability. The enrolled workstations that report AI tool activity also receive and apply the configuration you set here. You must enroll workstations first. See Enabling Agent Observability.

Playbook

See and Govern the AI Tools Already on Your Workstations sequences enrollment, discovery, routing and enforcement end to end.

note

Managing desktop tools is an administrator task. Opening this area needs permission to view settings, and changing it needs permission to edit settings. By default, operators can view settings but not edit them, so they see this area read-only. Supervisors do not see it.

What You Can Do​

Once a workstation is enrolled and managed mode is on, each managed 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 the same Discovered view as 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.
  • Enforce egress. Per tool, block direct traffic to provider hosts so inference cannot bypass the gateway. You choose whether the block fails open or closed. See Egress Enforcement.

Each tool supports a different set of these capabilities, and each workstation advertises what it can apply on its operating system. The gateway sends a tool only the configuration that both the tool and the workstation can apply. 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 today.

How Configuration Reaches a Workstation​

You set your organization's intent in the console, and each enrolled workstation applies it on its next check-in:

  1. The gateway resolves a configuration for each workstation. It layers your organization's settings on top of the platform defaults, adjusted by any per-workstation overrides. It delivers the result over the signed channel the workstation already uses for Agent Observability. The configuration carries gateway addresses and hostnames only, never a secret.
  2. The workstation 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, the workstation backs up the tool's original settings. It merges with the developer's own settings instead of replacing them.
  3. The workstation reports back what it applied, per tool and per capability. The Managed Devices dashboard shows whether the fleet is in the state you intend.

Configuration arrives as data, not built into the client. Adding coverage for another desktop tool is therefore a configuration change, not a workstation update.

Where to Start​

  1. Enable Agent Observability, and enroll your workstations. See Enabling Agent Observability.
  2. Make sure a provider connector exists for each tool you want to route. See Configuring Connectors.
  3. Turn managed mode on, and select the tools to manage. See Enabling Managed Desktop Tools.
  4. Once the fleet reports its routing as applied, turn on egress enforcement. See Egress Enforcement.
  5. Watch the Managed Devices dashboard, and troubleshoot individual workstations from there.