PrumoGrid

HomeLearnHelpGlossary

HELP / 02

Glossary

PrumoGrid terms in alphabetical order, with what they mean and where they appear on screen.

Updated for PrumoGrid 0.5.11

A–C

TermWhat it means
AgentA CLI that receives instructions and works on the project with your account, such as Claude Code, Codex or Gemini. PrumoGrid opens it and follows along; the agent writes the code. See The agents are your CLIs.
Agent profilesThe registry of CLI types (command, side, capabilities), in Tools → Agent profiles….
ApprovalA stage marked With your approval is only done when you approve the delivery (Approve and continue) or send it back (Return for correction…).
AttentionThe right sidebar tab with what needs you: permission requests, reviews and notices, including from other projects. See Attention.
BroadcastSending the same text to several selected terminals. See Send to multiple terminals.
CLICommand-line interface. In this portal, almost always an agent's CLI.
Command paletteThe list of commands opened with Ctrl+K. See Search and shortcuts.

D–F

TermWhat it means
DaemonThe background terminal service that keeps sessions alive when the window closes. The status bar shows daemon connected. See The daemon holds the sessions.
End-of-turn notificationThe signal the CLI gives when it finishes answering. It is what lets a stage without verification be done. Set up in Tools → End-of-turn notification….
EvidenceWhat was observed about a stage: the verification's output and exit code, the agent's notification, the approval. It appears in View result.
FlowThe sequence of stages for a goal, with dependencies between them. Also the central view that shows that sequence. See Flow.
FocusThe view that shows one terminal large and the others in a strip of thumbnails. See Grid and Focus.

G–P

TermWhat it means
GridThe view with the project's terminals side by side.
ModelThe AI model the CLI uses. When it is empty on a stage, the CLI's default applies.
Permission requestWhen the CLI asks for authorization to run something. It appears in the terminal, on the card, in Attention and in the status bar; See request opens the dialog.
Profile (TG_PROFILE)A separate set of data and service. Without the variable, PrumoGrid uses %APPDATA%\TerminalGrid.
ProjectA registered folder, usually a repository. See Projects.
Project cardEach project's block in the Projects column: name, path, branch, sessions, worktrees, verification and notices.
Prompt guideIn Focus, the list of instructions sent to the terminal in the spotlight, with a filter and a jump to each one. See Prompt guide.

R–S

TermWhat it means
ResultA stage's screen with its identification, the verdict, the recorded facts and the verification output. See Stages and results.
RoleThe agent's responsibility in a stage, such as analyst, implementer, reviewer or verifier, with its own rules. It does not depend on the CLI. See Roles.
RoutineA sequence of stages saved to repeat with another task. See Routines.
RuleGuidance that always applies to the agents within a scope: a project, every project, a role or a CLI type. See Rules.
SandboxChromium's protection for the app's interface. It does not isolate the commands in the terminals. See Language and sandbox.
See what was writtenThe receipt of what was written when rules were applied: paths, files, copies and failures. It is not a video of the terminal. See History and writing.
SessionA live terminal in the service, with its shell and its processes. Closing the pane can keep the session; ending the session ends the shell.
SideWhere the command runs: Windows or WSL. The same folder has different names on each side (C:\demo\loja-api and /mnt/c/demo/loja-api).
StageAn instruction, who runs it and when it is done. Created by New stage, by Flow or by a routine. See New stage.

T–W

TermWhat it means
TerminalA pane with a shell (PowerShell, CMD, WSL or Git Bash), opened in the project folder. See Terminals and shells.
tgThe local integration command, available in terminals opened by PrumoGrid (tg --help).
TicketAn item from a task list (GitHub, Jira or a command of yours that returns JSON) that becomes a stage draft through Start from a ticket….
Tokens per sessionInput and output of the observed conversations, per session, when the CLI reports them. It is not a billing amount.
UsageCPU, memory, processes and, when the CLI reports them, tokens and context for each terminal. See Usage and limits.
VerificationA command that checks the stage (for example npm test) and decides whether it is done. See Verification.
WorktreeAnother folder of the same Git repository, usually on its own branch, to keep pieces of work apart. See Worktrees.
Writing in projectsThe permission, per folder, for PrumoGrid to write the guidance block to CLAUDE.md or AGENTS.md. Different from See what was written. See Rules.