Several projects day to day

The scenario

You work on three related repositories: loja-api, portal-web, which consumes the API, and pagamentos. On some days there are agents running in all three. This recipe brings together the practices that keep that organized, from the start to the end of the day.

Watch the video

VIDEO 12 · 1:00

Multiple projects, day to day. A permission from another project through Attention, the Steps filters, Usage, closing a terminal and search. Captions and transcript ↗

Organize once

1. One project per repository. Register the three folders. Terminals, stages, rules and verification are tied to the project, so mixing repositories in a single project muddles all of that. See Projects.
2. Verification in each project. Check the Verification line on the card (for example npm test · detected). For stages that touch code, ask for the stage to be done only when the command passes. See Verification.
3. Project rules for what always applies. "Reply in Portuguese", "do not change package.json without telling me" and the like go in Rules and roles…, once per project, or in For every project if they apply to all of them. See the recipe A rule that applies to every agent.
4. Routines for what repeats. If you review and fix every week, save that as a routine. See A routine to repeat every week.

When you start the day

1. Open PrumoGrid and look at the status bar: daemon connected. Yesterday's terminals are still there, if the computer did not restart. If it did, PrumoGrid offers to restore the terminals and resume the identified conversations. See Resume after restart.
2. Read the Since your last visit banner, when it appears: it sums up what happened while the window was closed.
3. Look at the project cards: waiting for you means an agent is waiting for an answer.

During the day

One project in view, the others in Attention

Select the project you are working on. The Grid and the sidebar show only that one. When an agent in another project asks for permission, Attention shows it at the end of the list, for example, In another project: portal-web is waiting for permission.

1. Click the line. PrumoGrid selects portal-web and takes you to the terminal that asked.
2. Use See request, read the command and answer with Allow or Deny.
3. Click the loja-api card to go back.

Enlarge screenshot ↗

Stages by project

The Stages tab shows the selected project's stages. The All, Needs you and Results filters appear when there are stages; Needs you is the most useful in the middle of the day.

One flow per goal

In Flow, keep one flow for each goal: "fix the coupon" is one, "update the documentation" is another. The flow selector switches between them, and you read one piece of work at a time.

Two agents in the same repository

When two agents are going to work on loja-api at the same time, create a worktree for one of them: a second folder of the repository, on a separate branch. The card shows the line, for example, cupom-fix · worktree · 1 session. See Worktrees.

The right model for each task

Each stage's model field accepts the identifier your account offers. For a short task (explaining a script, changing some text), a smaller model usually does the job and answers faster. To find the cause of a bug, a larger model is worth it. When it is empty, the stage uses the CLI's default.

Usage and idle terminals

1. Turn on Tools → Rules and Usage tabs in the sidebar and open the Usage tab to see the CPU and memory of each terminal, adding up the processes it started.
2. If a terminal is heavy, use Limit… on its row or Tools → Memory and CPU limits….
3. An idle PowerShell in pagamentos that will not be used anymore can be ended (End session). That ends the shell and whatever runs in it.

Finding things

• Ctrl+Shift+F searches terminals, stages and rules ("cupom", for example).
• Ctrl+K opens the command palette: projects, terminals, Project verification… and the shortcuts.

When you end the day

If there is work that depends on the window, PrumoGrid asks Close this window? and offers Keep open or Close window.

Tips

• Short folder names that differ from each other make Attention and the cards easier to read.
• Leave the Windows notifications only on When I am needed if the others are too much; Attention and the cards keep showing everything.
• When a project drops off your radar for a few days, close its card (the ×). The files stay, and the live terminals remain reachable under All projects.