Cerevisor 2.0.1: Three Operator Fixes Found by Watching It Work
· v2.0.1
A same-day patch on 2.0.0: dismissing an Operator card now pauses the objective behind it instead of silently vetoing work you adopted, Operator can see what your existing workflows do so it stops rebuilding them under new names, and a generated workflow can no longer come out with the same agent twice.
A patch release, out the same day as 2.0.0. Three fixes to Operator, all found by watching it work for a morning, which is, fittingly, what 2.0.0’s new step trail was built for.
Dismissing something no longer quietly stops the work behind it
When you adopt an objective, Operator also puts a matching card on its agenda. Dismissing that card was telling Operator never to raise the subject again, including the objective itself, which stayed active the whole time. The result was an Operator that had work to do, had been told to do it, and then stood down every check with “the only concrete objective was dismissed”, while nothing on screen explained why.
Dismissing a card now pauses the objective behind it, so Dismiss means what it says, and Allow again brings both back. Work you have already adopted is never silently vetoed.
Operator can see the workflows you already have
Operator knew only the name of each workflow in your workspace and how many agents it had. It could not tell that something it was about to build already existed, so it built it again under a different name: a “Next Task Readiness” and a “Conservative Next-Step Planning Helper” that were the same three steps with the same three roles.
It now sees what each workflow is for and how it is shaped, and it checks a new workflow against the ones you already have before building it. Refining a tool it built for itself is unaffected; the check is against making a second copy, not against improving one.
A workflow can’t come out with the same agent twice
A workflow Operator generated could contain two agents in the same wave doing the same job under different names, a whole duplicate pipeline inside one workflow. Every agent was individually valid, so the completeness check passed it.
Generation now catches a repeated agent within a wave and asks for the workflow again. Two agents with the same role doing genuinely different work are still fine.
Upgrading
Cerevisor updates itself. If you would rather not wait, Settings → Updates → Check for updates.
Nothing in this release changes your data, your settings, or anything Operator has already built.