FEATURES / 09
Stages and results
The Stages tab lists each task in the project with its state; the Result shows what was observed, the verification, and the next step, including approving or returning.
Updated for PrumoGrid 0.5.11
What it's for
The Stages tab, in the right sidebar, is the work list for the selected project: each stage created by New stage, by the Flow or by a routine, with its state and the buttons to act on it. When a stage finishes, View result opens what PrumoGrid observed: who did it, what the verdict was, the verification command, the exit code, and the time. That is where you decide the next step, such as reviewing the changes, approving a delivery, or returning it for correction.
Watch the video
Two agents, one workflow. Claude Code reviews, Codex fixes and runs the tests, with a file as the bridge between them. Captions and transcript ↗
When to use it and when not to
Use the Stages tab to see at a glance what is running, what is waiting, and what has finished, without opening terminal after terminal. Use View result before you take in a piece of work: it separates what the agent said from what a command checked.
For the order of the stages and who waits for whom, the Flow shows it better. To answer a permission request, Attention is faster. Opening a result does not run anything again: to check once more, use Check again….
Step by step
Read the result of a fix
A flow in loja-api has two stages: Claude investigates the PRIMEIRA coupon and writes ANALISE.md; Codex fixes it and runs npm test.
- Click the Stages tab. The title shows Project stages · 2, and the flow name appears above the lines.
- Read each line: Stage 1 · Investigate why the PRIMEIRA coupon… with done, and Stage 2 · Read ANALISE.md, fix the cause… with its state.
- On stage 2, click View result. The result takes up the central area.
- Read the stage identification and the verdict: Verification passed, Verification failed, or Completion signal observed, when only the agent reported it.
- In What was recorded, check Command (
npm test), Directory, Expected exit code, Exit code, Verdict and Observed at. - If it failed, open View verification output and read the error.
- In Your next action, choose Review changes, Save as routine or Back to project. Copy result copies the report so you can paste it into a ticket or a conversation.
Approve or return a review
Stage 3 of the flow, with the reviewer, has the With your approval condition. When the reviewer finishes, it appears in Needs you and in Attention.
- Click Review. The Review delivery dialog shows the current excerpt of the reviewer's terminal, with the findings.
- Read the findings. If they are good, click Approve and continue: the next stage, if there is one, is released.
- If something needs to change, click Return for correction…. Choose the Terminal that will make the correction, write What needs to be adjusted, check What will be delivered, and click Send correction to recipient.
Returning opens another round in the same flow: the correction and a new review happen before the following stages are released. The previous review stays in the history.
What you see on screen
The filters at the top appear when the project has stages: All, Needs you and Results. Each line has a dot and a state word:
| State | What it means | Buttons that usually appear |
|---|---|---|
| running | The agent is working on the stage. | Open terminal |
| waiting | The stage is waiting its turn, such as for the previous one to be done. | Open terminal |
| needs you | A permission request, a review, or a decision of yours. | See request or Review, Open terminal |
| waiting for permission | A stage already done whose agent asked for permission again. | See request, Open terminal |
| done | The stage is done. | Continue in this session, View result |
| failed | The agent reported a failure or the verification failed. | View output, Open terminal |
More, at the end of each line, holds the less common actions.
Below the stages you find:
- Sent instructions · N: the instructions PrumoGrid delivered to the terminals, with time and origin. View all opens the list with search, a filter by project and terminal, Go to position (jumps to the instruction in the conversation), and Copy. The shortcut is Ctrl+Shift+I. Commands you type by hand in PowerShell or CMD are not included.
- LOG: what happened: the observed facts, with the time, and the receipts for written rules. See History and writing.
Review changes
Review changes, in the result, and See changes, on the stage, open the diff of the stage's folder.
- Check the directory shown at the top.
- Read the staged and unstaged changes. New files, not yet tracked by Git, show up by name only: their content is not read.
- If you want, write the commit message and click Commit everything….
- Read the Commit changes confirmation: it shows the folder and the message, and warns that changed and untracked files are included with
git add -A. The commit is local; nothing goes to any server.
The diff is the current state of the folder, not a snapshot from the moment of the stage. It may include changes of yours or from another task in the same folder. To keep work separate, use worktrees.
Stages from ended sessions
When you end a terminal's session, its stages leave the default list and the active Flow. To read them, use the Results filter and View stages from closed sessions (N). A temporary drop in the connection to the service does not count as an ended session.
Delete stage or end the session
These are different things:
- Delete stage, in Other actions on the card in the Flow, removes the stage from the plan. Its terminal stays open, with the conversation.
- End session stops the terminal's shell and processes. That does not make the stage approved: a process ending is not a completion.
To change only the command that checks the stage, use Change criterion instead of deleting it.
Tips
- Use the Needs you filter in the middle of the day: it shows only what depends on you, across all the project's stages.
- Before approving a review, open Review changes and read the diff yourself. The reviewer is an agent; the approval is yours.
- Copy result carries the command, the exit code and the verdict, which is what a colleague needs to check the work.
- Sent instructions answers "what exactly did the agent receive?" when its answer seems off from the request.
Known limitations
- The result keeps up to 200 characters of the verification output. The verification runs in the service, outside the agent's terminal, so looking for its output in that terminal may turn up nothing.
- The result shows only events from the same stage. Where there was no event, it does not fill the gap with a narrative.
- The diff may be truncated for large files, and the screen tells you when that happens.
- The interface event history keeps up to 2,000 events.
- Opening a result or the Results filter does not run commands again.