FEATURES / 01
Projects
Each project is a folder on your computer. Terminals, stages and rules are tied to it.
Updated for PrumoGrid 0.5.11
What it's for
A project is a folder that already exists on your computer, usually a Git repository. When you register the folder, PrumoGrid starts opening terminals inside it, showing the branch and open sessions on the project card, and keeping that work's stages, rules and verification there. Selecting a project switches the Grid and the right sidebar together, so you see only what belongs to it.
Watch the video
Organizing multiple projects. Three related projects: one project per repository, one workflow per goal, a worktree, the model for the task, verification, routines and rules. Captions and transcript ↗
When to use it and when not to
Use one project for each repository you work on. In this portal's examples there are three: loja-api (a store's API), portal-web (the website that consumes the API) and pagamentos.
Don't register the same folder twice to separate tasks. For two tasks in the same repository, use a worktree, which is another folder of the same repository on another branch. You also don't need to register the PrumoGrid installation folder.
Step by step
Registering loja-api and opening a terminal in it:
- In the Projects column, on the left, click + add projects… (the same command is in Tools → Add projects…).
- Choose the
C:\demo\loja-apifolder and confirm. You can choose several folders at once. - Check the card that appeared: the project name, the path and the branch line, for example
main. - With the card selected, click PowerShell in the NEW row, above the terminals.
- In the terminal, run
git status. The prompt showsPS C:\demo\loja-api>, because the terminal starts in the project folder.
To see everything at once, choose All projects in the selector at the top. To go back to one project, click its card.
What you see on screen
Each project's card sums up its state:
| On the card | What it means |
|---|---|
| Name and path | The registered folder. Hover to read the full path. |
main · branch · 2 sessions | The branch of the main folder and how many terminals are open in it. Terminals in the project's subfolders count here. |
| Worktree lines | Up to four worktree lines; the rest go under other N worktrees. See Worktrees. |
folder | A terminal opened outside the project folder. |
| Verification | The command that checks the project's work, such as npm test · detected, or No verification. See Verification. |
| waiting for you | An agent in the project is waiting for your answer, such as a permission request. |
| writing off | PrumoGrid does not write guidance to CLAUDE.md or AGENTS.md in this folder. The How to turn back on link explains how to undo it. See Rules. |
Closing a project
The × in the corner of the card closes the project. If there are open terminals, PrumoGrid asks for confirmation. Closing removes the folder from the open catalog and preserves the sessions: no file is deleted, and terminals that are still alive appear under All projects. To register it again, use + add projects….
Tips
- To put the cards in any order you like, drag a card or use Move up and Move down in the
···menu. See Organize projects and terminals. - Give folders short, distinct names. The card name is the folder name, and it is what appears in Attention ("In another project: portal-web is waiting for permission").
- In a new profile, the first terminal that opens on its own becomes part of the first registered project, as long as you haven't typed in it yet.
- A terminal without a project works normally. Only stages, rules and verification require a registered project.
- In Git Bash, the folder appears as
/c/demo/loja-api, and the card understands that it is the same project folder.
Known limitations
- Registering a folder does not clone a repository, move files or install dependencies.
- Worktrees and change review depend on Git. In a project without Git (or in SVN), stages run directly in the project folder.
- Closing a project does not remove its worktrees from disk.