PrumoGrid

HomeLearnFeaturesFlow

FEATURES / 08

Flow

Stages in sequence: one starts when the previous one is done, in the same terminal or another, and the Flow shows who is working, who is waiting, and what is done.

Updated for PrumoGrid 0.5.11

What it's for

A flow is a sequence of stages in the same project, each with the condition for the next one to start. PrumoGrid delivers the instruction for stage 2 when stage 1 is done, and so on, without you watching the terminal to type the next request. The Flow view, next to Grid and Focus, shows the stages as cards, with the agent, the role, when each one starts, and what makes it done. It is the same plan the Stages tab lists in the sidebar, drawn in order.

Watch the video

VIDEO 04 · 0:54

A simple workflow. Two steps in the same terminal, with the second one inheriting the context of the first. Captions and transcript ↗

When to use it and when not to

Use a flow when one task depends on the result of another: read and then suggest tests, analyze and then fix, fix and then review. It also lets you put two different agents on the same task, one reviewing and the other fixing.

The Flow is optional. If you work only with projects, terminals, the Grid and Focus, you can skip this part. For a single task, use New stage or call the agent directly in the terminal.

Two tasks that do not wait for each other work better as standalone stages.

Step by step

Two stages in the same terminal

Claude Code reads the free-shipping rule in loja-api and, in the same conversation, suggests tests for it.

  1. Select loja-api and click Flow in the bar.
  2. With the Flow empty, click Create flow.
  3. In Task and destination, write Read src/frete.cjs and explain the free-shipping rule in up to three lines. The summary shows the default agent and the project, Claude Code · loja-api.
  4. Click Review stage and then Add to plan. Stage 1 appears as planned.
  5. In the bar below the cards, click + Add stage.
  6. Write Now suggest two test cases for this rule, one line each. Do not change any files.
  7. Check the destination Continue in this terminal and the start once stage 1 is done. Click Review and Add to plan.
  8. Click Run flow. Stage 1 starts.
  9. When Claude finishes stage 1, the card shows continues automatically to stage 2, and the second instruction reaches the same terminal. In the Grid, Claude's terminal has both requests and both answers.

Nothing is delivered while the flow is planned. The cards say "No instruction will be delivered until you run the flow."

Two agents, a file as the bridge

Claude reviews the coupon and writes down the findings; Codex reads the findings and fixes the code.

  1. In Create flow, write for stage 1: Review src/cupom.cjs and write up to three findings in REVISAO.md, with file and line. Do not change the code. Add it to the plan.
  2. Click + New stage at the top. With a planned flow, it opens on Add to the flow, after stage 1.
  3. In Runs on, choose Codex CLI. In Where this stage runs, New terminal. The start is once stage 1 is done.
  4. Write Read REVISAO.md, fix only the first finding, and run npm test., choose Plan only, and confirm.
  5. Click Run flow. Claude starts; Codex waits its turn.

Codex does not see Claude's conversation: they are different programs, in different terminals. The new terminal receives only the next instruction, in writing. That is why stage 1 writes a file and stage 2 starts by reading that file.

What you see on screen

Empty Flow: Create flow builds the stages; Routines uses a ready-made sequence or one of yours.
Three stages, each with its own agent, its own role and its own condition for being done.
After running: each card says what happened and when.
On the cardWhat it means
Claude Code · model: no data · analystThe agent, the model when the CLI reports it, and the stage's role.
Starts:first stage, without waiting, when stage 1 is done, or alongside another one.
Done when:The condition: Automatic, Automatic with verification (with the command, such as npm test), With your approval, or Verification and your approval.
reported at 23:50: done (on its word, unchecked)The stage became done on the agent's report. No command checked it.
continues automatically to stage 2The handoff between the cards. With approval, it says waits for your approval before stage 2.
its own terminalThe stage runs in a terminal of its own. In the same conversation, it says same terminal as stage 1.

The legend above the cards shows the colors of the states: planned, in progress, needs you, done, returned, and rejected.

The Flow bar

  • The selector at the top shows the open flow. A project can have several flows, one per goal, such as "Fix the PRIMEIRA coupon" and "Update the documentation". The Create flow button next to it starts another one.
  • Run flow delivers the first instruction. With the flow running, Pause new deliveries holds back the next ones.
  • + Add stage creates the next stage already chained. Save as routine keeps the sequence for another task; see Routines.
  • The role buttons (implementer, reviewer, checker, analyst, and your own) create a planned stage that already has that role. Configure roles… opens the roles screen. See Roles.
  • Rules for this project · N counts the rules that apply to the project's agents. See Rules.
  • Tracking · history shows only what was observed, with the time.

Continue in this session

At the end of a completed flow, with the terminal still open, Continue in this session creates another stage in the same conversation. Model, effort and permissions stay those of the open conversation. The previous stage no longer marks the end of the flow. If the session was ended, that conversation cannot continue.

Role and sequence

In Other actions, Role and sequence changes the stage's role, its position, and whether it marks the end of the flow. The agent does not restart. A stage that has already started stays in the terminal it was delivered to; to hand work back to another agent, add a stage with the right destination.

Continue in another project

To carry a change from loja-api to portal-web: in Other actions on the source card, Continue in another project… opens the Another project dialog: choose the Destination project and click Plan at destination. New stage opens in the destination project, where you choose the agent and write the task. The destination card shows Waiting for source · loja-api and, once the source is done, Source completed · loja-api. See Across projects.

When the flow ends

The last stage can check This stage closes the flow, in the stage options. In When it closes, choose nothing (it is just recorded), tell me (a notification, the terminal border flashes, and a line in the tracking), run a command (open the diff, kick off a build), or start another flow, which receives the result of this one. The card gets the END OF FLOW badge.

Tips

  • Write each instruction for that stage's work. Stage 2 receives only its own text; the context comes from the conversation, if it is the same terminal, or from a file.
  • Parallel groups: choose alongside stage N so two stages work at the same time. The next stage waits for all stages in the group to be done. Two stages running at the same time cannot use the same terminal.
  • Switching views does not force a delivery. If the next stage has not started, the card and the Stages tab say why.

Known limitations

  • Up to 16 open stages in the project's plan. When there is no room left, the screen tells you and may offer to archive old completed stages.
  • Up to 64 flows in the service. A routine with several stages can take up more than one.
  • The history of one agent's conversation does not carry over to another terminal. Only the instruction is delivered.
  • Automatic advancing happens while the window is open. With the window closed, the terminals keep running, but the next stage only starts when you reopen it.
  • Create flow uses the default agent. For a stage with another agent, use + New stage with the flow planned.