state, the model (and effort, when it takes one) it was started on, when you picked one, an amber **checks off** badge while permission checks are off, and **Change agent** once it has
conversation, since New Session already does that in one click. The dashboard's **UPDATE AVAILABLE**
banner still shows, beside the bar's own **Update available**, and its steps say to run the command in a
terminal outside the app and then reopen the app (see "Keep it up to date" below). A slash command still offered to continue a step (such as `/plan2code-4-finalize`) stays
- **Strength per phase** (off): turn on **Set strength per phase** to see one row per phase still to build under four headed columns, **Match my session**, **Thrifty**, **Balanced** and **Best**, and click a dot in a row to pick (the arrow keys move along a row), or use **Set all to** for one pick. A thick line steps through each row's picked dot, so the choices read at a glance, and the model each pick becomes shows at the end of its row. A phase you leave untouched runs on the model the app was launched with, as before. A phase whose agent crashes or goes quiet gets its one retry (when the retry tick is on) one step up (Thrifty to Balanced, Balanced to Best; Best stays Best; **Match my session** runs on the launch model and its retry stays there), and the phase's helpers follow the same strength. Which model each word means for your agent is set in User Preferences, **Agents & models**, under **Strengths in the loop**; an agent with nothing mapped shows the toggle off with a link there. The picks are remembered per project and spec, and a pick for a phase that is done or gone is dropped.
names the project and spec and the phase as `Phase 2 of 4 (name)`, and, except the finish message (run time only), ends with the time the phase and the
**Send a test** saves the setup and sends a test message right away, after the app names the address in its
own window, so a wrong address shows up before a long run. A name can use letters, digits and `- _ . ~`. Pasting a Discord, Slack, Teams or Google Chat address picks
its choice for you, since a plain GET to a Discord webhook answers 200 and posts nothing. The call has 10
seconds and any 2xx answer counts. One that fails never changes what the loop does: the finish line or the
stop screen's evidence says so, without repeating the address, which is stored in `loop-setup.json` and
usually holds a token.
**It uses the app's agent.** The loop starts every phase on the agent and model you launched the app
with, and it needs permission checks off. With them on, an agent would wait on a prompt that nobody
sees, so **Start the loop** stays grayed out until you turn them off (see
[Permission checks are off by default](#permission-checks-are-off-by-default-same-as-the-terminal)).
**What is locked while it drives.** Answers, sign-offs, launches, Workspace, Helpers, **Back** and
**New Session** are read-only, and Ask is off, except for a question the loop is waiting on. Activities, Notebook, Help, Preferences, the documents
and the code review stay usable, so you can watch, play, or read along.
**You can always see it's running.** From the moment you confirm Start until the loop ends, a banner runs
across the top of the window, outside the console page, so it stays put as each phase's session comes and
goes. It says what the loop is doing right now (starting, building, between phases, stopping), with the
phase, its name and step, a pip per phase, the time so far and any retries. It turns amber when a question
needs your answer. The window title says the same, for the taskbar. While the loop works, the page's Send
button and "Nothing to send" line go away, and they come back when a question waits.
**Stopping it.** Two buttons on the banner: **Stop after this phase** lets the phase finish its
review, mark and commit, then ends the loop; **Stop now** ends the agent at once, after you confirm, and never commits, retries or finishes the build (a commit already begun finishes first). Stop after can be canceled by pressing it again. After a window reload the banner and both buttons come back, and Change project and Change agent are blocked while the loop runs.
Quitting the app ends the loop too, and the quit check says which phases are already committed.
**A question holds the loop.** When a phase needs an answer (with **Pause and wait for me**), the loop
waits with no time limit and nothing is lost. The app calls you back with the taskbar dot, a flash
of the window and the question sound, and carries on once you answer.
**When it stops by itself.** The loop ends on a stop screen, saying what failed and showing the
evidence, when:
- the phase's named tests or the quick check fail;
- Critical or Warning findings are left after the re-check, at a level the setup said to fix (a leftover Suggestion does not stop it);
- a task is blocked or the spec conflicts with itself;
- a commit is refused, for example by a pre-commit hook (the app puts the phase file back as it was, so the spec and git agree, and stops with the hook's first line; if the undo fails too, it says so and remembers it across a restart);
- a staged file looks like a secret (`.env` and the like; `.example`, `.sample` and `.template` are fine) or is oversized (nothing stays staged, and the stop line names the file);
- the project is on a detached HEAD (the loop will not start);
- the agent's report is missing task data or says its tests failed (the phase is refused);
- the watcher cannot read the session or hits an internal error (it ends on a stop screen, never a hang);
- the Smart pick skipped a Critical finding.
A crashed or silent agent gets exactly one retry per phase when the retry tick is on, and none when it is off.
It never retries a real failure. On a stop screen, **Ask a question** (first in the row, offered whenever Continue building is) wakes an ordinary agent on the stopped phase on the same page, so the Ask tab answers; it starts no loop and changes nothing, and **Continue building** is still there afterwards (pressing Ask again only opens the Ask tab). **Continue building** carries on unattended from the stopped
phase and **Fix together with an agent** opens an ordinary Implement session on it. The stop screen leads with a short reason, puts one line under each button saying what it does, and highlights one: Continue building after a crash, a silence or your own stop, Fix together after a failed check, a blocked task, a refused commit or a question. The phase list and uncommitted files sit under **Details**.