Approving and Denying Agent Actions
When a policy calls for a person, HYPR AgentPass™ holds the action and asks you. The agent waits, so nothing reaches the provider until you decide.
Set up your passkey first. See Setting Up Your Approval Passkey.
What Reaches You
A request arrives as a notification on your phone. Opening it shows what you need to decide:
- Which agent is asking
- What it wants to do, with a preview of the content where the action carries any, such as the message it would send
Read the agent name and the action together before you decide. This step exists to catch an agent acting on a target you do not recognize.
You can also answer the same request in the administration console, under Oversight → Approvals. See Approvals in the Console.
Your Options
Your answer decides what happens to the agent.
| You choose | What happens to the agent |
|---|---|
| Approve on Android, Allow on iPhone | The gateway releases the action, and the agent's traffic continues to the provider. Your phone asks for your face, fingerprint or PIN to confirm |
| Deny | The gateway stops the action, and the agent does not reach the provider. On Android, you confirm once more. On iPhone, it takes effect immediately |
| Answer | When the agent asked you a question instead of asking permission, your reply is routed back so it can carry on |
When your organization requires signed approvals, approving is signed with your passkey. The record therefore shows the decision was yours, not merely that someone with access clicked a button.
Requests Do Not Wait Forever
Each request stays open for a limited time. If it passes without an answer, the request expires, and the action does not proceed. Expiry is never a silent approval.
The agent is told to ask again, instead of being left waiting. An expired request therefore becomes a fresh notification, not a stuck agent.
Requests to reauthorize a connector are deliberately short-lived. Answer those promptly, or expect a new one.
Onboarding Approvals Are Time-Limited
Approving an agent's first connection grants it access for a period, not permanently. When that period ends, the agent's next request is held again, and a new approval reaches you as a re-onboarding request. Answer it the same way, and the agent resumes.
That is why an agent you approved last month can ask again without anything having gone wrong.
Turning an Agent Off
You can turn off an agent you own from the mobile app, without waiting for it to ask you something. Turn an agent off when it is behaving in a way you did not intend, and you want it stopped now, not at its next approval.
You can turn it back on only if you turned it off yourself. When an administrator turned it off, ask them to turn it back on. See Who Can Turn an Agent Off and On.
On iPhone, the switch is in the agent's detail screen, on the card that reads Agent is on or Agent is off. In a conversation with the agent, tap + next to the message box: the switch is at the top of the menu that opens.
Once an agent is off, the gateway refuses its calls. A request already in progress when you flip the switch is allowed to finish.
What the App Tells You
When you turn an agent off, the app tells you what the gateway took back. On iPhone the message appears under the switch.
| Agent | What the message says |
|---|---|
| An agent on a workstation, such as Claude Code or Codex CLI | Agent disabled. followed by what was cut off: how many channel sessions were revoked, what happened to the agent's live connection, and how many AgentCore sessions ended, when there were any. For example: Agent disabled. 2 channel sessions revoked · live connection closed |
| A cloud agent | Agent disabled. New sessions are blocked and running sessions are being interrupted. |
The live connection is the channel the agent uses to receive your messages during a conversation. The message reports it in one of three ways:
| The message says | Meaning |
|---|---|
| live connection closed | The gateway closed the agent's live connection |
| live connection closing within 30 s | The connection is being closed and is gone within 30 seconds |
| no live connection | The agent had no live connection open |
When the message reads only Agent disabled., the agent is off and the gateway reported no further detail.
Turning an agent back on shows no message. The switch and the agent's status show that it is on.
Who Turned It Off
While an agent is off, its detail screen shows who switched it off and when, for example Disabled by jane.smith@example.com followed by how long ago it happened. The line appears when the gateway has recorded who made the change. After you turn an agent off yourself, it appears the next time the agent list refreshes.
When the Switch Does Not Move
If the gateway refuses the change, the agent keeps its previous status and the app says why.
| The app says | What it means | What to do |
|---|---|---|
| You don't manage this agent, so you can't switch it. | The agent is not one you own or supervise | Ask the agent's owner or your administrator to change it |
| This agent is in a conflicted state and can't be switched. | The gateway is holding the agent in a state that blocks status changes | Ask your administrator to review the agent |
| Couldn't change the agent's status. | The change did not go through | Try again |
Related
- Setting Up Your Approval Passkey — enroll before approvals can reach you
- Policies — what decides that an action needs you
- Viewing the Request Log — what happened after you decided