Cerevisor 3.4.0: What's New

3.4.0 is about your work leaving the computer it was made on. A saved workflow now opens and runs on another computer, another user account or another drive, as long as its folder travels with it; and Share turns a workflow or a whole world into one file you can send to anyone who uses Cerevisor, with nothing of your own machine in it. Decisions on the canvas also grew up: you can read exactly what a decision was given, agents that feed a decision are told how much room they have, and a refusal now names its real cause. Saving is safer, and a round of fixes landed in the chat builder, the launcher and the run window.

1. A workflow that moves with its folder

A workflow works in a folder: the place its agents read their input files from and write their results to. When you save, files inside that folder are now written as positions inside it, not as places on your own disk. Copy or move the whole folder, with the .cerevisor or .cerevisor-world file in it, open the file on the other computer, and everything the workflow reads and writes is found again. Files that live outside the folder keep their full location, because they really do live somewhere else and Cerevisor does not guess a new home for them.

If the workflow file travels on its own, the workflow still opens and a card appears above it: This workflow was saved on another computer — Choose the folder it should work in. Your agents’ files will be looked for there. Choose folder points it at a folder on this computer; Create one here makes a new, empty folder named after the workflow, next to the file. If you pick a folder and none of the files the workflow expects are in it, the card stays and you simply choose again, so a wrong first pick is never the final answer. If the workflow uses secrets, the card adds that secrets saved for the old folder will not follow it.

Cerevisor finds the folder on its own in the ordinary cases: the folder sits next to the file or the file sits inside it, the folder it was saved with still exists on this computer, or the file’s own folder already holds one of the files the workflow names. Workflows saved by older versions open exactly as before.

An agent card now marks an input file not there when it is missing and no earlier agent is going to write it. And a run that is refused because its folder is missing carries a Choose folder button that opens the same flow.

2. Share a workflow as one file

Share this workflow… on a workflow’s menu, or Share… in the title-bar menu for a whole world, writes a single .cerevisor-share file. You send it however you like. Nothing is uploaded, and Cerevisor never sends it anywhere for you.

The dialog asks for a name and an optional description, and lists the files to include. Files your agents read are ticked for you; attachments and anything typed into the workflow input start unticked, and you decide. A file that cannot travel is greyed out with the reason — not text, too large (1 MB per file, 10 MB in all), or not found — and left-out files are named in the shared file so the receiver knows what is missing.

What is never in the file: where anything lives on your computer (and therefore your user name), your model, provider and key choices, your connected tools beyond their names, your secrets beyond the names of their variables, actions you approved for an agent, schedules and watch triggers, a Hands-free setting, run history, recordings, chats, pinned notes, and anything your agents wrote. The file is readable JSON, so you can check all of this in a text editor before you send it.

Opening one you were sent: double-click it, use File → Open, or drag it onto the window. The Open shared workflow dialog shows what is inside before anything is written — the name, the description, the agents, the files that will be created, what the sender left out, and anything this computer does not have yet — and says plainly: This came from someone else — look it over before you run it. Cerevisor makes a new folder (under Documents/Cerevisor unless you change it), writes the files there and opens the workflow. Nothing runs on open, nothing you have is overwritten, and the first run shows the ordinary pre-run summary, because your machine has never agreed to anything on this workflow’s behalf. Cerevisor re-checks a shared file with its own rules when it opens it rather than trusting how it was made.

Sharing and opening shared workflows are free on every plan.

3. Decisions you can inspect, with inputs that fit

See what a decision was given. Each decision card has an Inputs button: the connected sources, the exact prepared context the model received, and any preparation problem. A long preview is labelled as a preview; the model context is shown in full. A decision card now shows its inputs and outputs beside it, the way an agent card does.

Producers are told their budget. A decision reads every declared output of each agent connected to it, and the whole context has to fit a fixed size. An agent that feeds a decision now reads its budget in its instructions, and is sent back once if a declared file is over. The budget is one pooled total across the reply and the declared files. The over-length note is advisory: work is never failed for its length. Oversized or missing input is never silently cut down — the decision explains what to prepare and makes no speculative model call.

A refusal names its cause. Where one sentence used to cover three different problems, a decision now says which it was: too large, a file type it cannot read, a missing file, or a file outside the folder.

Evidence from a table. A row of a CSV is never quoted word for word, so evidence drawn from a spreadsheet-style file was always refused. A quote from a .csv or .tsv may now be Label: value pairs whose values all come from one row; an invented value is refused and named. A short verified excerpt can come from a long source document, and unrelated inherited files no longer invalidate an otherwise valid evidence packet.

