Loading the documentation…
A mode is an agent preset: the instructions Oda follows, the capabilities and skills it may use, and the model it starts on. Agent modes introduces the modes that come with DataMind Oda. This page shows how to build one of your own in Settings > Agent presets, and how to change or remove it later. To choose a mode for a task instead, see Choose a mode for a new task.
<name> copy and keeps the source preset's description.The new preset copies the model, capabilities and instructions of this preset. A copy also keeps the source preset's skills choice.Presets that come with DataMind Oda, and presets installed for you, are read-only: their cards carry no Edit or Delete, and a change to one is refused with Built-in and installed presets cannot be changed. Duplicate it and edit your copy; the presets you make sit under Custom.
To build a preset by conversation instead, choose Let the agent help me create a preset in the Custom group: it starts a task in Creator mode where you describe the preset and Oda creates it. While mode selection for new tasks is off, the row is disabled and explains: Turn on mode selection for new tasks to start Creator mode.
{{model}}, {{cwd}} (the folder the chat works in) and {{provider}}; Oda fills them in for each chat.This preset has no capabilities that can be switched. The rows are labelled: Project instructions (AGENTS.md), Terminal commands, Read and edit files, Search files, Background jobs, Skills from folders, Use skills, The /goal command, Goals, Plan mode, Long conversation compaction, Subagents and workflows, Ask you questions, To-do list, Web search and pages, Inspect the app configuration, Show files to you, Programmatic tool calling, Install and manage plugins.The switches turn the preset's own parts on and off; the editor does not build a new capability into a preset. To give a preset a part it does not carry, the preset itself is built that way (Preset compositions).
If the preset, the model list or the skill list cannot be read, the editor says so with the reason, for example Could not read the models: <reason>.
Skills sets which skills Oda may use under the preset, including the ones you start yourself with /:
All skills: every skill is available, and new skills appear automatically.
Only selected: the skills you tick are available; a skill added later stays out until you add it.
All except selected: the skills you tick are hidden; everything else stays available, including skills added later.
The search box filters the list, and the field shows how many are selected, for example 3 selected. An empty list reads No skills are installed yet. or No skills match your search.
Skill names are lowercase letters, digits and hyphens, for example review-checklist.
A skill that is no longer installed stays listed as Not installed and stays selected.
A skill your organisation requires shows a padlock and Required by your organization. Its box cannot be changed and does not count as selected, because every preset keeps it.
While Use skills is off, the section is locked, and the hint names the switch to turn on: Turn on “Use skills” to choose skills. A preset with no skills settings gets them when you switch Use skills on.
Leave the section alone and the preset, or your copy, keeps its own choice. Skills in chat covers how Oda picks and runs skills.
The saved model <model> is no longer available, so this agent uses the default model., the list shows it as <model> (not available), and the card reads Model <model> is no longer available, so this preset uses the default model.The editor checks the form first and shows what to fix:
Enter a name. when the name is empty.Use at most 64 characters for the name. when the name is over 64 characters.Use at most 500 characters for the description. when the description is over 500 characters.The instructions are too long. when the instructions pass 32,768 characters.Double braces can only insert {{model}}, {{cwd}} or {{provider}}. when the instructions contain another double-brace word.The skill selection is not valid. when the skills choice cannot be saved.Choose a model from the list or use the default model. when the model choice cannot be saved.If the app itself refuses the change, the editor stays open with Could not change the preset: <reason>. The reason can be, for example:
Built-in and installed presets cannot be changed.This application cannot save presets. on an installation that cannot write presets.The default model must name a provider and a model. or The model "<name>" is not available.The preset has no switchable row "<capability>". when a switch is requested for a part the preset does not offer.The preset has no skill selection a form can change. when the preset sets its skills in a way the editor cannot rewrite; the skills choice then does not appear in the editor.New tasks use the saved version; tasks already running keep the version they started with. A new chat that is still blank picks the change up, and the helpers a running chat starts join the version that chat began with.<name>; any field can change, including the Name. The id under the name, made from the name when the preset was created, stays the same.Delete <name>?) that reads New tasks can no longer use this preset, and tasks that use it cannot be resumed after they close. Delete preset removes the preset.Presets that come with DataMind Oda, and presets installed for you, are read-only. A change to one is refused: Built-in and installed presets cannot be changed. Duplicate it, edit the copy and save; your presets live under Custom.
The editor names what to fix, for example Enter a name., The instructions are too long. or Choose a model from the list or use the default model. (What the editor checks before a save). If the app refuses the change itself, the editor stays open with Could not change the preset: <reason>; an installation that cannot write presets says This application cannot save presets.
Your own guidance for chats on this preset: how the work should be done, what to check first, what to avoid. Instructions add to Oda's own guidance and never replace it. You can insert {{model}}, {{cwd}} (the folder the chat works in) and {{provider}}; any other double-brace word is refused when you save, and the instructions can run up to 32,768 characters.
No. The switches turn the preset's own parts on and off; the editor does not build a new part into a preset. A switch for a part the preset does not offer is refused: The preset has no switchable row "<capability>".
Either the preset's Use skills capability is off, which locks the Skills section (Turn on “Use skills” to choose skills.), or the preset sets its skills in a way the editor cannot rewrite, so the choice does not appear at all. A skill your organisation requires is always kept and cannot be unticked.
Only with All skills or All except selected: both keep skills added later available. With Only selected, a skill added later stays out until you add it to the list.
It stays in the list, marked Not installed, and stays selected; the preset saves as usual. Deselect it if you no longer want it.
The preset uses the default model instead, and the editor and the card say so. Pick another model from the list, or go back to Use the default model. A model saved earlier that has since left the list is kept, and the preset still saves unchanged; a newly picked model that is not offered is refused.
No. A chat that has already started keeps the version it began with, and the helpers it starts join that version. Chats that start after the save use the new version, and a new chat that is still blank picks the change up as well. No restart is needed.
Yes. Open it with Edit, change the Name and save. The code under the preset's name is its id, made from the name when the preset was created; renaming does not change it, and you never need to type it.
Deleting the preset you set as your new-task default clears that choice, and new tasks use the application default again. A chat that ran on the deleted preset cannot be resumed after it closes.