Give a Team Governed Coding Agents
Purpose
This playbook gives the running order for putting a team's coding agents behind HYPR AgentPass™. Each developer then runs Claude Code through the gateway, with the tools their role allows, and a supervisor who approves from a phone.
Each step is a summary. The detail, with screenshots, field values and caveats, is on the page the step links to.
When you finish:
- A developer's first agent connection is held for approval.
- The agent sees only the MCP tools its supervisor's role permits.
- The Request Log attributes every request to a person.
Architecture
A local agent's traffic reaches the gateway. The gateway checks the agent's identity and its supervisor's role, then forwards to the provider or an MCP connector. Approvals go to the supervisor's phone. For the diagram and the request path, see Architecture: The Request Path.
Prerequisites
You need the following:
- An OpenID Connect provider for console sign-in
- A HYPR tenant for supervisor passkeys
- An account with the AI provider the team uses
- The endpoints and credentials of the MCP servers the team needs
For the full list, see Prerequisites.
Procedure
Complete these tasks in order.
Connect Console Sign-In and Assign Roles
Configure console SSO against your identity provider. Then give each developer a supervisor role, and each administrator an administrator role. The Humans tab of People shows who has which role.
See Signing In to the Console and Roles and Permissions.
Add the AI Provider Connector
Add the connector for the team's provider, and set its Onboarding Mode to Require Approval. Each new agent's first connection is then held until its supervisor approves it.
See Anthropic and Onboarding Mode.
Add and Publish the MCP Connectors
Add one MCP Server connector for each tool the team needs. Leave Publish to endpoint catalog on, so managed workstations pick the connectors up automatically. A developer who adds a connector to their agent by hand uses its Gateway MCP URL.
See MCP Servers and Provisioning MCP Tools.
Scope Tools by Role
On each role's Agent tools permission tab, permit only the tools that role's agents may call. An agent is offered nothing its supervisor's role cannot use.
See Controlling MCP Tool Access by Role.
Set Up Mobile Approvals
Connect the gateway to your HYPR tenant, so supervisors can enroll a passkey. Then configure push delivery, so approval requests reach their phones. A test push confirms the path.
See Connecting to Your HYPR Tenant and Notifications.
Hand the Supervisor Guide to the Team
Start each developer at Being a Supervisor. The guide walks them through these tasks in order:
- Install the HYPR app for iOS or Android. See Getting the HYPR App on iOS or Getting the HYPR App on Android.
- Enroll a passkey. See Setting Up Your Approval Passkey.
- Point their agent at the gateway, and approve its first connection. See Onboarding Your Agent.
- Add the MCP connectors they need. See Connecting to a Gateway MCP Connector.
Validate
Have one developer point their agent at the gateway, and check the following:
- Their phone receives the onboarding request, and approving it releases the agent's first request.
- In the Request Log, that request is attributed to the agent and its supervisor.
- The agent's tool list shows only the role's permitted tools.
See Approving and Denying Agent Actions.
Logs and Audit Trail
Every request the team's agents send is in the Request Log. Agent Session Forensics reconstructs a whole coding session: the files touched, the commands run and the tools called.
See Reading Your Request Log and Agent Session Forensics.
Related
- Local Agents — what Endpoint Guard does for each coding agent
- Require a Person for High-Value Agent Actions — add approval policies once agents are onboarded
- See and Govern the AI Tools Already on Your Workstations — enforce routing for tools the team already runs