HELP / 01

Troubleshooting

What to check first when an agent won't open, a stage doesn't move forward, verification fails or the terminal service is running another version.

Updated for PrumoGrid 0.5.11

How to use this page

Look for the symptom in the table of the matching section. The "Check first" column gives the most common cause; the last column, what to do. The portal search (at the top of the sidebar) also finds symptoms by keyword.

Agents and terminals

Symptom	Check first	What to do
The agent doesn't open or shows as not found	Is the CLI installed and signed in on the side you chose (Windows or WSL)?	Open a regular terminal on the same side and run `claude` or `codex`. In WSL, the installation and login are the Linux ones. Check the command in Tools → Agent profiles….
The CLI asks whether you trust the folder	It is the CLI's first time in that folder	Answer in the terminal itself. PrumoGrid does not answer for you.
`tg` is not recognized	The terminal was opened outside PrumoGrid	`tg` only exists in terminals opened by PrumoGrid.
The terminal opened in the wrong folder	The project selected when you opened it	Terminals start in the selected project's folder. Close it and open it with the right project, or use `cd`. For a terminal outside the folder, the card shows the `folder` line.
Pasting a screenshot doesn't work	Does the CLI accept images?	Use `Ctrl`+`Shift`+`V` to paste the file path, or drag the file onto the terminal. The CLI and the model need to accept images.
Text was not delivered to a terminal	The right terminal, the prompt, an open permission request	Answer the permission in the terminal and see the reason for the hold on the stage. A busy agent can hold the instruction until it is free.

Stages and flows

Symptom	Check first	What to do
The agent finished, but the stage doesn't become done	Open permission request, verification criterion, end-of-turn notification	Read the stage card and Attention. If the stage has verification, it only becomes done when the command passes. In Tools → End-of-turn notification…, check whether the CLI's notification is set up.
The next stage didn't start	The previous stage's condition and the window	The next stage starts when the previous one becomes done, with the PrumoGrid window open. With the window closed, progression waits for you to reopen it.
The stage was saved, but the start was not confirmed	The stage already exists	Resume the existing stage. Don't create another one to make up for it.
Another project is disabled in New stage	How many projects are open	Hover to read the reason: Only one project is open. Register the second project.
Allow and Deny are turned off on the request	The request could not be read safely from the screen (for example, when the terminal wraps the Codex option onto two lines)	Use Go to terminal and answer in the CLI itself.
The request shown has changed	The request is read from the terminal screen	Close the dialog and open See request again before answering.
Stage limit	The plan accepts up to 16 stages	Archive old finished stages when the screen offers to, or start a new flow.

Verification

Symptom	Check first	What to do
Verification failed	Command, folder, dependencies, expected code and the output	Open View verification output in the result. Fix the cause (code, dependencies or the criterion itself) and use Check again.
Verification passes even without the work done	Does the criterion test what was asked?	Write a criterion that fails before the work. See Verification.
Verification takes too long and gives up	The time limit (from 5 to 900 seconds)	Increase the time or use a more focused command.
I can't find the verification output in the agent's terminal	Verification runs in the service, outside the terminal	The output is in the stage's result.
In the worktree, verification fails because dependencies are missing	The worktree starts without `node_modules`	Install the dependencies in the worktree first, or make that the first instruction.

Service, window and updates

Symptom	Check first	What to do
The running service is from another version.	You installed a new version with sessions open	Use Restart now when you can end the sessions, or Later to put it off until the next launch. Reopening just the window does not update the service.
The status bar doesn't say daemon connected	The service stopped or didn't respond	Read the notice on screen. Click the indicator in the status bar to see the available actions.
The Restore banner didn't appear after reopening	Was there a real restart of the service?	It only appears after the service restarted and there are panes with no live session. Reopening the window with the same service does not show the banner, because the terminals are still alive.
The agent's conversation didn't come back after the restart	The CLI's history in the same account and on the same side	PrumoGrid keeps the link to the conversation, not a copy of it. Without the identifier, it opens the CLI's conversation picker.
Windows warns that the publisher is unknown	The installer is not signed yet	Compare the file's SHA-256 with the one published on the website before running it.
The sandbox option doesn't seem to take effect	This launch × Next launch	The choice takes effect on the next app launch. Corporate policies or antivirus may block the sandbox; in that case PrumoGrid opens without it and tells you.

Rules, history and usage

Symptom	Check first	What to do
The agent doesn't follow the rule	The rule's scope, writing allowed in the folder, a conversation opened before the rule	Check Applies to, open See what the agent reads and, if the conversation was already open, start another. With writing off on the card, use How to turn back on.
The rule was not written	Writing receipt	Read the receipt (See what was written). A write error is not a delivered rule; fix the cause and save again.
Usage shows no data	Does the CLI report that data?	No data means unknown, not zero. Not every CLI reports tokens or context.
The history disappeared after clearing	Clear previous records hides that project's old records	Stages, evidence and sessions are still there. There is no way to show the hidden part again in this version.
I can't find the stages of a terminal I closed	Session ended	In Results, use View stages from closed sessions.
I can't remove a worktree	Uncommitted changes	The dialog asks for a stronger confirmation. Without it, nothing is discarded. Commit, or confirm that you want to lose the changes.

How to report a problem

Write down the action you took, the project, the terminal type (PowerShell, WSL, Git Bash, CMD), the exact message and the time. The service log, terminal-grid-daemon.log, is in %TEMP% (up to three 50 MB files). Before sharing screenshots or terminal excerpts, review them so you don't expose code, paths or confidential data.