Release notes

Release notes: 8 November 2026, evening

What changed in the evening release of 8 November 2026, including Agaro Agent as an app, cleaner Agent interfaces with a period switch, Activity for every Super Admin, every app in the Store, App Builder builds that no longer stall, project visibility enforced everywhere, safer Studio buttons, and loading screens that match their pages.

Agaro Agent

  • Agaro Agent is now an app in the Store. It stays on for everyone until a workspace removes it, or an admin turns it off for a person in Users & Roles. When it is off, its page, the docked chat and its button are gone, and the server refuses its requests. App Builder and Studio keep working. See Agaro Agent in the Store.
  • Interfaces in answers draw far more reliably. When part of one cannot be drawn, the rest is drawn and the remainder appears as plain text, instead of a note in place of the answer.
  • Interfaces look cleaner: compact headline figures that never break across lines, a change arrow with the percent, chart axes that are never cut off, bars with a line on the same chart, statement tables with totals, indented rows and costs in parentheses, and outlined action buttons.
  • A period switch (for example Q1, Q2, Q3 and YTD) changes the figures in place without asking again.
  • Answers are written in plain, professional sentences, without dashes between phrases or dash lines between sections.
  • A profit and loss answer no longer lists net income twice.

See Answers drawn as interfaces.

Activity and the Store

  • A Super Admin can always open Activity, unless it was turned off for them on purpose. Workspaces created since mid October could not open it from the bell's View all.
  • The Store's All category lists every app on one page, with the number of apps shown. It used to show only the first 24.

App Builder

  • A build at a high thinking level no longer ends with "Could not produce a usable plan". The planner gets a fixed time to think. If it has written nothing by then, it stops thinking and writes the plan in the time it has left.
  • If you reload the page or open the project again while a build is running, the builder keeps following that build and starts the preview when it is done. A message you send in the meantime waits in the queue. Stop appears only when you can stop the build, and says so if the build could not be stopped.
  • A refresh opens straight on the project, its chat and its preview, never on the "What should we create?" page first.
  • When a build fails because the AI service failed, the time ran out, or the build was interrupted, the newest message offers Try again, which sends the same request with your answers once more. The builder never asks you to say go.
  • The Getting ready card has no previous, pause or next buttons. Its tips move on by themselves.
  • The helpers that build your site are called Agarians. Each one shows as its drawing alone, with no spinning ring around it.

See Building a site.

Who can open a project

A project's visibility (Only me, My team, A group, or Whole workspace) now holds everywhere a project is read: the projects list, opening a project or its address, publishing, versions, search, references to another project, and the API. It holds for Super Admins and Managers too, so a project set to Only me opens for its creator alone. A published site stays public. See Share an app with your team.

Studio buttons and automations

  • A Studio button now runs its workflow's steps for someone other than the person who published it, when the publisher has at least the presser's role and access to that module. Staff pressing an admin's or a Manager's button get the same result as the publisher.
  • When the publisher has less access than the person pressing, for example a Super Admin pressing a Manager's button, its ERP steps are refused with a message saying so, and the workflow receives only the record's id, not its values. The same holds for a retry of that run and for workflows it calls.
  • Test data you pin in the workflow editor is refused when it is nested more than 1,000 levels deep, the same limit a run already has. A retry of an older run with data that deep ends with a clear message.

Loading screens and text

  • More pages show a loading screen drawn from the page itself, so nothing moves when the page arrives: barcode adjustments, email marketing reports and their detail pages, the automation editor, member access, the upgrade page, sales teams, the inbox, referral alerts, the email marketing and campaign lists, an invoice, and the tabs of Workspace Settings.
  • Text is easier to read: body text is a little heavier and darker, and secondary text has more contrast in both the light and the dark theme.