Skip to main content
The Settings section of the agent’s configuration panel (the gear icon on the detail page) covers the administrative operations you need for day-to-day use.

​
Changing settings

  • You can change the name, description, model, and system prompt
  • Renaming to a name an existing agent already uses is rejected (case-insensitive). The name, description, and system prompt are capped at 120 / 2,000 / 50,000 characters, with a live counter under each field
  • If a save fails, the message names the cause — a field over its limit, a duplicate or missing name, an archived agent, a model that is no longer offered, or a connection problem — so you know what to fix before trying again
  • “Auto-generate” regenerates the description and system prompt from the current inputs, written in the app’s display language rather than the language the agent’s name happens to be in
  • The creator and last-updated timestamp are shown in the “Info” section
Model changes apply to new chats only. Existing chats keep running on the model they were created with, so chats within the same agent can end up on different models, with noticeable differences in response style.

​
Changing settings from chat

While chatting with an agent, you can also ask it to change its own settings — “make your tone more formal,” “switch your model to Haiku.” The AI shows a “Settings change proposed” card with the changes (including a system prompt diff) and applies them only when you press “Apply changes.” Changes apply from the next chat. Sharing changes can be proposed from chat too — see Share an agent. Lifecycle operations — deleting or archiving the agent — and erasing its memory are deliberately not available from chat: if you ask, the AI directs you to the agent’s settings screen or Memory section instead. See In-Chat Forms and Suggestions for the full list of cards.

​
Version history

Changes to settings such as the system prompt are recorded as version history.
  • Open “Version history” in the Settings section to list past versions
  • You can view the diff of the system prompt for each version
  • Use “Restore” to roll back to a previous version

​
Duplicating

“Duplicate” builds a new agent from an existing one. It sits in the ”…” menu on each card or row in the agent catalog, and in the “Duplicate agent” card of the Settings section.
  • Anyone who can see the agent can duplicate it — including an agent shared with you and an agent opened from another workspace because it is shared org-wide. Archived agents cannot be duplicated
  • The copy is created in your workspace as your private agent; the original’s sharing settings are not carried over
  • The name defaults to “<original> (copy)” and can be edited in the dialog before you confirm. Duplicating your own private agent skips the dialog and copies straight away
  • Workspace-shared skills, knowledge, and connectors stay linked to the shared originals, so the copy keeps receiving their updates. Resources that belong to the agent alone are copied as they are at that moment and stop tracking the original
  • Duplicating an org-shared agent from another workspace copies the attached skills and knowledge — the workspace-shared ones included — into your workspace as material of your own, so nothing stays in sync. Custom MCP connections are not carried over in this case; set them up again on the copy
  • Memory and chat history are not carried over. Jinba Flow connections are copied, but using them still requires your own Jinba Flow access, and the agent’s own MCP server settings, which hold credentials, are not carried over (the dialog says so when it applies)
Once the copy is created you land on its detail page.

​
Archiving

Archive agents you are not using for the time being.
  • Archived agents cannot be selected for new chats, but past chats remain viewable
  • Settings and sharing cannot be changed while archived (the sharing scope stays visible as read-only): the fields and buttons of the Settings section are disabled, and hovering one explains why — “Archived Agents cannot be edited. Unarchive it first.” Unarchive first if you need to make changes

​
Deletion

Delete an agent from “Danger zone” in the Settings section. Deletion happens only on this screen — it cannot be performed from chat.
Deletion also removes the version history and audit log, and cannot be undone. Associated chats are not deleted — they are unlinked and remain in your history as standalone chats. A scheduled task that runs on the agent is disabled the next time it tries to run (Tasks). Workspace-shared skills, connectors, and knowledge that were attached to the agent are only unlinked and stay in the workspace; agent-only ones (“This agent only” skills, agent-only connections, agent-only knowledge) are deleted together with the agent and cannot be restored.