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

Where Agents Run

Every agent HYPR AgentPass™ governs runs either on a person's workstation or on a managed cloud platform. Where it runs decides two things: which enforcement point brings its traffic to the gateway, and which identity it carries.

Kind of agentExamplesBrought to the gateway byIdentity it carries
Local agent: a harness on a person's workstation that calls a cloud-hosted LLMClaude Code, Codex CLI, CursorEndpoint GuardIts supervisor's, the person who onboarded it
Provider-managed cloud agent: a harness the provider hostsMicrosoft 365 Copilot, AWS Bedrock AgentCore, Anthropic managed agentsAgent Portal and the gateway's connector credentialA gateway-issued credential per agent. People reach it on their own behalf

Agents that run with nobody at the keyboard, such as scheduled jobs and pipelines, use a service agent identity with its own role and credential.

Whatever the kind, the gateway applies the same four controls once traffic arrives: identity, policy, record and tools governance. Identity explains how the identities differ.