Resume from review

When a coding agent needs a decision - a design choice, a missing detail, or a finished PR awaiting your sign-off - it pauses in the review state instead of guessing. You reply, and it picks up exactly where it left off.

The flow

1. The task enters review (often with a PR already open).
2. Open the task detail page and read the agent's full terminal history to see what it did and what it is asking.
3. Choose Resume from the task's actions menu. The agent is woken on its still-running machine and the task goes back to running.
4. Type straight into the live terminal, or use the follow-up box under the conversation - either reaches the agent, which continues from the exact point it stopped, on the same machine, with its workspace intact.

If the machine was recycled

A task's machine is recycled after fifteen idle minutes, but its workspace - the checkout, installed packages and the CLI's own transcripts - is kept for 14 days. If you resume a task whose machine is gone, Foxl Code escalates to Reconnect: it re-invokes the same session on that saved workspace and the agent continues where it left off. Only when the workspace itself is gone does it say so and leave Retry to you - a retry is a new task on a fresh clone, and it spends, so it is never taken unasked. Reconnect is offered from review, failed and cancelled; a merged task is left alone, and a running one already has an agent attached. Codex cannot reattach to a session, so for a Codex task Retry is the route.

Reconnect

The pane discovers a sleeping session when you type: a strip over the terminal says so once and offers Reconnect, which resumes on the saved workspace - on the task page and on a Runtimes pane alike. A momentary failure to read the screen no longer counts as gone; the strip clears itself when the agent answers. If the workspace itself was cleared (a Foxl Code update, or 14 idle days), Reconnect rebuilds it from your pushed branch and says so in the pane, instead of offering only a paid Retry.

Steering without pausing

You don't have to wait for a review pause to interact. While an agent is running, the orchestrator (and the autonomous loop) can read its screen, send input, resize its terminal, and resume, retry or cancel it - see How it works. Review is simply the agent explicitly handing control back to you.

Fix it on a red build or a changes-requested PR in Work, and Request changes from the review pane, both resume the same agent on its saved workspace with the feedback, so it pushes to the branch it already opened.