Enabling Managed Desktop Tools
Overview
In HYPR AgentPass™, you manage desktop tools in the Desktop Tools view under Oversight. There you turn managed mode on for your organization and choose which desktop AI tools the gateway manages. You also set how each tool is routed and enforced, and see what every enrolled workstation has applied. Managed mode stays off until you enable it here.
Managing desktop tools is an administrator task. Opening the view needs permission to view settings, and changing anything in it needs permission to edit settings. By default, operators can view settings but not edit them, so they see the view read-only. Supervisors see neither the navigation item nor the controls.
Before You Begin
Managed Desktop Tools uses the same enrolled workstations and signed channel as Agent Observability. Have these in place first:
- Agent Observability is enabled. Workstations fetch their managed configuration over the observation channel. While observation is off, the gateway turns enrolled workstations away and they receive no configuration.
- Your workstations are enrolled. A workstation that has not enrolled receives nothing, so managed mode has no effect on it until it enrolls. See Enrollment Tokens.
- Your organization's gateway address is configured. Routing and MCP provisioning give each tool your organization's public gateway address. Confirm with your HYPR representative that it is set for your organization.
- A provider connector exists for each tool you want to route. Claude Code and Claude Desktop route through an Anthropic connector, and Codex through an OpenAI connector. A tool with no enabled connector for its provider is still managed, but not routed. See Configuring Connectors.
Open the Desktop Tools View
In the console, open Oversight → Desktop Tools. The view is a single page. From top to bottom it holds the managed mode switch, the configuration cards, the Save and Reset to default buttons, and the Devices dashboard.
Turn Managed Mode On
Turn on the Managed mode switch. It takes effect immediately, without Save. On its next check-in, each enrolled workstation applies your configuration to the tools you selected.
While managed mode is off, enrolled workstations receive a configuration that leaves their tools unmanaged, so nothing changes on a developer's machine.
Turning managed mode off again is your organization-wide off switch. Every workstation stands down on its next check-in. It removes any egress blocks and returns its managed tools to the settings it backed up. For per-workstation controls that stop short of this, see Managed Devices.
Choose the Tools to Manage
Under Managed tools, select each desktop AI tool the gateway should manage. Tags beside each tool show the capabilities it supports: route, mcp, enforce and hooks.
| Tool | Provider | Capabilities |
|---|---|---|
| Claude Code | Anthropic | route, mcp, enforce |
| Claude Desktop | Anthropic | route, mcp, enforce |
| Codex | OpenAI | route, mcp, enforce |
| Cursor | — | mcp, enforce, hooks |
A tool you do not select stays unmanaged, even while managed mode is on. Selecting a tool reveals the routing and enforcement controls that apply to it. The Inference routing card appears only when a selected tool can route and your organization has an enabled connector for its provider.
Set the Behavior
The Behaviour card holds two organization-wide settings:
- When the gateway is unreachable is Fail open (the default) or Fail closed. It decides what a workstation does with a tool's egress block when it cannot reach the gateway. See Outage Behavior.
- Poll interval (seconds) sets how often each enrolled workstation checks in for configuration, from 10 to 3600 seconds. The default is 60. A shorter interval gets your changes to workstations sooner. A longer one reduces traffic on large fleets.
Click Save to publish your configuration. Every enrolled workstation picks it up on its next check-in.
Reset to default discards your organization's configuration, and returns it to the platform defaults your organization inherits.
Reset to default takes effect as soon as you click it, with no confirmation step. Note your current configuration first if you might want it back.
Capability Awareness
Each tool supports a different set of capabilities. Each workstation also advertises, when it enrolls, what it can apply on its operating system. The gateway sends a tool only the configuration that both the tool and the workstation support:
- Route inference is supported by Claude Code, Claude Desktop and Codex. Cursor cannot route, so it is observed through hooks instead.
- Provision MCP tools is supported by all four tools.
- Enforce egress is supported by all four tools.
- Observe through hooks is used for Cursor.
Claude Desktop management, and Claude and Codex channels, apply on macOS workstations only.
The gateway does not send an unsupported capability. The workstation reports it as unsupported, not as a failure. Cursor is therefore fully managed for the capabilities it supports, and never appears half-configured. For what each operating system's endpoint client applies today, see Platform Support.
Related
- Routing and Observation — choose the provider connector to route through, or observe tools that cannot route
- Egress Enforcement — block direct traffic to provider hosts
- Managed Devices — see applied configuration and control individual workstations