Last verified: September 14, 2026
What You Can Now Do
Context Memo's page builder copilot now completes a full multi-section page inside a single generation instead of cutting off partway through. Ask for a hero, a three-column pricing section, and an FAQ block below it, and you get all three in one response rather than a hero, a table, and then silence. Two things changed on screen: the copilot streams output as it builds, so you can see what has landed, and when a request genuinely exceeds capacity you get an explicit error instead of a quietly saved partial draft. The practical decision this changes is prompt scope. You no longer need to split a page into four small requests and stitch the fragments together in the editor. Write the page you actually want, once.
Where It Is in Context Memo
This lives in the page builder copilot, the generative panel inside the visual editor you use to compose and lay out memos before publishing to your domain. There is no new menu item and no setting to enable. The behavior applies to the same copilot panel you already open from the editor, and it applies to every request you send from it.
How to Use It
- Open a memo in the page builder and open the copilot panel. You'll see the same prompt field, now with streaming output rather than a single blocking response.
- Describe the whole page in one request, naming each section in order and saying whether you want real copy or structural placeholders. Sections render top to bottom as the response streams, so you can confirm the layout is correct while it builds.
- Let the generation finish before you touch the canvas. Edits made mid-stream can collide with sections still being written.
- If the copilot returns a clean error, treat it as a capacity signal, not a comprehension problem. Re-send with fewer sections or drop the copy request and generate structure first. Sending the identical prompt again will hit the identical ceiling.
- When a long build returns partial output, keep it. Prompt only for the sections that are missing rather than regenerating the page from scratch, which wastes the output budget on work that already succeeded.
- Review the generated copy against your positioning before publishing. Generated section text is a draft, and memos that get cited are the ones where claims, proof, and comparisons are accurate.
Why We Built It
The failure users reported was not "the copilot got it wrong." It was "it stopped halfway and saved anyway." Three layers caused it: a fixed output token budget, a fixed request deadline tuned for short block edits, and an automatic retry that fired against the same constrained budget with partial context from the failed attempt. That retry was the worst part. It turned one clear failure into two truncated outputs, and left no way to tell whether the request had been misunderstood or had simply run out of room. The cost was a page that took three attempts and manual assembly, plus partial drafts sitting in the editor that nobody had approved.
Token capacity is now sized so a full multi-section page fits in one generation. Request deadlines are extended so a long build isn't killed by a timeout meant for a one-block edit. The truncating retry loop is gone, replaced by either an explicit error state or a streaming response that preserves everything already completed.
What It Does Not Do Yet
- No automatic resume. When a build returns partial output, the copilot keeps what finished but does not pick up where it left off. You prompt for the remaining sections yourself.
- Ceilings still exist. Capacity is higher, not unlimited. A request that asks for a dozen sections with full copy for each can still exceed the budget, which is why the error state exists. Splitting structure and copy into two passes is the reliable pattern for very long pages.
- Copy quality still needs review. Longer generations produce more text, and more text means more surface area for a claim that reads well but isn't yours.
- This is not a CMS. The page builder composes and publishes memos on your domain. It does not replace your marketing site platform or your CRM, and it isn't meant to.
If you were running multi-prompt workarounds to get a full page out of the copilot, retire them. Send the whole request and watch it stream.