Design-time warnings. The workflow checker gained three: a file type a decision cannot read, too many evidence sources on one decision, and a deliverable a decision will cap. The builders are told to put a compact brief between a long report and a decision, and to split per-part questions across parallel decisions.

Decision waves are their own waves. A column holds either decisions or regular agents, not both. Prepare evidence in an earlier column, decide in a decision column, and put follow-up work in a later one. The builder refuses an edit that would mix them, and an existing mixed workflow has to be separated before it runs.

4. Safer saves

World and workflow files are now written to the side and swapped in only once complete, so a crash or a full disk in the middle of a save cannot leave a half-written file where your work was.

Also fixed

• Chat builder: when it builds several things in one go, later steps now point at earlier ones by a short handle rather than by retyped name, and names are matched tolerantly (case, spacing, punctuation) when they identify exactly one thing. The same matching is used by Operator’s drafts and Progressive mode. When the canvas refuses some steps, the reply says which, instead of reading as a complete build.
• Signing in to Claude with a setup token: a token still being printed was sometimes captured half-finished and refused. Cerevisor now waits until the token is complete.
• Output check: a free-text sentence describing deliverables is no longer treated as a missing file; only entries shaped like file names count.
• Launcher: the panel belongs to the workflow it was opened for. Switching workflows closes it, and pressing Play on another workflow opens it fresh.
• Run window: a workflow that never ran reads idle instead of borrowing another workflow’s live run header.
• Resuming from a wave asks for the same confirmation a Run button does, and a launch that fails now says so instead of doing nothing.
• Quick checks with a TypeSafe account: a request is validated whole and evidence is no longer trimmed on the way out.
• Repairs to a decision made by the chat builder or Operator are visible and checked before they apply.
• A license whose plan name Cerevisor does not recognise reads as the free plan, instead of locking features every plan includes.

Known limits

• Moving a workflow: Cerevisor looks one level up and no further. If the folder sits two or more levels above the workflow file, you will be asked for it after a move.
• Moving a workflow: a moved project that names no existing file shows the folder card once, even when the folder is right beside it.
• Moving a workflow: an older Cerevisor cannot find files saved the new way. A file saved by 3.4.0 still opens in an older version, but its agents’ files read as names it does not recognise. Ask the other person to update first.
• Moving a workflow: schedules, watch triggers, secrets, run history and chats do not travel. Set schedules and secrets again on the new computer.
• Moving a workflow: answering the folder card is not something Undo takes back. Use Choose folder again.
• Sharing: only text files travel, up to 1 MB each and 10 MB in all. Images, PDFs and the like are named as left out.
• Sharing: a dropped shared file sometimes cannot be read from where it landed. Cerevisor says so; open it with File → Open instead.
• Sharing: a shared file is a snapshot. Changing your workflow afterwards does not change a file you already sent.
• Decisions: an existing workflow that mixes decisions and regular agents in one column must be separated before it runs.
• Decisions: the Inputs view’s file buttons open the current file, which may differ from what was captured when the decision was evaluated.
• Everything listed under 3.1.0’s through 3.3.0’s known limits still applies.

What this was verified on

On the tree this release is cut from, the whole automated suite, the type checks, the desktop-channel contract check, the phone-app checks and a production build were run on one Windows development machine on 2026-09-21.

The type checks printed the same three lines as the previous release; the desktop-channel contract check passed; 965 of 968 test files and 11,774 tests passed in the full run; all 310 phone-app tests passed with its type and boundary checks; and the production build succeeded. Two test files did not pass in the full run: each had one slow test run out of time while thousands of tests were running at once on the same machine, both are on the list of files known to do that, both passed when re-run on their own (11 of 11 tests), and neither touches anything this release changed. The end-to-end suite, the coverage check and the performance check were not run for this release.

Nothing in the sections above has been exercised by hand in an installed app. No workflow was carried to a second computer, no shared file was sent to or opened by another person, and no installer was involved. Those are written down as unverified rows for a person to run, in docs/plans/2026-09-18-portable-share-real-app-checklist.md (PS1–PS20). Nothing in this release claims otherwise.

Platforms

Available for Windows, macOS (Intel and Apple silicon) and Linux (AppImage and Debian package), all built from the same tagged tree by the release workflow.

Updating

Existing installations receive the update through Cerevisor’s built-in updater, and the installers are available from cerevisor.com/download and the private GitHub release. Your workflows, run history and settings carry forward untouched. Saved files gain folder-relative references the next time you save them; files saved by earlier versions open unchanged.