It crashed or my computer restarted
Sessions that were working come back by themselves when you reopen Yardmaster.
Quick question
What do you need?
To know what happens when I reopen it
What you see when you reopen Yardmaster
Read it in Sessions come back after a crash or restartThe window opens and every session that was working shows Starting. You can use the app straight away.
A message appears: "Resuming 4 sessions from last shutdown" (with your number). It has a Stop button and stays until all of them are back.
The sessions come back one at a time, a few seconds apart. Each gets a short "Please continue" message, marked with a small badge so you can tell Yardmaster sent it, not you.
With a dozen or more sessions this can take several minutes. That is on purpose, so reopening never freezes your computer. Nothing is dropped for being slow.
One session back right now
Want one back right now?
Read it in Sessions come back after a crash or restartOpen it and click Restart now on its "Restoring this session" line, or just send it a message. It jumps the queue and starts at once; your message becomes its first turn instead of "Please continue".
If that session is the one being started at that very moment, you see "try again in a moment" for a few seconds.
A session did not come back
When one does not come back
Read it in Sessions come back after a crash or restartIt turns red a few seconds in. Yardmaster tries once more, replaying the conversation. If that also fails, it stays red for you to open. Common causes are a moved project folder, a sign-in that needs renewing, or a full disk.
It shows "Recovery failed". It made the app crash three times in a row while coming back, so Yardmaster stopped trying and the rest of your sessions open normally. Send it a message when you are ready.
Its project folder is missing (an unplugged drive, a renamed folder). It is skipped until the folder is back.
Keep Relaunching a Session Until It’s BackSettings, Workflow · Default: OnWhen a session that was running fails to launch because the machine is momentarily overloaded (a transient OS hiccup), keep retrying, with a growing gap between tries, until it comes back, instead of giving up after a few attempts. Genuine errors still stop and turn red.Open in YardmasterOpens Yardmaster. Don't have it? DownloadFor a reply that stops halfway while the app is running, see My agent stopped responding.
The gap between sessions is at least 5 seconds and grows while your computer is still busy with the previous one.
A session waiting on you (a question or an approval) when the app closed is restored as it was, whether or not Auto-Resume is on.
If another copy of Yardmaster is already using the same data, nothing is resumed, so two copies never run the same session.
Interrupted sessions show in the Inbox even with Auto-Resume on, until they are back.
Other engines (Codex, Gemini and others) that were cut off when you closed the app come back the same way, through their own resume.
Sessions to stop coming back
Stop sessions from coming back
Read it in Sessions come back after a crash or restartThis time only: click Stop on the "Resuming" message. Sessions that had not come back yet stay stopped, quietly, and you can restart them later from Manage sessions.
Every time: turn off Auto-Resume Sessions on Restart. The same switch is in the Manage sessions window as Resume sessions when Yardmaster restarts.
Auto-Resume Sessions on RestartSettings, Workflow · Default: OnAutomatically restart sessions that were active when the app was closed or crashed. Running sessions receive a continue nudge. Sessions waiting for your input are restored.Open in YardmasterOpens Yardmaster. Don't have it? DownloadWith it off, those sessions wait for you in the Inbox instead: one cut off when you closed the app shows Interrupted, and one cut off by a crash shows Error. Send it a message to carry on.