May 2026

Updates released in May 2026.

Duplicate Apps

May 30, 2026 — App Builder: duplicate any app you can clone

You can now make your own copy of an app from a single dialog, with sensible defaults that keep your apps list tidy.

• Duplicate from two places — the actions menu (⋯) on each card on the /apps page, and a new Duplicate button in the Duplicate App section of an app's Properties tab.
• Name and slug you can edit — a confirmation dialog opens with both fields pre-filled. The defaults append today's date (e.g. "My App (2026-05-30)" and "my-app-2026-05-30"), and add a numeric suffix if a collision is detected (… (2), …-2, and so on).
• No stacked dates — if the source app already ends with a date suffix, that date is replaced rather than appended again.
• Clean copy — files, description, categories, form factor and safe-mode flag are copied; sharing, Web Client integrations, conversations, statistics and deployments are not. You land straight in Design mode for the new app.
• Permission required — works on apps you own or that have been shared with you at Clone level or higher.

See Managing Apps under Build Apps in the help.

Reference Other Apps

May 30, 2026 — App Builder: reference another app to copy code across

The App Builder agent can now look at the files of another app you have access to, and adapt them into the app you are building.

• Type @ in the chat — a popover lists the apps you can reference (anything shared with you at Clone level or higher, excluding the current app). Pick one and the editor inserts an @app:<slug> mention.
• Read-only on the source — the agent can list and read the referenced app's files, but never write to it. Anything it copies is written into the current app, the same as any other build step.
• Just describe what you want — "adapt the dashboard layout from @app:sales-overview into this app" is enough; the agent will fetch the relevant files and bring them over.

See AI in Apps under Build Apps in the help.

Device Form Factors

May 22, 2026 — App Builder: design for phone, tablet, desktop, or wide screen

You can now tell the App Builder which device shape your app is meant for, and the preview resizes to match — similar to the device mode in a browser's developer tools.

• Display form — a new property on every app with four choices: Phone, Tablet, Desktop, and Wide screen, each labelled with its target pixel size.
• Preview matches the choice — the preview area centres your app on a stage of the chosen size, with scrolling when it doesn't fit, so you see exactly how it will look on that device.
• Just ask the agent — saying "make me a mobile app" or "design this for tablet" is enough; the App Builder switches the display form for you.
• Saved per app — the choice sticks across sessions. The standalone, deployed app still uses the real device viewport of whoever opens it.

See Managing Apps under Build Apps in the help for the full list of properties.

Bearer Token Auth

May 22, 2026 — MCP Servers: connect using a Bearer token

