Agents: an overview

How your intern's agent works for you through us, with a token limited to what you tick, rehearsal before live, your approval on what leaves, and a record of everything.

The agent your intern builds can work on your accounts, such as drafting replies in your Gmail. It never gets your password. It works through us, with a token that can do only what you tick, and every request is recorded. Open "Agents" in the dashboard menu; the page is called "Your intern's agent".

The pieces

  1. A connected account. You connect Gmail and Google Calendar, a copy-and-paste inbox, or a web address of yours. See Connecting accounts.
  2. A token. You issue it for your intern's agent and tick what it may do. See Tokens for your intern's agent.
  3. Your approval. Requests that need it wait for you. See Approvals and standing permissions.
  4. Rules. Who it may write to, which links it may use, and how often. See Allow-lists and limits.
  5. Stop switches. "Pause all", per-agent pause and "Something went wrong". See Pause all and reporting a problem.
  6. The record. Everything the agent asked for. See Agent activity, the export and the daily digest.

Rehearsal and live

Each intern's agent has a card on the Agents page with its stage.

  • Rehearsal: "Every draft and every message waits for your approval." Every agent starts here.
  • Live: "Drafts go through on their own. Every message that would leave waits for approval, unless a standing permission covers it."

Going live

Three things must happen, in this order:

  1. You press "Let it go live" on the agent's card and agree. The card then says when you agreed.
  2. Our team runs the go-live check on the agent and it passes.
  3. Our team moves it to live.

The card shows the check: "Not checked yet", "Checked and ready", "Not yet:" with how many items to fix, or "Needs a fresh check" if the agent went back to rehearsal after it was checked.

"Back to rehearsal" on a live agent puts every draft and message back under your approval at once. Going live again then needs your agreement and a fresh check.

What never changes

  • Anything that touches what you said must never be automated is refused.
  • Posts to your web address always wait for your approval, even when the agent is live.
  • Reading and searching need no approval, but only if you ticked them on the token.
  • Your intern never sees your passwords or the access Google gives us.

Before an intern is matched

The Agents page says "Tokens and the rehearsal switch appear here once an intern is matched to one of your projects." You can connect accounts before that.

  • Connecting accounts

    Connect Gmail and Google Calendar, a copy-and-paste inbox with no password at all, or a web address of yours, then send a test to see how approvals work.

  • Tokens for your intern's agent

    Issue a token that lets your intern's agent do only what you tick, send it privately, and revoke it at once if it leaks.

  • Approvals and standing permissions

    Review each held request and approve or decline it, approve all or some items of a batch request, and give a standing permission so one kind of request runs without asking, up to a daily number, until a date.

Was this helpful?

Edit suggestions

Spotted something wrong, out of date or missing? Tell us which guide and what you expected to see.

Email hello@aiharnesslabs.com