Boards and Flows

The top bar switches between three views of the same engine: Normal (one conversation), Boards and Flows.

Boards

A board puts several conversations side by side in one window, each with its own project, provider, model, chat and workspace. Turns keep running in the same engine; only the presentation changes. Toggle Boards with Ctrl+Shift+B.

Add panes

Add pane offers:

• General chat — no project, with its own working folder;
• one of your projects;
• Open folder…, which registers the folder as a project and starts a new conversation;
• an existing conversation.

You can also send the conversation you’re in to a board with Open in Boards from the sidebar.

Pane status

Each pane shows a confirmed status — Working, Needs you, Finished or Failed — and counts unread results. Panes collapse into narrow strips when you need the space. Needs you means an approval or a question is waiting in that pane.

More panes don’t add provider capacity: several panes on the same provider share its limits. The app warns you past a number of panes, and you can adjust that warning in Settings.

Messaging between panes

The agents of a board can message each other when you enable Messaging between panes. Each pane can receive, send, both or neither. The rules:

• A message from another pane’s agent is untrusted data for the receiver, not an instruction with authority.
• Sending needs your approval per destination pane.
• A message never grants the receiver new permissions, and a turn started by another pane can’t spawn subagents.
• Chains between agents are limited to three hops.

If you want another pane to act on something, use Send to pane…: your message arrives there as your own task, not as an agent message. You can forward a pane’s last response the same way.

Flows

Flows shows how the active conversation advanced, as a sequence of stages:

• a stage is a run of turns in the same mode, drawn as Planning, Implementation or Review;
• a PLAN opens a new cycle, so each plan and the work that follows it read together;
• each stage shows its status (In progress, Needs you, Completed, Failed, Stopped), duration, turns, models and agents that took part, files changed, checkpoints and verification results.

Every value comes from what the engine recorded — turns, changes, tasks and verification — never from a model’s estimate. Progress appears only where there is evidence: a build stage that ended without task data says no data rather than 100 %, and the total says Progress not computable while any stage is unknown. Go to turn opens the turn behind a stage.

Flows needs an engine that offers it; with an older one, the view asks you to update the engine.

The same projection is available in the terminal:

rinari flow                      # the registered project in this folder
rinari flow --session <session-id>