Multiple workflows (World View)

A workspace is a collection of N workflows arranged on a shared canvas: the World View. Each workflow appears as a framed area; you can link agents across frames.

Saved as a .cerevisor-world file. Legacy single-workflow files (.cerevisor / .opaal) auto-wrap into a one-workflow workspace on load.

When to use it

• You have multiple related workflows you want to see side by side.
• You want to chain workflows together (one workflow's output feeds another's input).
• You're building a project that's too big for one workflow.

If you just have one workflow, you don't need to think about workspaces. The single-workflow file format works exactly as before.

The workflow rail

The left edge of the canvas shows a vertical list of cards: one per workflow in the workspace. Click a card to switch to that workflow; the camera flies to its frame.

Long-press a card (or right-click it) for a radial menu (Run, Schedule, Loop, Remove). While a workflow is running the menu shows Pause/Resume, Stop, and Remove instead.

Click + at the bottom of the rail to add a new workflow.

Adding a workflow to a workspace

Click + in the rail (the canvas toolbar's add menu has an Add Workflow entry too).

The Add Workflow modal asks for:

• Folder: the project folder for this workflow (drives the Markdown panel scan, file intelligence, etc.). Required — you pick it first.
• Name: the workflow's display name (pre-filled from the folder name).

The new workflow's frame is placed to the right of the rightmost existing frame, with a comfortable gap.

Switching active workflow

Three ways:

1. Click a workflow's frame on the canvas.
2. Click its card in the rail.
3. Alt+1 through Alt+9: fly to the N-th workflow in the rail order.

Switching preserves per-workflow undo history. Cerevisor snapshots the outgoing workflow's undo/redo stacks before switching and rehydrates the incoming one; Ctrl+Z works on a per-workflow basis.

Cross-workflow links

You can make one workflow feed another through a shared file. Drag from the link handle on a workflow frame's banner and drop on another frame: the Link two workflows modal opens.

You pick one thing: the name of the markdown file that flows between them (default handoff.md). The source workflow's final agent writes that file; the destination workflow's entry agent reads it on every run. It's a plain file in the source workflow's folder — no special wire format.

The link is rendered as a trade-route edge between the frames: a different style from in-workflow edges so you can see at a glance which connections cross boundaries.

The world canvas

The world canvas is just a zoomed-out view of all your workflow frames at once. You can:

• Pan (drag empty space in Pan mode, hold Space, or drag with the middle mouse button).
• Zoom (scroll wheel, or pinch on trackpad).
• Marquee-select: switch to Select mode (canvas toolbar, or press V) and drag empty space; hold Shift to add to a selection.

To edit an individual agent, click its workflow's frame to make that workflow active (the camera flies to it), then work in the normal canvas mode.

The world intro cinematic

The first time you open a multi-workflow workspace, Cerevisor plays a brief cinematic: it starts on the active workflow, pulls back to frame the whole world, then settles back in. It's a delight feature, ~3-4 seconds, and it doesn't block anything — you can pan or click right through it.

• The intro plays once per workspace (workspaces with a single workflow skip it).
• Press Ctrl+Shift+W (Cmd on Mac) any time to replay it.

World stats gauge

A floating pill at the bottom-center of the canvas shows aggregate stats: workflow count, active runs, runs completed today, spend today, total agents, and an estimated-time-saved figure (plus an error count when something failed).

Click the × to dismiss. Re-show via the status bar's eye icon.

Saving

Save (Ctrl/Cmd+S) writes the workspace to its .cerevisor-world file. Save As (Ctrl/Cmd+Shift+S) always shows the file dialog, which defaults to the .cerevisor-world format.

Opening a legacy single-workflow file (.cerevisor / .opaal) wraps it into a one-workflow workspace; your next save prompts for a .cerevisor-world path.

Performance

The world view is performant up to ~20 workflows on most hardware. Beyond that, consider splitting into multiple .cerevisor-world files.

The world canvas uses the same React Flow renderer as the single-workflow canvas, same zoom, same pan, same agent rendering. The bottleneck is total node count (sum of agents across all workflows), not frame count.

When to back out

If a workspace is feeling unwieldy, consider:

• Splitting it into multiple workspaces. One project per .cerevisor-world file.
• Promoting a sub-workflow to its own file. Open the sub-workflow, Save As .cerevisor (single-workflow), then remove it from the workspace.
• Using pipelines instead of cross-workflow links. For purely sequential chains, the Pipeline feature is cleaner than visual links.