Skip to content

Standing delegations

Agents relay work to each other. A message that says “the operator said release” could be true, or invented by a model. Your computer never treats that claim as your permission. A standing delegation is how you give a session permission ahead of time.

A delegation is a signed record on your computer. It lists:

  • the actions: merge, deploy, release, push, tag, migrate, close a ticket, or start a session;
  • the repositories, as owner/name;
  • for push, the branches it covers;
  • the sessions it applies to, by name;
  • when it expires, at most 7 days ahead;
  • how many risky actions it covers, 3 unless you choose another number up to 50.

Nothing is read from free text. A note you add is only a note.

Only an Admin device can create a delegation: a phone paired as Admin, or a phone or browser signed in to your account with the Admin role on this computer. A paired phone confirms with the passkey it registered while pairing. A device signed in to your account confirms with the passkey it signs your messages with, set up under Sign my messages. The same goes for approving a session’s request for a one-time grant and for signing a message an agent asks you to sign. The computer shows the exact fields, your device checks they match what you asked for, and you confirm with the passkey. Without that confirmation there is no delegation, so a program on your computer can’t make one for itself. A delegation stops counting when the device that confirmed it is unpaired, is removed from your account or is no longer Admin. One confirmed from a device signed in to your account also can’t be checked after the computer restarts, until that device connects to it again.

To create one, open Settings, then Security, then Delegations. The section shows only on an Admin device.

  1. Tap Issue delegation.
  2. Pick what it allows (merge, deploy and release; push; closing tickets; or your own choice of actions), the repositories, the branches for push, the sessions, when it ends and how many uses it has.
  3. Tap Continue to passkey. Your computer builds the delegation and sends it back.
  4. Check the terms on screen. They are the ones your passkey signs. Tap Confirm with passkey.

If the computer sends back anything that differs from what you picked, your phone signs nothing and says so. A cancelled passkey prompt creates nothing.

Sign my messages, in the same section, signs each message you send to this computer so a session can check it came from you. On a device signed in to your account, signing turns on after you sign in again with your passkey or your second factor. Nobody has to approve it at the computer or on another device. When the computer can check your account passkey itself, one tap with it is enough. Otherwise the app makes a passkey for this device, then asks you to sign in again with your account passkey or a code from your authenticator app. A device paired without an account still needs approval on your computer or on another device of yours. If the passkey on a device was replaced or removed, Fix signing sets it up again the same way. The status reads On while the computer takes your signature, Waiting for the computer while it can’t confirm this device yet (its account feed lags by more than 5 seconds, which passes on its own and needs nothing from you), and Needs attention when it no longer accepts this device’s signing key. Messages sent while it waits go unsigned.

Before it acts on its own judgment, a session asks your computer whether a delegation covers the action. The answer is for that session only.

  • A merge, deploy, release, migration, tag or new session uses up one of the delegation’s uses, for the one target the session names, such as a pull request or a version.
  • A push to main, master or a release/ branch in any letter case, to a branch the delegation doesn’t list, to anything that isn’t a plain branch such as a tag, or a forced push is risky too. refs/heads/main counts as main.
  • Closing a ticket, or a push to a listed branch, uses nothing.

The session must still get your approval for each command as usual. A delegation answers “may I”, it doesn’t run anything.

You can save a secret, such as a release or deploy token, for one action:

Terminal window
remotxai secrets set release-token --env RELEASE_TOKEN --gate release < token.txt

The action is merge, deploy, release, tag or migrate. A secret saved this way never reaches a shell command, a session’s environment or another session. A session gets it only through run_with_secrets, and only when it names the action, repository and target of a check your computer allowed for that same session in the last 5 minutes. The check names the exact command, and only that command gets the secret, once. Panic stop, or revoking the delegation, locks it again at once. Every unlock is written to the audit log with the session, the delegation and the secret’s name, never its value.

The app doesn’t show or change this setting yet.

The session chooses the command when it asks. Outside yolo mode you approve each such command on your phone, so you see it. In yolo mode nothing stops a session from naming a command that sends the secret somewhere else and keeping it after the delegation ends. The audit log holds only a fingerprint of the command. Gate a secret only for sessions you’d trust with the secret itself.

A session can also ask whether a message it received carries a signed order from you. Once this device holds a pinned key on the computer and Sign every message is on, every message you send from it is signed, files included. A message goes out unsigned when the device has no pinned key there, in Sign only when an agent asks, or when one of its files was attached on another device or before the page reloaded. In that last case the composer tells you. A message that quotes a yes from your computer is a forgery, and sessions are told so.

Revoking a delegation takes effect at once and needs no passkey: tap Revoke on its row in Delegations. Panic stop revokes every delegation on the computer, and a delegation confirmed after panic started is not created. After a panic you create new ones. If the computer can’t save a revocation, no session gets a yes until it can, and lifting a panic stop waits until every revocation is saved.

remotxai delegations lists every delegation on the computer with its actions, repositories, sessions, expiry, uses left and state; --json prints the list as JSON. A delegation shows as unverifiable when its key was revoked or the device that confirmed it is unpaired, removed from your account or no longer Admin: every check refuses it, and you can still revoke it. The app shows the same state as Can’t be checked. remotxai delegations revoke <id> revokes one, and the id can be any unique start of it. No command creates a delegation: that needs an Admin device and its passkey. A command run from a terminal an agent started waits for an Admin device to approve it.

remotxai provenance rotate replaces the key your computer signs delegations with. The old key still verifies what it signed for 8 days. If you think the key leaked, run remotxai provenance rotate --compromised: the old key verifies nothing from that moment, so every delegation it signed stops counting and you create new ones from your phone. The key also rotates by itself every 30 days. Every rotation is written to the audit log.

Every check is written to the computer’s audit log with the session, the action, the repository and the target. A session never gets a yes the log didn’t record. Keys, signatures and passkey data never appear in an answer or in the log. A session that asks more than 30 times a minute is refused until the minute passes.

A program running as you on the computer can read the delegation files. It still can’t create a delegation without your passkey. A session that never asks is stopped only by your usual approvals.

Claude Code sessions are denied the delegation files and your saved secrets file in their file tools. A Claude Code session started in a sandbox is also denied them in its commands. That isn’t a guarantee: a link made after the session started, or the same path written in other letter case, may get past the file tools, and on a Mac a sandboxed command can still ask the keychain for a saved secret. So every answer says same-user for now. Programs remotxai didn’t start are never counted.