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 agent | Examples | Brought to the gateway by | Identity it carries |
|---|---|---|---|
| Local agent: a harness on a person's workstation that calls a cloud-hosted LLM | Claude Code, Codex CLI, Cursor | Endpoint Guard | Its supervisor's, the person who onboarded it |
| Provider-managed cloud agent: a harness the provider hosts | Microsoft 365 Copilot, AWS Bedrock AgentCore, Anthropic managed agents | Agent Portal and the gateway's connector credential | A 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.