Skip to content

Approvals

Some actions hand out access, send your data somewhere new, or change what runs:

Action Who asks instead of doing it
Creating an API key Every agent and app: the API has no direct way to create one
Adding, removing or re-enabling a webhook endpoint An agent connected through MCP. A coding agent that uses your own token or the command line makes the change as you.
Publishing a version An agent connected through MCP. A coding agent that uses your own token or the command line publishes as you, unless the workspace requires a second person.
Creating a webhook trigger, or rotating its secret An agent connected through MCP. A coding agent that uses your own token or the command line makes the change as you.

When an agent needs one, it asks, and a person who could take the action themselves decides.

  • Publishing a version. A workspace can also require a second person to publish, and then everyone asks. An owner or admin approves the publish, and the person who asked can’t approve their own request.
  • Webhook triggers. A webhook trigger’s URL starts runs, so a workspace owner approves. The actions are trigger.webhook.create and trigger.webhook.rotateSecret. The URL goes to the owner, never to the agent. See Webhook triggers.
  • Running a script that needs approval. A script or environment can require a person to approve its runs, either the runs of agents connected through MCP or every run. The run waits until an owner or admin approves exactly that run, with the same version and inputs.
  1. The agent asks. The request says what the agent wants to do, with the details and a reason, such as “I’m connecting acme-web and need an API key that can read the workspace”. Everyone who could approve it gets a notification.
  2. A person decides. Open the request from the notification or from the link the agent shows you. You see exactly what will happen and why, then choose Approve or Deny.
  3. The action runs as you. It runs with your permissions, and the audit log records it under your name, along with the agent that asked.

A request expires after 24 hours. Once someone approves or denies it, the decision is final.

You can decide a request from your phone:

  1. Turn on push on your phone, once. See Turn on push. On an iPhone, add Reminix to your Home Screen first.
  2. Tap the notification. It opens the request’s page.
  3. Read what will happen. A run’s request names the script, its version and its environment, and lists every input in full.
  4. Choose Approve or Deny.

You can also find the request in the app’s notifications, or under Runs, filtered to Awaiting approval.

Some actions create a secret, such as an API key or a webhook signing secret. The agent never sees it:

  • If the CLI asked: after you approve, the CLI writes the secret straight into a file in your project. It never prints the secret, so an agent working in the terminal can’t read it.

    Terminal window
    reminix workspace approval-requests create --action workspace.apiKey.create \
    --input '{"name":"acme-web","scopes":["workspace:read"]}' \
    --reason "Connect acme-web" --json
    reminix workspace approval-requests redeem <id> --wait --write-env .env
    # Done: … Wrote REMINIX_API_KEY to .env (the value is not shown).
  • If an agent asked over MCP: the action runs when you approve, and you see the secret once, on the approval page.

Three endpoints cover approvals:

Endpoint What it does
GET /v1/workspace/approval-actions Lists what an agent can ask for, each with its input schema and who approves it.
POST /v1/workspace/approval-requests Asks for an action.
GET /v1/workspace/approval-requests/{requestId} Returns the decision.

To ask, you need the workspace.approvals:write scope and a credential that belongs to a person: a personal access token, or an app a person connected. A workspace API key can’t ask.