Skip to main content
Start with the task the agent should handle. Work through the settings that support that task, then review the complete version rather than publishing isolated field changes without their context.

​
Choose a guide

​
Review a saved configuration

Use the API quickstart for a complete creation example. Use versions and drafts to select a branch, inspect the diff, and read the published configuration back. Dashboard controls marked as previews do not establish saved configuration. Use the supported persisted controls or the corresponding API fields, and confirm the saved values after a change.

​
Frequently asked questions

Define one task, then configure the prompt and first message. Add models and permitted resource references after the task is clear.
No. Configuration publication and runtime execution are separate. Review deployment preparation and current availability.
A prompt can rely on a voice, language policy, knowledge attachment, or tool. Reviewing these together catches mismatches that a single-field check misses.