November 2026

Updates released in November 2026.

Agent delegation is paused

November 1, 2026 — Agents can no longer hand parts of a task to other agents. This feature is paused and will probably be removed.

Until now, an agent could split a large job and pass pieces of it to other agents (sub-agents), then collect their results. This is switched off for all agents and no longer appears among an agent's capabilities. Your agents' settings are kept as they are, and past results from sub-agents remain in your conversation history.

What to do instead:

• Pick the right agent yourself — start the chat with the agent built for the job, for example your own Invoice Helper agent for invoice work, instead of asking a general agent to pass the job on.
• Use skills for specialised work — write the way a task should be done into a skill, such as Month-end supplier invoice check. Operator finds and follows the skill on its own in any conversation, so one agent can cover many specialised tasks. See Instance Skills.

Teach Operator how your company gets things done

November 1, 2026 — Skills let you write down your company's rules so Operator follows them in every conversation

A skill is short guidance written for Operator: what to do, in what order, when a certain kind of task comes up. It is not an SOP for people — it tells the AI how to work. Anyone can write one for themselves; a Process Owner or instance Admin can approve it so the whole instance benefits.

• Write it your way — open Build → Skills, or describe the task in chat and let Operator draft the skill. Each skill holds a name, a When to use line, and the step-by-step Guidance, and is filed under a business area such as Finance or Sales — picked for you, and easy to change.
• Operator finds it on its own — before working on a task, Operator looks for a skill that fits and follows it, unless you tell it otherwise. Only the skills a task actually needs are loaded.
• Teach as you go — tell Operator a rule that should hold from now on and it applies it right away, then offers to save it into the right skill, naming that skill, so it also holds in later chats.
• Personal or shared — a skill starts as yours alone. Send it for approval and, once approved, everyone connected to the instance can rely on it.
• Every change is on record — History shows what changed in each version and who made the change. Restoring an earlier version asks you to confirm first, after showing exactly what would change.
• See it as a chart — the Diagram tab draws the skill as a top-down process chart in the skill's own language, and remembers the style you asked for.

For example, a Finance skill titled Month-end supplier invoice check might say: list the month's unpaid supplier invoices, flag those without a purchase order, and summarise the totals per supplier. The next time you ask "check our supplier invoices for October", Operator works exactly that way.

See Instance Skills under Skills.