You can now add an MCP server that needs a personal API key (such as Render's https://mcp.render.com/mcp) directly from the Capabilities page.

• New authentication option — the Authentication field offers a third choice, Bearer token, alongside No authentication and Send user's instance token.
• Paste once, use everywhere — drop the key into the new Bearer token field; every call to that MCP server is sent with the token automatically.
• Stored securely — the token is kept with the rest of the server's configuration and is never shown back in plain text after saving.

See Organizational Capabilities under Build Agents in the help.

Safe Mode

May 20, 2026 — App Builder: Safe Mode for recovering frozen apps

A custom app whose preview hangs or loops can now be opened without running its preview, so you can fix it instead of losing it.

• The Apps page actions now live in a single overflow menu, with two new entries:
  • Open in Safe Mode — a one-time rescue for the current tab. The next normal open runs the preview again.
  • Switch to Safe Mode — keeps the app in Safe Mode permanently, until you turn it off.
• In Safe Mode, the preview area shows a clear placeholder telling you whether it is one-time or permanent. The Code tab and chat keep working, so you can edit files or ask the agent to revert.
• A matching switch in Properties controls the permanent mode and shows a notice when a one-time session is the reason the preview is hidden.
• Apps that are permanently in Safe Mode get a Safe Mode badge in the apps list.

See Safe Mode under Build Apps in the help for the full walkthrough.

Delegation Polish

May 19, 2026 — Agent Delegation: clearer waiting state and more reliable finishes

Follow-up polish for the Agent Delegation feature shipped on May 18.

• A clear "Waiting for sub-agents…" indicator now shows for the whole time the main conversation is waiting on its helpers, with a spinner on each one — so it no longer looks stuck while they are still working in the background.
• The "this execution looks stuck" warning is hidden while any helper is still running, removing a false alarm that could appear during a resume.
• Helpers that run in the background no longer get incorrectly reported as failed when they actually completed successfully — the main conversation now consistently sees the real result and summary.

Agent Delegation

May 18, 2026 — Agents can now split work across helpers

Agents can now hand parts of a job to other agents you have created — or to copies of themselves — and bring back the combined results.

• Off by default. Turn it on per agent from the Capabilities page. Available on a few of the more advanced built-in agents that typically coordinate larger pieces of work.
• Big jobs fit. Each piece runs in its own conversation, so long or context-heavy work no longer has to squeeze into a single run. If helpers are still busy when the main agent checks in, it simply waits and tries again.
• Live status. The main conversation shows a card per helper — running, waiting for confirmation, completed, failed — that you can expand to read its full transcript.
• Stays in your control. Anything sensitive a helper tries to do still surfaces in your main conversation for your approval.
• Limits for now. Only your own custom agents can be targets. Up to five helpers per call, and helpers cannot themselves dispatch further helpers.

See Delegation & Sub-Agents under Build Agents in the help for the full walkthrough.

App Statistics

May 17, 2026 — See exactly what each app costs and who uses it

• Every app in the App Builder now has a new Statistics tab with a full breakdown of its activity. Three top cards split AI credit usage by mode: Design (credits you spent building the app in the App Builder), Execution (credits the app itself consumed when run by users) and Usage (unique users, total opens, opens this month, instances and last-opened timestamp). Each credit number is shown together with its approximate EUR value, using the same per-credit price as the Automations stats so the figures stay consistent across the product. Below the cards, two horizontal bar charts — Lifetime by instance and This month by instance — group unique users and activations per ERP instance, with one row per instance so the chart scales cleanly as more instances adopt the app. Click a legend entry (Users / Activations) to toggle that series on or off.

Per-Tab Active Instance

May 6, 2026 — Active instance is now remembered per browser tab — and across sessions

• Your active instance connection now follows the same persistence model as the agent picker: it's stored both per-tab (so two tabs can be on different instances independently) and as your cross-session default in your profile (so a brand-new tab opens on the instance you last picked from Home). Picking an instance from the Home screen ("New" mode) updates both — that becomes the new default. Loading an old conversation no longer changes which instance the New button picks: the instance selector goes read-only and just shows the connection that conversation is bound to, while your home instance is preserved untouched. Pressing New restores it.

Conversation Properties

May 6, 2026 — Inspect the metadata of any conversation

• The conversation's overflow menu (⋯ in the conversation history sidebar, plus the right-click / long-press context menu) now has a Properties action. It opens a dialog showing the full metadata of the conversation: title, ID, status, type, created/updated timestamps, agent (resolved to its user-friendly name), instance, connection ID, reasoning level, app/site IDs, capabilities, unlocked tools, auto-approved capabilities, and — when applicable — the failure reason and details. Useful for debugging, support requests, and confirming which agent / instance / capabilities a conversation is actually bound to.

Per-Connection Budget

May 5, 2026 — Pick who pays for each connection's AI credits

• Each instance connection can now choose which budget pays for its AI usage: your Home connection pool (the default) or This instance — the per-instance balance an admin allocated to you on that instance. Edit a connection on /my-instance-connections and a new AI credit budget section appears with both options and live balances for each. The This instance option is disabled until an instance admin tops you up there (with the hint "ask the instance admin to top you up"). When selected, AI usage on that connection bills the per-instance budget — and if it runs out you get an explicit error rather than a silent fallback to your home pool. Typical use case: an external consultant whose customer wants to fund the consultant's AI usage on the customer's instance directly. The actual debiting ships in a follow-up release. A new Instance Connections section in /help documents this and the rest of the connection management UI.

User Credit Budgets

May 4, 2026 — Give individual users their own AI credit balance

• The /billing-credits page now has two tabs: Instance Budgets (the existing one-time top-up flow that funds an instance pool) and a brand-new User Budgets tab where instance admins can manage per-user balances. Credits, once topped up to a user, belong to that user — they don't follow the home connection if it changes later. From the new tab admins can: (1) Top up now — move credits from one of their instance pools into a user's personal balance, with a live preview of the pool's remaining credits and the user's monthly headroom; (2) Edit settings — set an optional monthly top-up limit (cap on how many credits can be moved into the user this calendar month) and configure auto top-up (when enabled, picks a threshold + ceiling + source instance — the system will later top the user up to the ceiling whenever their balance falls below the threshold); (3) View history — full audit log of every top-up with type (manual / auto / adjustment), source instance, performer and resulting balance. Monthly totals are computed live from the audit log, so they're always in sync. Usage debiting (consumption of these user balances by AI requests) ships in a follow-up release.

Home Connection

May 4, 2026 — Pick the instance that pays for your AI credits

• Each user now has a single home connection among their ERP.net instance connections. The home connection is the one that will be billed for AI credits going forward (the budgeting itself ships in a follow-up). On /my-instance-connections your home instance is marked with a small Home badge in the Name column, and a Set as home action has been added to the row's overflow menu (⋯) — picking a new home automatically demotes the previous one. The instance dropdown in the top bar also shows a small home icon next to the home connection so it's identifiable everywhere. When you add your first ever connection it becomes home automatically; when you add another internal connection while still having no home, the Add Instance dialog offers a "Set as my home connection" checkbox (pre-checked). Existing users who currently have exactly one connection were backfilled — that one connection is now their home. Users with multiple connections were left untouched and can pick a home from the overflow menu.

Download Link Expiry

May 3, 2026 — Code Interpreter: generated file downloads now expire after 3 days

• Files produced by the Code Interpreter (Excel exports, charts, PDFs, etc.) are stored in Operator's private file storage and surfaced as signed download links inside the conversation. Until now those links were valid for 10 years, which meant the storage bucket grew without bound. Each link is now valid for 3 days (72 hours) from the moment it is generated, and the expiry is shown next to the download (e.g. "link expires in 3 days"); once it elapses, the download button in the file card becomes disabled. A nightly cleanup job at 03:15 UTC removes both the expired storage object and its database record, and writes one summary row per run into the API Logs viewer under log type Cleanup — so admins can spot any failed deletions and the affected paths. If you need a file that has already expired, just re-run the prompt to regenerate it.

Buy AI Credits

May 2, 2026 — Instance admins can now top up an instance

• Instance admins can now purchase AI credit packages for any ERP.net instance they administer. Open the instance dropdown in the top bar and pick Buy AI Credits, or go directly to /billing-credits. Four one-time top-up packages are available — 100 credits for €30, 1,000 for €250, 10,000 for €2,200, and 100,000 for €18,000 — with the per-credit price dropping as the package grows. Credits attach to the instance (not to a single user), so the whole team shares the same pool. Each top-up is logged in Purchase history on the same page. Payments are handled by Stripe; Operator never sees card details.

App Builder for Power Users

May 1, 2026 — App Builder: now available to instance Power Users

• Until now, the App Builder agent required a global Power User role in Operator. It is now also available to users who are Power User or Admin in the currently connected ERP.net instance — even if their global Operator role is just Normal User. The boost is tied to the active instance: disconnect, or switch to an instance where you only have Normal/External access, and the App Builder hides itself again (any in-progress selection falls back to the default agent). Global Power+ users keep unrestricted access regardless of which instance is connected. The same rule gates the Apps page and the Build → Apps menu entry.

Auto-Promote Instance Admins

May 1, 2026 — Instance Admins are automatically promoted to Admin in Operator

• Each time you connect to an ERP.net instance, Operator now checks whether you are an admin in that instance and updates your instance role to match. If you are an admin in ERP.net, you are promoted to Instance Admin in Operator automatically; if you are no longer an admin, your Instance Admin role is dropped to Power User. Lower roles aren't touched. This keeps your per-instance permissions in Operator — entity instructions, permission policies, instance user management — aligned with ERP.net without anyone having to assign roles by hand. Every change is recorded in the audit log.