Operator

Approvals belong to the person who started the work

A checkpoint goes to whoever started the session. Members without approval rights get a read-only view.

Talha Bera4 Sep 2026 · 1 min read

When an operator session reaches a checkpoint, it asks the person who started it. They see what the agent wants to do and approve it, ask for changes, or discard it.

Read-only for everyone else

Other company members can open the session and follow along. Without approval rights they get a read-only view: the transcript and the checkpoint, but no buttons.

Keep reading

Operator28 Aug 2026

Versioning operators without breaking live runs

Edit a draft while v1 keeps running. Publish when it is ready; running sessions finish on the version they started.

Operator20 Dec 2025

Named HTTP endpoints on an operator agent

The model fills arguments. URLs and header secrets stay on the server.

Lead engine24 Sep 2026

How one agency runs a lead engine for every client

Acme GmbH set a target of 10 qualified leads a week. Lead Gatherer found 146, Lead Qualifier kept 44, Mail Marketer contacted 31 and 9 replied. Here is how the agency runs it, and where it stops for approval.

Give every client a lead engine.

Relay is invite-only while we onboard agencies. Tell us about your clients and we set up the first workflow with you.