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.

Right-click a card for a radial menu (activate, duplicate, settings, delete).

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

Adding a workflow to a workspace

Click + in the rail, or File → Add workflow… in the title bar menu.

The Add Workflow modal asks for:

• Name: the workflow's display name.
• Folder: the project folder for this workflow (drives the Markdown panel scan, file intelligence, etc.).
• Template: blank, or a starter template.

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 wire an agent in workflow A to an agent in workflow B. Drag from a workflow frame to another frame on the world canvas: the Cross-Workflow Link modal opens.

Configure:

• Source agent: which agent in workflow A produces the data.
• Target agent: which agent in workflow B receives it.
• Data description: free text.
• Handoff format: Summary / Structured JSON / File Reference / Full Output (same options as in-workflow connections).

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, or hold Space + drag).
• Zoom (scroll wheel, or pinch on trackpad).
• Marquee-select (Shift + drag): but selection within the world view selects frames, not individual agents.

To edit an individual agent, double-click into its frame (zoom in) and work in the normal canvas mode.

The world intro cinematic

The first time you open a multi-workflow workspace, Cerevisor plays a brief cinematic: a fly-through that frames each workflow in turn. It's a delight feature, ~3-5 seconds.

• Press Esc to skip.
• The intro plays once per workspace ID (cached in localStorage).
• Press Ctrl+Shift+W any time to replay it.

You can disable the intro globally in Settings → Learning Experience.

World stats gauge

A floating pill at the top-right of the world canvas shows aggregate stats: total agents, total waves across all workflows, current run cost.

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

Saving

Save (Ctrl/Cmd+S) writes the workspace to .cerevisor-world. Save As lets you pick a new path or write a legacy single-workflow copy.

The save dispatcher knows whether you have a workspace (multi-workflow) or a single workflow open. Single-workflow files don't promote to workspaces unless you explicitly add a second workflow.

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.