FEATURES / 19
Resume after restart
What keeps running when you close the window, what happens when Windows restarts, and how PrumoGrid reopens the terminals and the agents' conversations.
Updated for PrumoGrid 0.5.11
What it's for
PrumoGrid's terminals don't live inside the window. They run in the terminal service, the daemon, a separate process that keeps the shells and agents alive. The window only connects to it. That is why you can close the window in the middle of a task and open it again with everything as it was. Restarting Windows is a different situation: then the processes end. When you come back, PrumoGrid offers to reopen the terminals in the same folders and resume the Claude Code and Codex conversations. This page explains each case and how to shut things down in the right order.
Watch the video
What PrumoGrid is. Projects, terminals and CLI agents on Windows, the service that keeps everything running, where the name comes from and the areas of the screen. Captions and transcript ↗
When to use it and when not to
Count on persistence to close the window at the end of the day, free up the screen or update the app without losing what is running. Check the status bar to confirm you are in persistent mode: daemon connected and N persistent sessions.
Don't count on it to carry live processes across a Windows restart: an npm test or an agent in the middle of an answer stops when the machine shuts down. And don't count on the Flow moving forward automatically with the window closed: that happens in the window.
Close the window
With the status bar showing daemon connected, closing the window disconnects the interface and leaves the sessions in the service. If there is work that depends on the window, such as a flow waiting for the next stage, PrumoGrid asks first:
- Close the window. Close this window? appears, with the state read from the service, for example 3 terminals continue running.
- Read the notices: The next stage will not start while the window is closed. and Reopening resumes monitoring and automatic progression.
- Choose Keep open, if you want the flow to carry on by itself, or Close window.
If there are only terminals and no stage depends on the window, it closes right away. Not being asked does not mean the sessions ended. With the window closed, whatever an agent finishes in the meantime is recorded with the real time when you reopen, and waits for you to ask for verification.
In local mode, when there is no persistent service, the status bar shows local panes, and closing the window ends the terminals it hosts. The dialog says so.
Reopen the next day
When you open it again, the panes reconnect to the same sessions, with the text that was already in them. The Since your last visit banner sums up what changed while you were away:
- 1 stage has updates and 1 decision needs you, for example.
- Each item names its source: Source: agent (the agent said it finished) or Source: verification (a command passed or failed it).
- View updates opens the list, Go to pending decision takes you to what is waiting for you, and Dismiss closes the banner.
Dismissing means you saw it. It does not approve a stage or run a test.
Step by step
Resume after restarting Windows
The example: on Friday night, loja-api had a PowerShell, a Claude Code and a Codex in the Grid. Windows restarted over the weekend.
- Open PrumoGrid from its shortcut. Because the previous service no longer exists, a new service starts.
- The Restore banner explains, for example, that 3 panes from the previous layout have no live session because the daemon restarted, and that restoring opens 3 new terminals in the same folders.
- Click see the folders to check where each terminal will open.
- Click Restore all 3. The terminals reopen in
C:\demo\loja-api. Claude Code and Codex reopen the identified conversation; if PrumoGrid did not keep the identifier but recognizes the agent, the CLI opens its own picker so you can choose the conversation. - If you'd rather start from scratch, use Start clean (the previous layout is kept as a copy). The copy goes into the saved layouts, named Previous layout: with the date.
Since 0.5.11, the Restore banner only appears after a real restart of the service and when there are panes with no live session. Reopening the window with the same service does not show it. If the query to the service fails, nothing is opened or discarded: the layout is kept for the next launch.
The conversation must still be available in the CLI, in the same environment and the same account. A Claude Code conversation started in WSL is not found by the Windows Claude Code. PrumoGrid keeps the link to the conversation, not a copy of the messages.
Service from another version
Installing a new version of PrumoGrid does not replace the service that is already running your sessions. When the service code has actually changed, a line appears at the top of the window: The running service is from another version., with two buttons.
- Restart now asks for confirmation, says how many sessions will end, restarts the service and reopens the app. After that, the Restore banner offers to reopen the terminals.
- Later hides the line until the next launch. Nothing forces you to shut down now.
When updating from 0.5.10 to 0.5.11, the line appears once, because the 0.5.10 service does not report which code it runs. From 0.5.11 on, it only comes back when the service changes. Reopening just the window does not update the service.
Update without losing your work
In Tools → Advanced options… › Updates, a new version tells you whether it replaces the service. This update does not replace the service means terminals and sessions carry on; This update replaces the service warns that open sessions will end on restart. Choose Reopen now when you can stop, or On close to install when you close the app. With the installer downloaded from the website, close the window before running it; the terminals stay in the service and come back when you reopen. Details in Language and sandbox.
Finish a stage, a pane, a project or the day
| Action | What happens |
|---|---|
| Stage finished by the agent's notice | Records the observed statement; it can release the next stage, depending on the condition. |
| Stage approved by verification | Records the verification command's verdict. |
| Delete stage | Removes the definition from the plan. The terminal is not ended because of it. |
| Close project with the × on the card | Asks for confirmation if there are terminals, keeps the sessions and removes the folder from the open catalog. No file is deleted. |
| Close pane | Removes the pane from the grid; the session carries on in the service. |
| End session | Ends the shell and the processes it started, after confirmation. |
| Close window | Disconnects the interface. In persistent mode, the sessions carry on. |
| Stop the daemon and every session | Stops the service and all its work, after confirmation. |
Don't end the shell just to "check off" a stage. A process that ended is not an approval.
Shut everything down
To stop the service and all sessions, for example before maintenance on the machine:
- Save what you need and check which processes are running.
- In the status bar, click N persistent sessions. The menu reminds you that the terminals stay alive when you close the window and that automatic progression between stages stops while it is closed.
- Choose Stop the daemon and every session.
- Read the confirmation, which shows how many sessions will end and how many terminals appear to be running, and confirm.
- Wait for the message that the daemon stopped.
Tips
- At the end of the day, close the window instead of ending the sessions. The next morning the terminals are there, with yesterday's output.
- Before restarting Windows, leave the agents at the prompt. An answer cut in half is not resumed from where it stopped.
Known limitations
- Restarting Windows ends every terminal process. PrumoGrid reopens new terminals; whatever was running has to be run again.
- Resuming the conversation depends on the CLI still having that conversation, in the same environment and account.
- With the window closed, stages don't move forward on their own.
- In local mode, closing the window ends the terminals.