Agent sessions now run on every live campaign
The per-campaign switch for agent sessions is gone, so every live campaign gets agent work. Underneath, agents learned to hand heavy reading to a helper and to ask when a client's own pages contradict each other.
Most of today was under the surface. The visible part is one fewer thing to turn on, plus a date field that now refuses a date it should never have taken.
For our partners
- Agent sessions run on every live campaign. There is no switch to turn on.
- Recording a draft as published no longer accepts a date in the future.
- The “Get Early Access” line under Websites in the sidebar reads on whatever sidebar colour you picked.
1. Sessions without a switch
Agent work was gated on a per-campaign setting that sat on top of the two conditions that already decide it: the client is active and the campaign’s service is live. That setting is gone, and with it the Sessions page’s “turn on sessions” screen and the settings panel whose only control was that switch. Every campaign now starts in the first phase of its profile.
2. Published dates stop at today
A post scheduled to go live next week is not published yet, and recording it as published leaves a link that does not resolve until the site catches up. Every place that records a publish, including draft review, now refuses a date later than today, and the date pickers stop there too. Today is read generously, so the date you are living in is always accepted.
Behind the scenes
- An agent can now hand a reading job to a helper: here is the question, here are the pages, come back with a short answer.
- Site edits are described at one of two levels, pages or shared, and the implementer decides where a shared change lands.
- The agent that plans page optimizations raises a conflict instead of resolving it on its own.
- Client sites running no SEO plugin at all can now have their titles, descriptions and canonicals set the same way any other site can.
1. Reading handed off
A session that reads fifty pages was still carrying all fifty pages an hour later, which made every later step slower and more expensive than the one before it. Letting the session drop old reading helped less than we expected, because dropping has a cost of its own. So the reading leaves the session entirely: a helper opens the pages, answers the question it was given, and returns a short report. On a page-heavy run the main session’s load fell to under a third of what it was.
3. When the site disagrees with itself
One client’s pages stated three different starting prices. The agent picked one, which is the wrong move: only the practice knows which is current. It now asks, and the ask is scoped to facts it would otherwise state in its own copy. We tested that on four scenarios, with and without the rule, to confirm it asks once rather than turning every small inconsistency into a question.
Get these updates by email
A short note when something changes on the platform, plus whatever else you pick.
Check your inbox to confirm your subscription.