Bots, sub agents and agents: one set of words, top to bottom

OpFlow now has four levels, named the same way everywhere a person or a tool reads them: Assistant, then Agent, then Sub agent, then Bot. A bot does the work. A sub agent is one focused job that carries out bots and owns knowledge files. An agent is a part of the business, such as Sales, Billing or Support, that an assistant looks after and that carries sub agents. Your data, run history, URLs and webhook addresses did not change.

What each old word became

• Workflow is now bot. Everything named workflow in the console, the docs and the emails says bot.
• The old agent is now a sub agent.
• The old task is now an agent.
• The hidden layer between a sub agent and its bots is now called a step. It is not shown in the console; a bot attaches straight to a sub agent.

MCP tools: old name, new name

These renames only changed the word; the old names still work, and they are not listed in tools/list.

• list_workflows, get_workflow, get_workflow_health, create_workflow, update_workflow, validate_workflow_graph, run_workflow are now list_bots, get_bot, get_bot_health, create_bot, update_bot, validate_bot_graph, run_bot.
• archive_workflow, restore_workflow, archive_workflow_folder, move_workflow_to_folder, move_workflows_to_folder are now archive_bot, restore_bot, archive_bot_folder, move_bot_to_folder, move_bots_to_folder.
• create_task, rename_task, delete_task, archive_task, restore_task (the step under a sub agent) are now create_step, rename_step, delete_step, archive_step, restore_step. The old names still work.
• attach_workflow_to_task is now attach_bot_to_step. There is also a new attach_bot_to_sub_agent, which attaches a bot straight to a sub agent. The old name still works.
• Folder kinds: workflow is now bot, and agent_file is now sub_agent_file. The old values are still accepted.

MCP tools: the names that changed meaning

Because agent now means the level that task used to be, these old names would give you a different object than before. They are not aliased. For 30 days, until 2026-11-15, they answer with a notice or an explanation instead of acting on the wrong thing.

• What you called list_agents, create_agent, rename_agent, delete_agent, archive_agent and restore_agent for an agent is now list_sub_agents, create_sub_agent, rename_sub_agent, delete_sub_agent, archive_sub_agent and restore_sub_agent.
• move_agent_file_to_folder and move_agent_files_to_folder are now move_sub_agent_file_to_folder and move_sub_agent_files_to_folder. The old names no longer exist and answer with a pointer for 30 days.
• list_agents, create_agent, rename_agent, delete_agent, archive_agent and restore_agent now work on agents (the old tasks). list_agents carries a notice for 30 days. create_agent now needs an assistant_id; called the old way it explains itself and points to create_sub_agent. Giving rename, delete, archive or restore an id that is a sub agent returns that sub agent's tool name.
• New: attach_sub_agent_to_agent and detach_sub_agent_from_agent, and set_assistant_name.

REST API

• /api/v1/workflows is now /api/v1/bots (old addresses still answer, with a Deprecation header).
• POST /api/v1/agents/{id}/run now runs nothing. It answers 410 for 30 days and points to POST /api/v1/sub-agents/{id}/run, which does what the old path did.
• /api/v1/openapi is regenerated with the new names.