PrumoGrid

HomeLearnFeaturesTerminals and shells

FEATURES / 02

Terminals and shells

PowerShell, CMD, WSL and Git Bash inside the project, the agent CLIs you already use, pasting screenshots, scrollback, the status bar, and closing versus ending.

Updated for PrumoGrid 0.5.11

What it's for

Each PrumoGrid pane is a regular terminal: a PowerShell, CMD, WSL or Git Bash running on Windows, opened in the selected project's folder. What you type goes to the shell as in any terminal. Agent CLIs, such as Claude Code, Codex and Gemini, are your own programs that run inside these terminals, with your installation and your account. The terminals live in a background service, the daemon, which is why they keep running when you close the window.

When to use it and when not to

Use a PrumoGrid terminal for everything you already do in a terminal: git status, npm test, a local server, an agent CLI opened by hand. None of that requires a stage, flow or rule.

Choose the shell based on the side where your tools are installed. If your Claude Code is installed in WSL's Linux, open a WSL; if it is on Windows, open PowerShell, CMD or Git Bash. The same agent name can be two different installations, with different accounts, one on each side.

Don't use a plain terminal when you want PrumoGrid to follow a task, tell you when it finishes or check the result with a command. That is what New stage is for.

Step by step

Opening two terminals in loja-api

  1. In the Projects column, click the loja-api card.
  2. In the NEW row, above the terminals, click PowerShell. Ctrl+Shift+1 does the same.
  3. In the terminal, run git status. The prompt shows PS C:\demo\loja-api>, because the terminal starts in the project folder.
  4. Click Git Bash in the same row, or press Ctrl+Shift+4.
  5. In Git Bash, run npm test. The folder appears as /c/demo/loja-api, and the project card still counts this terminal as part of loja-api.
  6. Check the card: the branch line now shows main and 2 sessions.

The four shortcuts follow the order of the NEW row: Ctrl+Shift+1 PowerShell, Ctrl+Shift+2 CMD, Ctrl+Shift+3 WSL and Ctrl+Shift+4 Git Bash. WSL and Git Bash only work when they are installed on this machine.

Opening an agent by hand

  1. In the loja-api PowerShell, type claude (or codex) and press Enter.
  2. If the CLI asks you to log in or to trust the folder, answer in the terminal itself.
  3. Ask for something short, for example Explain in one sentence how the PRIMEIRA coupon works.

PrumoGrid recognizes the CLI drawn on screen and shows the pane's state, such as at the prompt. A task typed this way is your conversation with the agent; it does not become a stage and does not appear in the Stages tab.

CLI agents

PrumoGrid does not install or authenticate agents. Install the CLI and log in beforehand, on the side you chose. With no agent at all, the terminals work the same.

Claude Code, Codex CLI and Gemini CLI come already registered. For another tool, open Tools → Agent profiles… and use + Register a CLI agent type: each type states the command that starts the CLI, the side (Windows or WSL), the rules file it reads (CLAUDE.md, AGENTS.md or .tg/spec.md) and what it can report. Registering a profile does not install the tool, and checking a capability the CLI lacks does not give it that capability.

In Tools → Agents → Default agent you choose between Claude Code, Codex and Always ask. This sets the agent that New stage suggests.

End-of-turn notification

To know that an agent finished answering, PrumoGrid relies on a notification from the CLI itself. For agents opened by New stage, Flow or a routine, that notification is already in the launch command: there is nothing to install in the project.

Outside PrumoGrid, in your usual terminal or in VS Code, the agent finishes and nobody finds out. For that case, open Tools → End-of-turn notification…. The screen says, one line per CLI found, whether the notification is ready. Install in Claude Code shows the content and writes it to the project file; the recipes for the other CLIs are under Show recipes. Check the change in Git before committing it.

This notification is different from Windows Notifications, explained in Attention.

Pasting screenshots and images

  • Copy a screenshot and press Ctrl+V in the agent's terminal. The image goes through the CLI's native shortcut, when it has one. Right-clicking with no text selected does the same.
  • Ctrl+Shift+V pastes the file path. PrumoGrid saves the screenshot as a PNG in the profile's attachments folder. In WSL, the path arrives already converted to /mnt/....
  • Drag PNG, JPEG, GIF, WebP or BMP files onto a terminal. The path goes only into that terminal, even with broadcast on.

PrumoGrid does not send anything on its own. Check the reference, write the request and press Enter. The CLI and the model must accept images or read the indicated file.

Interrupting, copying and scrolling

Ctrl+C with no text selected interrupts the foreground process, as in any terminal. With text selected, Ctrl+C copies; Ctrl+Shift+C also copies, with no risk of interrupting.

Each terminal keeps 5,000 lines for you to scroll back. To change that, open Tools → Advanced options…, section Terminals, field Scrollback lines per terminal: from 1,000 to 50,000. It applies to terminals opened after the change. The agent's conversation is still stored in the CLI itself.

What you see on screen

Three loja-api terminals. At the top, the NEW row; at the bottom, the status bar with the color legend and usage.
On screenWhat it means
at the prompt in the pane headerThe shell or CLI is idle, waiting for you.
✓ 325ms in the headerThe last command finished successfully and took that long.
daemon connected in the status barThe window is connected to the service that keeps the sessions.
agent: claude codex · shell: PowerShell CMD WSL Git BashThe color legend: each agent and each shell has its own, repeated in the dot in the pane header.
3 persistent sessionsSessions open in this window that live in the daemon and survive closing the window.
3 terminals · 0% CPU · 383 MB RAMThe combined usage of the terminals, counting the processes each one started.
1 waitingAn agent is waiting for your answer. Clicking takes you to it.
Agent profiles: command, rules file and features of each CLI type.
The end-of-turn notification already comes set up in PrumoGrid terminals. Installing it in the project is for when the agent runs outside PrumoGrid.

Closing a pane or ending the session

The × in the pane header, or Ctrl+Shift+W, opens the Close terminal question with two ways out:

  • Close and keep the session removes the pane from the grid. The shell and the process keep running in the daemon.
  • End the session ends the shell and every process it started. Unsaved work may be lost.

Closing the PrumoGrid window is something else: the terminals stay in the daemon and come back when you open it again. To stop everything there is Stop the daemon and every session, in the persistent sessions indicator in the status bar, which asks for confirmation and says how many terminals will end.

Tips

  • Double-click the pane name to rename it. Names like Reviewer and Implementer help when there are several identical agents. See Organize projects and terminals.
  • In PrumoGrid terminals, tg --help shows the help for the local integration, which agents use to signal the end of a task.
  • CMD expands variables even inside quotes. If PrumoGrid refuses to open an agent through CMD because the instruction has a character like %, open the agent through PowerShell or Git Bash.
  • If you want to read a terminal calmly, use Focus.

Known limitations

  • PrumoGrid does not install, update or authenticate agent CLIs, and does not change their settings.
  • Pasted screenshots stay in attachments inside the profile until you delete them. Each screenshot can be up to 20 MB and 40 million pixels; one drag accepts up to 16 files.
  • A folder that only exists inside WSL does not receive rules through Windows and cannot have a worktree created by the app's Git.
  • Terminal scrollback has the ceiling chosen in Scrollback lines per terminal. It does not replace the CLI's history or a backup of your files.