Approving agent changes

Some teams connect AI agents or automated scripts to a project through Aquilla’s API, for example, a translation pipeline that drafts cells in bulk. When an agent is set up to run in ask mode, it can prepare changes, but committing them needs a human to review and approve first.

Looking for the built-in agent instead?

This page covers agents and scripts connected through the API. Aquilla’s own in-app assistant is documented separately: see Using the AI agent and Agent memory & the project brief. Its staged imports land on the same approval page described below.

Approving a changeset

If an agent is waiting on you, it will hand you an approval link. Opening it brings you to the Approve agent changes page, which shows:

• the project the changes belong to,
• a summary of what will be applied (for example, how many translations will be added or updated),
• any warnings worth a second look, and
• when the approval expires.

From there you can Approve or Reject. Approving lets the agent commit: the changes appear in the project and go to validation just like any edit from a human translator. Rejecting discards the proposed changes; nothing is written to the project.

Who can approve

You need to be signed in, and only the person who owns the credential the agent used to prepare the changes can approve or reject them; a teammate can’t approve on someone else’s behalf.

Approvals are time-limited

An approval link is good for about 15 minutes, and the underlying proposed changes expire after an hour. If either runs out before you act, the link stops working: ask whoever runs the agent to prepare the changes again.

Connecting an agent

Mint personal API tokens for connecting an agent or script to the Agent API right in the app, from Preferences → Account → API tokens (the rest of that page is covered in Your preferences):

Personal access tokens for the Agent API. Anyone holding a token can act with your access, up to its scope — treat it like a password.

When you mint a token you choose:

• A name for the token, so you can tell your tokens apart later.
• A Mode: Ask (“every write waits for your approval”) or Act (“writes apply immediately. Requires a project below where you’re a maintainer.”).
• An Organization or Project to scope it to.
• An Expiry: 30 days, 90 days, or No expiry.

Minting a token: Ask mode is the default; Act only unlocks with a project scope where you're a maintainer.

The token’s plaintext is shown once, with a clear warning: “Copy this now — you will not see it again.” So save it somewhere safe immediately; Aquilla can’t show it to you again.

Each token’s row lists its prefix, mode badge, scope, expiry, and when it was last used, plus a Revoke action. Revoking is immediate and irreversible: a revoked token stays revoked. Replace it with a new one instead.

Who can create which kind of token

Scoping a token to an organization or project needs Contributor access or above there. Act mode additionally needs a project scope and Maintainer access or above on it: that’s the mode that skips human review, so Aquilla requires more trust before it’s available.

Ask-mode tokens work exactly as described above: writes from that agent land on this same approval page (/approve/:id) for a human to approve or reject. Aquilla’s in-app assistant works differently: it acts under your own session and role rather than a token. See Using the AI agent.