Skip to content

Build your first Agent

Create a small support-writing Agent, save its instructions, and try it in Private Preview. You will finish with a saved snapshot and a private test result ready to inspect.

Prerequisites

  • Sign in to an existing Console and select your active Team.
  • Have agent.read, agent.edit and agent.test in that Team. A Team Developer normally has these; see role presets.
  • Have a generation model available in the Team allowance and sufficient developer limits. Preview calls can incur provider charges.

This tutorial uses no tools or personal Connector accounts. Publication is a separate step requiring deployment permissions.

1. Create the Agent

Open Build → Agents → Create Agent. Name it Support writing assistant and add a description such as Draft short replies using only facts in the message. Open its workspace.

2. Save a small definition

In Build, choose your allowed generation model. Leave Tools empty and set Instructions to:

You draft support replies using only facts supplied by the user.
Keep the reply to three sentences or fewer.
If a fact needed to answer is missing, ask one concise question.
Do not claim to have checked an order, account, or external system.

Choose Save snapshot. This records an immutable definition; later edits create another snapshot.

3. Try the saved snapshot

Use Private Preview and send:

Draft a reply to a customer asking when order DEMO-104 will arrive.
We know it shipped on Monday. We do not have a delivery estimate.

Inspect the answer. It should use the supplied facts and acknowledge the missing estimate. Exact wording varies by model; the instruction is not a guarantee of correctness. Refine the instructions and choose Save and test to iterate.

Expected result

The Agent has a saved snapshot and a Preview conversation. Creating or testing it has not published a Production deployment. No service restart or new Console session is needed.

Verification

Confirm the saved snapshot appears in Snapshot history. With Team observability.read, open Activity or Observe → Requests to inspect the attributed work. Reading captured prompt and response content additionally requires observability.content.read and effective content capture.

Failure recovery

Symptom Next step
No Team or model available Select the intended Team and ask an administrator to check membership, the catalog and Team allowance.
Preview is unavailable Check agent.test, current membership and the saved snapshot.
A request is denied or reaches a limit Inspect its safe error/correlation ID and follow request troubleshooting.
The answer invents facts Refine the definition and add that prompt as an evaluation case; a successful HTTP response does not establish answer quality.
Publication is unavailable Request the separate deployment publication/access permissions described in the publishing guide.

Next steps