September 2026

Bring your own connected services to any agent

September 28, 2026 — You can now add personal MCP servers for tools only you use, and organizational MCP servers are available again for whole teams

MCP servers connect Operator's agents to services such as Slack, Notion, Business Central, and tools built by your company. Organizational MCP servers were temporarily unavailable while their security model was strengthened; they now work again.

• Your own servers — anyone can add a personal MCP server from Capabilities → My servers, without needing an ERP.net instance or a special role. It stays private to you and can be used in any of your conversations.
• Shared across an organization — Power Users and Instance Admins can add an organizational MCP server once and make its tools available to everyone connected to that ERP.net instance.
• Sign in as yourself — when a service supports personal sign-in, each user connects their own account. The agent can offer a Connect button directly in the conversation when access is needed.
• Choose exactly what the AI may use — test the connection to see the server's tools, allow only the ones you want, and decide whether Operator should ask before each use.
• Clearer problems — if a connected MCP server fails, Operator names it when possible and points you to Capabilities to test or disable it.

For example, connect your personal Slack account to ask an agent to post a weekly summary, or add an organizational Business Central server so your team can compare its open purchase orders with ERP.net. See Connected services (MCP servers).

Apps can now connect securely on your behalf

September 27, 2026 — A Pro app can now log in to other services and call them safely — the part that must never happen in your browser

Many things an app might want to do are not safe to do from the browser: signing in to a service that needs a non-standard login flow, calling an API with a private key, talking to a system that only accepts connections from a server. A Pro app can now run procedures — small jobs the App Builder writes for it, which run on Operator's servers instead of in your browser.

• Just describe what the app should be able to do — "Add a button that fetches today's currency rates from our provider's API." The App Builder writes the procedure; you press the button.
• Credentials stay on the server — keys and secrets used by a procedure never reach your browser, so nothing sensitive is exposed by simply opening the app.
• Handles tricky logins for you — services that need custom sign-in flows, signed requests, or server-only endpoints are no longer off-limits for an app.
• Runs to completion, even if you leave — the job runs on the server; closing the app while it works changes nothing.
• Every run is on record — each procedure keeps its own history in the app's Cloud tab, so you can see when it ran, whether it succeeded, and what it reported.

How this differs from Web Requests. Web Requests already let an app make a single call to another service with a standard sign-in — a stored key or a regular company login — and they are included in the daily Cloud cost. Procedures go further: they can run any secure logic the browser must not, such as custom logins, signed or chained calls, and keeping a session open. Because of that, each procedure run costs a little (0.1 credit, once billing starts after BETA). Start with a Web Request; the App Builder switches to a procedure only when one call is not enough.

Procedures need a Pro app and are set up by the App Builder in Design mode — just say what the app should be able to do. See Procedures under Apps.

Explore the new Examples Gallery

September 26, 2026 — A gallery of working example apps and agents shows what you can build with Operator — and every example opens live

Wondering what an AI-built app looks like? The Examples Gallery is a collection of ready-made apps — an online shop, a door configurator, a service dispatch board, a machine configurator, a purchase invoice workflow, an email campaign studio, and more — each one openable in a single click.

• See it before you build it — every example is a real, working app you can click through, not a description of one.
• More than apps — the gallery also shows example agents, so you can see how both sides of Operator work in practice.
• Open in one click — each card links straight to the live demo, on the gallery's public address or from inside Operator.
• Demo data, real potential — the demos run on sample data and are not connected to a real ERP instance. With Operator, the same apps connect directly to your ERP.net data — or, with a small setup, to any other ERP.

Inside Operator, the gallery is always at hand: open your profile menu, hover Build, and choose View Examples Gallery. Or visit it without signing in at operator.net/examples.

Apps can now work on their own with triggers

September 23, 2026 — An app no longer waits for somebody to open it — a trigger lets it act on a schedule or when something happens

A trigger is a small script the App Builder writes and keeps with your app. It runs on the server exactly as written — every morning at eight, when an email arrives, when a webhook is called — and costs no AI credits. Just say in plain words what should happen and when.

• Runs while nobody is watching — "Every weekday at 07:30, refresh the open-orders table from ERP.net" and the app shows fresh data the next time you open it.
• Reacts to events — incoming emails, webhook calls, and record changes can all wake up your app, using the same events that already drive agents and automations.
• PDF reports by email — "Every Monday, email last week's sales by customer as a PDF to the sales team." A copy of each report is kept in the app's files.
• Tied to your data — a trigger can be bound to a specific ERP.net instance, so it reads and writes exactly that instance's data even when nobody is connected.
• Easy to adjust — "Move the daily snapshot to 07:30" changes only the time; the script and everything else stay untouched.
• Watch them run — the Triggers tab in the App Builder shows each trigger's next run, its history, and anything that went wrong.

