Skip to main content
An Agent Operating Procedure (AOP) holds reusable instructions, inputs, and an agent configuration. Start with a task you repeat, such as drafting a weekly report from selected files.

​
Create and test an AOP

How to create an AOP, test it, and run it on a schedule

  1. Open Spaces. In the asset creation menu, choose AOP.
  2. Enter a name and select Create AOP.
  3. Describe the task, source material, output, and review requirements in the prompt. Configure the agent and tools it needs.
  4. Add inputs for values that change between runs. For example, [[topic|type=text]] asks for a topic each time.
  5. Select Run, fill in the inputs, and inspect the resulting session and assets. Revise the instructions until the test produces the result you need.

​
Example: a weekly project update

Paste this into the prompt of a new AOP. The two placeholders become the run form.
A run with Project set to Northwind freight exceptions and three status notes selected produces a document like this:
Northwind freight exceptions: weekly update, Oct 13
  • 14 of 19 open exceptions closed; 5 remain (Exceptions tracker, Summary tab).
  • Summit Haulage credit of $2,340 approved (Finance note, Oct 10).
Blockers: Lakeside Foods dispute waits on proof of delivery (owner: Sam, raised Oct 8). Missing: no update on the Riverside depot audit in the selected files.
To try the same task once as a chat before you build the AOP:

​
Choose how it starts

Open Triggers and select Create. Choose the trigger for your task:
  • Schedule: use Recurring for repeated runs or One-Time Run for a single run. Check the time and timezone.
  • Email: choose Dedicated Address to receive messages at an AOP address, or Connected Inbox to respond to email in your connected account.
  • Meeting or Video Session: start after the session ends and its transcript is available.
Other connected services may offer additional triggers. See Pick the right trigger.

​
Review runs

Inspect the output before using or sending it. Check citations, calculations, recipients, and any actions taken in connected services. A retry starts a new execution, so check for completed external actions before retrying. See AOPs for input types, versions, and execution options.