Skip to content

Agent Editor

Agent Editor is where operators do the real day-to-day work on an agent. You do not need to master every control at once. For most improvements, you will repeat the same loop inside one screen: update the agent, test the change, save a version, and move on.

Consultation Desk editor

Why this screenshot already looks active

The example agent is already live, so you can see the full working state in one image. A brand-new agent starts with the same fields, but Live Test becomes useful after you add the first working version.

The operator loop inside the editor

For Consultation Desk, the usual sequence is:

  1. Define the agent's role, outcomes, and boundaries on the left.
  2. Use Copilot when the instructions are still vague or incomplete.
  3. Try the exact behavior in Live Test.
  4. Click Apply to save a new working version.
  5. Publish the version only after the behavior is good enough for real users.

What matters most on day one

You can ignore many settings at first. Start with these:

  • Name: what your team calls the agent
  • Description: one sentence describing the job it does
  • Instructions: the operating rules that matter most
  • Live Test: the fastest way to see whether the current version behaves correctly

For the Consultation Desk example, the minimum useful version is simple:

  • ask clarifying questions before recommending anything
  • choose only one allowed next step
  • avoid invented prices, services, or guarantees
  • hand off when the situation is risky or unclear

Use the editor like an operator, not a form filler

When you open the editor, do not try to perfect every field before testing. A better pattern is:

  1. Write or generate a first instruction draft.
  2. Test one realistic prompt in Live Test.
  3. Fix the specific failure you just saw.
  4. Save that improvement with Apply.

This keeps the work tied to observed behavior instead of abstract preferences.

Where Copilot fits

Copilot is useful earlier than many operators expect. Use it to:

  • clarify the outcome when the request is still vague
  • ask follow-up questions about decision points, boundaries, and handoff rules
  • suggest what should live in Instructions, Knowledge Base, or Web Search
  • draft the first version of the instructions and recommend tools only when the task actually needs them

The instruction workflow is covered in Instructions.

Where Live Test fits

The right side of the screen is not just a demo panel. It is the fastest quality check you have before a stakeholder sees the change.

Use Live Test to confirm that the agent:

  • asks the right follow-up questions
  • stays within the allowed outcomes
  • explains the recommendation clearly
  • stops and hands off when it should

If the test fails, go back to the left side, adjust the agent, and test again immediately.

Apply and Publish are not the same

  • Apply saves a new working version of the agent.
  • Publish moves a version to the public experience used by channels.

That split matters. Operators should save often with Apply, then publish only the version they are willing to stand behind.

The details are covered in Version Management and the beginner publishing flow in Share for Feedback.

What to leave for later

Once the core behavior works, you can decide whether the agent also needs:

  • Tool Configuration for connected data or actions
  • Attachments for small always-on reference files
  • suggested questions for a cleaner starting experience

Next Steps