Triggers need a Pro app and are set up by the App Builder in Design mode — just describe what should happen. See React to schedules and events under Apps.

Agents can now draw diagrams in their answers

September 22, 2026 — When an answer describes a process or a flow, agents can now show it as a diagram right in the conversation

Besides charts and dashboards, agents can now include diagrams — process steps, workflows, relationships, or timelines drawn as connected boxes and arrows. A path that took a paragraph to describe becomes something you can follow at a glance.

• Diagrams when they help — the agent adds one when the answer naturally describes a process, flow, states, or dependencies; simple answers stay text-only.
• Interactive — zoom and drag to explore, open full screen, or download as an image.
• Controls never get in the way — zoom and download options sit in their own slim row above the diagram and appear only when you hover, so nothing is covered.
• Readable at first glance — diagrams are drawn to fit the conversation area, so long processes flow top-to-bottom instead of shrinking into tiny text.
• Plays well with dashboards — one answer can contain both a diagram for the structure and a dashboard for the numbers.

For example, ask "How does a sales order move from creation to invoicing?" and the answer can show the whole path as a diagram, with the explanation below it. See Visuals in answers under Chat.

Queue your next message while the agent is working

September 15, 2026 — You no longer have to wait for an answer to finish before sending the next one — just add it to the queue

When an agent is still working and you already know what you want to ask next, you can queue your message instead of stopping the current answer. It runs automatically the moment the agent finishes — in any conversation, including the App Builder and the Agent Builder.

• One press to queue — while an answer is running, sending a message (or the clock button next to Stop) adds it to the queue instead of interrupting.
• Queued messages survive closing the tab — they are kept safely, so whatever you queued still runs when you come back.
• Edit or remove before they run — queued messages appear as small cards above the message box; change the text or drop them entirely while there is still time.
• Stop holds the queue — stopping the agent also pauses everything queued; Resume (or simply sending a new message) continues it.

For example, in the App Builder you can queue "Now make the header dark" while the first change is still being built — it will run right after.

Agents can now answer with dashboards

September 14, 2026 — Business Specialist and the other text agents can now show their answers as charts, KPI cards, and tables, right inside the conversation

When you ask a text agent a numbers question — turnover by month, top customers, stock levels — the answer can now arrive as a visual dashboard instead of only text. You get an at-a-glance summary you can read in seconds, without leaving the chat.

• KPI cards — headline figures like total revenue or open orders, each with its value and unit.
• Bar, line, and doughnut charts — trends, comparisons, and breakdowns drawn directly in the answer, with legends and labels.
• Tables — the underlying rows when you need the exact numbers behind a chart.
• Real data only — agents build dashboards exclusively from data they have actually retrieved; they never invent figures, and each value names its unit or currency.
• Matches your theme — dashboards follow your light or dark theme automatically.

Just ask for the numbers as usual — for example, "Show me turnover by month for this year as a chart." The agent decides when a dashboard adds clarity and includes one in its reply.

Operator is now integrated inside the ERP.net Web Client

September 14, 2026 — You can open Operator as a side panel directly from entity forms in the ERP.net Web Client

Instance admins can register Operator as an extension panel inside the ERP.net Web Client. Once registered, a new Operator panel appears on entity forms, so users can ask questions about the current record without switching tabs or copying context.

• Context travels automatically — the panel receives the current entity type and record ID, so agents like Business Specialist already know which record you are looking at.
• Works on any entity form — register it once and it appears across all entity forms in the instance.
• Managed under Instance settings — go to Manage instance → Web Client Integration to add, update, or remove the panel.
• Requires ERP.net Web Client v.27 — the extension-panel feature is available starting with ERP.net version 27.

Agents can now send you notifications

September 13, 2026 — Agents can reach out on their own — to you, and to anyone on the platform who allows it

Agents with the new Notifications capability can now send Operator notifications proactively, instead of only replying in a conversation. This is especially useful for always-ON agents like Digital Entities, which can now deliver reminders and alerts even while you are away.

• Notify the owner directly — an agent can always message the person who created it, for example to report that a nightly import finished or to deliver a scheduled reminder.
• Notify anyone on the platform — agents can look people up by name or email and send them a notification too, but the first message arrives as a permission request; only after the recipient taps Allow do further notifications come through.
• You are in control — recipients can allow or block notifications from each agent, and every notification shows which agent sent it.
• Sensible limits — each agent can send up to 20 notifications per recipient per day, so nobody gets flooded.

To enable it, turn on the Notifications capability for an agent in its settings.

Operator now sends device notifications

September 12, 2026 — Operator can now push notifications straight to your phone, tablet, or desktop

You no longer need to keep Operator open in a browser tab to stay on top of important alerts. Once you enable device notifications, new notifications from the platform are delivered to your installed Operator app or browser in real time.

