Skip to main content

​
Agent settings & subscribers

​
Agent settings

Open an agent, then Settings (or Configuration) to adjust:

​
Display name

Update the name shown for this agent in the app and in notifications.

​
Default timeout

Default timeout is the default expiry for new approval requests, in seconds (minimum 30). The server applies these saved defaults whenever a create request does not override them.
  • REST (POST /v1/approvals) — You may omit timeout in the JSON body; the server merges these dashboard defaults. You can also send a partial timeout object so only the fields you set override the defaults.
  • MCP — Tools do not accept timeout. New approvals always use the dashboard defaults unless you switch to the REST Agent API for that call. The MCP adapter exposes request_human_approval and create_approval for the same POST /v1/approvals create (pick either name for your client); use get_approval_result to poll. See MCP.

​
Timeout mode

  • Expire with no action — If nobody responds before expiry, the request ends without a human choice (per product behavior).
  • Expire with predefined instruction — If you choose this mode, you must provide instruction text (up to 1000 characters) that applies when the request expires that way.
Save changes when you are done.

​
Delete agent

Owners can delete (deactivate) an agent. The app may ask you to type a confirmation phrase (such as DELETE) to prevent accidental removal. Deactivated agents stop accepting new approvals; historical data follows your product’s retention policy.

​
Subscribers

Open Subscribers for an agent to choose who receives push notifications when new approval requests are created for that agent.
  • The list is limited to members of the same workspace.
  • Toggle people on or off, then save.
  • Subscribers only get notifications if they use the app with notifications enabled on their device.
Fallback: If this agent has no subscriber rows configured yet (for example legacy data or a fresh agent), the service may notify all workspace members instead, so someone still sees new requests. If subscriber rows exist but everyone has turned notifications off for this agent, the service does not override that—configure at least one subscriber with notifications on if you want pushes. Workspace owners manage this list; members can still respond to approvals in the app if they have access, even if they are not subscribers.