Atarim 5.1.2: your experts' memory is now yours to read and edit
Every conversation you have had with your AI experts since 5.1.0 has been teaching them how you work.
- The client who insists on British English.
- The plugin you never recommend.
- The way you want a recommendation costed before anyone touches a site.
They wrote it all down and it has been steering every job since.
From today that memory is yours. Open it, read what they have learned about your agency and each of your clients, and change anything that is wrong. That is what this release is for.
Alongside it, WordPress work is faster and costs fewer credits, because your experts stop asking a site the same question twice.
New features
Your experts now have a memory you can read and edit
The specialists keep one memory for your workspace and one for each project. The workspace memory is read on every job. Each project memory is read alongside it, on that project only. Until now the experts were the only ones who could see either.
Settings → AI Web Agency → Memory shows both.
Open one and you are reading the experts' own notes on how you and that client work. Two ways to change it. Edit opens the file itself. Notes for your experts takes a plain sentence ("stop suggesting Elementor Pro") and folds it in on the next sweep, so you never have to write in the file's own structure.
We tested it the way you would use it, in a task on a client site:
Remember these for this project going forward: the client writes in British English, they do not want to be sold Elementor Pro, and every recommendation should state its credit cost before we act on it.

The three rules landed in the project memory exactly as written, under three headings, attributed to the person who asked. Project memory reaches task chat, so that is where they show up. Owners and admins edit, contributors read, clients and collaborators do not see it.
One thing worth saying plainly, because memory makes people ask: nothing you or your clients put into Atarim is used to train AI models. Not ours, and not our providers'. Every request goes to endpoints that keep neither the prompt nor the response. The full detail is in our Platform privacy notice and DPA.
WordPress work is faster and costs less
Every time a specialist works on a connected WordPress site it first has to find out what the site can do. On a site running JetBackup, Elementor, WPForms and Yoast that is a list of 264 tools, most of them nothing to do with the job in hand, fetched again for every task and every step of every workflow.
Plugin 5.1.4 changes how that conversation runs. The specialist asks for one area at a time, and runs many abilities in a single request instead of one call each. We ran the same listing on the same site before and after updating: 264 tools, then six. Skills carry their own tools, so a specialist activating a skill starts with what it needs rather than searching for each one. Automation steps begin with the tools they used last run.
Fewer round trips to your site means less waiting between a request and a result, and fewer credits spent getting there. Nothing to switch on; update the plugin and it applies to every task and workflow on that site.
Improvements
Restore points tell you when they are ready. On a site running JetBackup, readiness is tracked until the snapshot actually reads as ready, so a point that is still arming is never mistaken for cover. The previous locked snapshot is released and snapshots marked for deletion are cleaned up. We asked Glitch on a test site:
Take a restore point of this site first. Then tell me the WordPress version, the PHP version, and which plugins have updates waiting. Report exactly what happened with the restore point, including whether it is actually ready to restore from.

The answer named the job, said the database was dumped and files were still archiving, and stated plainly that the new snapshot was not yet ready to restore from while the one from 4 September was. That is the sentence you want before risky work.
Or put it on repeat: Weekly backup and verification in the workflow library confirms every site has a recent, restorable backup and warns you when cover slips.
Schedules stay as you wrote them. The picker preserves cron expressions it cannot represent, so "last day of the month" and "second Tuesday" survive an edit. A recurring workflow with no schedule is refused before saving, and a run is priced from its schedule rather than at zero.
Straighter answers from hosting and the site. A firewall that blocks a call says so. A hosting provider that is not connected returns its own message instead of a gateway error. An unreachable WordPress site is reported as unreachable rather than landing in your approval queue as a "destructive" action.
AI review knows when it has finished. Failure is announced once, when it has actually failed; a failed retry keeps your issues; the tasks tab shows loading with a retry instead of "complete" while results stream in.
White-label. The default logo is a PNG that renders in email, and a brand colour without its hash still makes valid CSS.
Smaller things. The Slack channel picker pages and surfaces fetch failures. Help links in settings and inbox point at articles that exist. Tablet scrolling, review stickers in device preview and the graphics small-screen notice are fixed.
Bug fixes

- Onboarding and plugin activation. Terms must be accepted before an account exists. An empty "Other" role is refused. A domain the crawl could not read gets a clear message and a retry, and the plan works from what you typed. An already connected WordPress site says so and offers a way forward. Activating the plugin on a site you already added merges onto that project instead of creating a second one. One-click login from the dashboard establishes a real WordPress session, and a blocked popup tells you. New client accounts no longer crash on first login, and a multi-project client lands on all their projects.
- Clients, folders and archiving. Archiving every project in a client folder keeps the folder visible and the client manageable. Deleting all of a client's projects no longer blocks re-adding them, and a project can be taken back out of a client folder.
- Automations and integrations. Tag Added runs Add Comment. Asana picks up task updates. A ClickUp attachment with an empty path no longer crashes the sync. Make gets its page info. Comment integration references save cleanly. Webhooks carry the original HTML alongside every flattened field.
- Chat and the specialists. A chat thread survives a model that takes over 45 seconds to send its first token. Elementor edits are validated before save, so a bad setting no longer aborts your next Publish. The WordPress connection recovers a lost session. On some hosts WP-CLI reported a successful command as failed; it reports success.
- App surfaces. Pagination in the feedback experience no longer hangs without the Chrome extension. The sidebar keeps its width. Cookie consent sticks. Share no longer crashes from the widget or the project card. Filter by latest activity works. Comment attachments download from the plugin. Old-storage avatars load. Free-plan projects from the Chrome extension keep AI on.
- Billing. Credit pack checkout no longer fails. A cancellation the billing system refused is reported as refused, and cancel-to-free works on both routes.
Coming next
Built and live for our team, opening once they have run against real customer sites:
- Do It without a browser tab. Do It runs from the backend, with undo, whether or not anyone has the page open.
- Browser-side task screenshots with a one-time consent prompt, so logged-in state and dynamic content are captured.
Go and read your memory
Open Settings → AI Web Agency → Memory.

Take a look through what your experts have written down so far. Some of it is probably going to be spot on, and some of it you'll want to tweak or correct, and that's exactly how it should be. The whole idea is for your agency to run the way you run it, and now you finally have a way to check that it does. Have a dig around and let us know what you find.
Vito






