• Install Operator as a PWA — add it to your home screen or desktop for the best experience and reliable delivery.
• Notifications turn on automatically with install — once you install Operator as a PWA, device notifications are enabled right away on that device, so you do not have to remember to turn them on later.
• Enable notifications from the user menu — open your profile menu, choose Device notifications on this device, and turn them on.
• Works across devices — each device you enable is registered separately, so you can receive notifications on your phone, your laptop, or both.
• Notifications drop-down helps you opt in — if device notifications are not enabled on the current device, a banner at the top of the notifications panel explains how to turn them on.
• Automatic cleanup — stale or expired device registrations are removed, so you do not receive duplicate or broken deliveries.

Device notifications are delivered for any notification you would normally see inside Operator, including broadcasts sent from the admin panel.

App Builder reasoning levels

September 11, 2026 — You can now choose how deeply the App Builder thinks when building apps

The App Builder now supports five reasoning levels, so you can trade speed against depth depending on the task. Pick the level from the reasoning badge in the chat header before you send a message:

• Quick — fastest responses for small edits and straightforward tweaks.
• Smart — balanced thinking for everyday changes and UI work.
• Expert — deeper reasoning for multi-file features and app structure; this remains the default.
• Genius — maximum analysis for complex refactors, performance work, or tricky bugs.
• Savant — the deepest thinking available, reserved for the hardest builds; the slowest and most credit-intensive option.

Higher levels use more capable models and more AI credits, so Quick is ideal when you only need a fast adjustment, while Savant is there when even Genius is not enough. The App Builder keeps working the same way no matter which level you choose.

App Builder now catches frozen previews automatically

September 7, 2026 — If an app preview stops responding in the App Builder, the editor notices and offers recovery options before the browser does

The App Builder now watches the live preview while it runs and detects when it becomes unresponsive. Instead of the whole tab locking up, you see a clear “Preview stopped responding” message with four choices:

• Wait — hide the notice and give the app a little more time; it keeps running in the background and may recover on its own.
• Restart preview — reload the app from scratch if waiting did not help.
• Turn Safe Mode on — disable the preview entirely so you can edit the code and chat with the Builder without the frozen app getting in the way.
• Ask the Builder to fix it — send the App Builder agent the freeze time and recent console output, so it knows exactly what went wrong and can suggest a fix.

The editor stays usable the whole time: you can still switch tabs, edit files, and continue the conversation while the notice is shown. Once a preview has frozen, the Builder will not embed it directly in the editor page again, so a runaway app cannot freeze the whole workspace.

App Builder pages and public apps

September 6, 2026 — Pro apps can now have multiple pages, including public pages that anyone can visit without signing in

Apps built with the App Builder are no longer limited to a single screen. You can now add extra pages, each with its own address and access mode, so the same app can host both internal ERP tools and public-facing content. This makes it practical to build anonymous-access websites such as landing pages, product catalogs, or registration forms directly inside Operator.

• Each page gets its own path — for example /pricing, /docs, or /register. Sub-pages are organized as nested paths.
• Public pages need no login — visitors can open and share the address without an Operator account or an ERP.net connection.
• Internal pages stay protected — pages that require an Operator user or an ERP.net internal user still ask for sign-in, so one app can mix public and private content safely.
• The Home page sets the default — you choose whether the app opens publicly or internally by default, and new pages inherit that choice unless you change it.
• Public pages use safe backend requests only — they can call backend web requests that you explicitly mark as public, but they cannot reach ERP.net data, app tables, files, or secrets directly.

To add a page, open an app in the App Builder and go to Backend → Pages. Public pages require a Pro app.

App Builder now runs big jobs as a step-by-step work plan

September 4, 2026 — Large app changes no longer restart from scratch when a build spans several turns

When you ask the App Builder for something substantial — a multi-file refactor, a performance analysis, or a complex new feature — it now breaks the work into an ordered plan and works through it one step at a time. You see the plan right inside the conversation as a compact Work plan strip.

• Progress you can read at a glance — the strip shows how many steps are done and which one is active, so you know exactly where the build stands.
• Each step finishes before the next begins — the Builder completes one focused piece of work, records what it found, and only then moves on.
• Pauses resume where they left off — if a long build is interrupted or needs a Continue, the next turn picks up the pending step instead of rediscovering everything from the start.
• Less wasted context — findings from completed steps are carried forward, so the same question does not get answered again and again.
• Big jobs become steadier — refactors, optimizations and large new screens are less likely to drift or lose momentum halfway through.

The work plan appears automatically whenever the App Builder decides a request is large enough to benefit from it. You do not need to manage the steps yourself; just describe what you want and watch the plan update as the Builder works through it.