Build a Guide from an Agent plan

Build this guide sends a selected Agent response and chosen supporting messages to Codex mode for implementation in the open Guide.

Use it after discussing a plan in the Guide editor's ordinary Agent chat. You need cloud authoring access, and the ordinary response must have finished before its build action is available.

Review and start the build

1. In the Guide editor's Agent, discuss the changes you want. Ask it to wait before editing if you want planning only.
2. Under the assistant response you want to use, select Build this guide.
3. Check Editor target, including the Guide and any named sequence, page, or block.
4. Edit Selected plan to say exactly what should be implemented.
5. Expand Supporting messages and deselect discussion that should not be carried forward.
6. Add relevant files if needed, then select Build this guide in the review.
7. Follow progress in Codex mode and inspect the accepted Guide.

Opening the review does not start the build. Cancel leaves the review without submitting a new build request.

The target is captured when you choose the response. Moving to another page does not silently replace that target. If the captured target is wrong, cancel and select the plan again from the intended context.

Choose useful context

The selected assistant response becomes the editable plan. Earlier chat messages are offered as supporting discussion and start selected; later messages are not included. Private tool output is not copied as supporting chat text.

Attach files again in this review if the build needs them. Do not assume an earlier chat attachment was included merely because its discussion was selected. See files and images.

The complete plan, selected discussion, and target description must fit within 32,000 characters. If the review reports that it is too long, shorten the plan or deselect messages. You can attach up to ten files, each containing 1–50,000,000 bytes.

If submission is interrupted

The review saves unfinished visual-editor drafts before starting the handoff. If that save fails, resolve it before continuing.

After submission begins, the plan and file selection are locked for that attempt. Use its Retry action after a connection or upload problem. It reuses the attempt and successful uploads instead of creating a fresh build request.

A lost reply does not prove that nothing started. Check Codex history and the Guide before submitting another plan. If you leave the review after an uncertain attempt, follow unconfirmed-request recovery. Canceling the review after work has been accepted does not stop that work; use Stop work in the cloud conversation.