Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Basic Details

Basic Details is the agent's identity card. It carries the information that travels with the agent everywhere it appears: a name, a short description, the format its responses are written in, and its conversation starters. These settings are what users (and other systems) see; they are the agent's outside.

Reach this page by clicking Agent Config in the canvas header. Basic Details is the first item under Agent Setup in the left navigation, and the default section when the dialog opens. The page reads "Define your agent's identity - name, purpose, and how it should respond."

The fields

The right pane has two sections, Identity and Response, and a Conversation Starters list.

Identity

Name (required). The agent's display name. This is what appears in the header strip, in the agent-name selector menu, and on the agent-list dashboard. Renaming here is the same action as renaming through the agent-name menu in the header.

Description (required). A short prose description of what the agent does. It is used in listings of agents and in tooltips. Keep it action-oriented, saying what the agent does for users, not how it is built.

Response

Output Format (required). A dropdown that sets how the agent's text responses are rendered:

  • Markdown (default): the agent's output is treated as Markdown. Headings, bullets, code blocks, bold, and links render with formatting.

  • Json: the agent's output is treated as a JSON payload. The host application is responsible for parsing it.

Choose Markdown for any agent whose output is read by humans in chat. Choose Json when the agent's output is consumed by another system that needs a structured payload.

Conversation Starters

A list of suggested first messages for the agent, such as Ask about a policy or Troubleshoot a common problem. They appear as buttons in an empty conversation, and selecting one fills the message box without sending it.

Select Manage to change the list. The Conversation Starters window reads "Help users start a conversation with your agent." and holds one text box for each starter:

  • Edit a starter by typing in its box.

  • Select the bin icon beside a starter to delete it.

  • Select Add Starter to add a box. It is unavailable while the list holds four starters.

  • Select Regenerate Suggestions to have the platform suggest a new set of starters.

  • Select Save to keep your changes. It stays unavailable until you change something. Select Cancel to close the window without saving.

Fields and obligation

Field
Obligation
Notes

Name

Mandatory

Recommended. Auto-generated.

Description

Mandatory

Recommended. Auto-generated.

Output Format

Mandatory

Markdown (default) or Json.

Conversation Starters

Optional

Select Manage to change the list.

Saving

The Save button sits in the top-right of the right pane. It activates when you've made unsaved changes. Clicking it commits the changes to the current draft of the agent.

Saved changes here do not automatically create a version snapshot. They're saved to the draft. To preserve the current state as a recoverable version, click Draft Version in the header strip after saving.

Why this matters

These fields are the agent's public face. The name is how every other surface (the dashboard, the chat, the Layout canvas, any embed of this agent in another application) refers to this agent. The description shapes how teammates decide whether this agent is the right one to invoke for a new use case. The output format quietly decides whether your agent fits cleanly into the host application. The conversation starters decide what a first-time user is invited to ask.

Last updated

Was this helpful?