Recover cloud Guide authoring

Use the existing Codex conversation's status and accepted Guide to determine what still needs attention.

Inspect synchronization

1. Open the Guide's Agent in Codex mode and select the relevant history entry.
2. Expand its Guide synchronization section.
3. Read pending files, diagnostics, conflicts, and media status.
4. For a conflict, compare Current Guide value with Proposed value.
5. Choose Keep current or Use proposed when the choice is clear.
6. Verify the resulting Guide and test it in Preview.

Guide files are synchronized means no currently reported pending work. Guide changes are pending can indicate validation, media, or network work. Guide changes need attention calls for inspecting the listed problems.

A conflict choice applies to the reviewed file group. Keep current uses the accepted Guide version; Use proposed selects the competing proposal while retaining independent changes and validating the result. It cannot force invalid content to be accepted.

The panel shows bounded comparisons; long values can end with an ellipsis. If the information is insufficient, inspect the Guide or ask the agent to explain the full proposed change before choosing. If the content changed during review, re-read the refreshed conflict.

For a source diagnostic or failed media import without a repair button, describe the displayed problem in the conversation and request a correction. A successful chat response alone does not clear pending Guide changes.

Reconnect without duplicating work

Reconnecting means observation is interrupted; it does not mean the cloud job stopped. Restore connectivity and use Retry.

A request is not yet confirmed means the browser does not yet know whether it was accepted. Retry checks the original request. History can also reconcile a lost reply. Resolve this state before starting another chat or sending the same work again.

If a worker stopped before confirming delivery to the agent, the conversation can instead say the request was not confirmed and needs review. Check both the accepted Guide and history before deliberately requesting further work.

Return after an interruption

Reopen the same Guide and cloud history. Accepted edits and conversation history remain on the server. Unsaved composer text depends on browser-session storage and is not guaranteed across devices or storage clearing.

Recovering conversation can occur while cloud execution resumes. Waiting for your answer needs the question response, not repeated prompts. Work stopped with an error requires reading the failure and checking accepted changes before continuing.

Leaving the editor does not stop work. Use Stop work when that is your intent.

Resolve access or ownership changes

Guide edit permission and workspace capabilities are checked again during work. Losing them can stop authoring without removing previously accepted changes.

If the Guide moved to another workspace, open a new authoring conversation there. Old conversation history is scoped to its original workspace. Attachments can also depend on the prior folder.

Restore the required access or credit eligibility, then inspect the current Guide before issuing another request.