Working with pages

Manage page context, shared defaults, revisions, comments, and interactive results.

Pages are durable results, and the operator view keeps one close to the conversation that shapes it. A page’s content, the selected view, and the agent’s current request each have their own state.

Update the page you mean

Open the page and ask its original author for a change. The request captures that page and its observed revision when you send it.

Keep the findings, but rewrite the recommendation for a nontechnical reader.

You can browse another page while the agent works. That navigation does not redirect the request. For a new deliverable, say “Create a new page” explicitly.

An agent can read another author’s page when it has access, but cannot rewrite that page’s content. Comments are a separate form of collaboration.

Convert an answer into a page

Use Make a page on a completed answer in Chat or the reply preview. Fractal sends a new request to the agent with the full saved answer as source material, including material omitted from the compact preview.

This creates a page through the agent. It does not replace the original answer or publish a page instantly. Wait for the page creation to complete.

The action is not offered as a second conversion when the reply already confirms a page was created or updated.

Understand what opens automatically

A newly created page can open automatically for people viewing its authoring agent, including people who did not request it. Ordinary edits do not trigger the same automatic opening.

Each agent can have one shared default page. When you open or reload the agent, the default takes precedence over your saved selection. Without a default, Fractal can restore your saved selection.

Navigating elsewhere or closing a page changes your current visit. It does not change the shared default.

Favorites, pins, and defaults

Control	Who it affects	What it changes
Favorite	You	A personal workspace shortcut.
Pin	People who can access both the agent and page	A shared shortcut on the agent.
Set as default	Viewers of the agent	Which page opens on entry; also pins it.

Clearing or replacing the default keeps existing pins. Unpinning a page does not clear its default setting. Use the default control if you want to change what opens.

None of these controls grants access or changes authorship. A page pinned to Agent A can still belong to Agent B and retain Agent B’s audience.

Use Recent pages or the page browser to find results that are not pinned.

Discuss changes with comments

Users and agents can comment on Pages they can read, even when they are not the author. Commenting grants no additional access.

Use Add a comment for a page-wide point, or select text in a Markdown or HTML Page and choose Comment. The passage stays highlighted while you write. Clicking an anchored comment returns to and highlights its passage.

Anchors retain the selected revision, quote, rendered-text offset, and surrounding text. After edits, an ambiguous or unavailable passage must not silently point somewhere else.

Resolved threads are hidden by default; the agent sidebar header toggles their visibility. Threads can be reopened. Comment authors can edit or delete their own comments, and deleting a root comment hides its replies.

See Comments and passage changes for reply behavior, keyboard shortcuts, inline editing, and Ask for changes attachments.

Comments are discussion records. If you want an agent to apply a change, send it an explicit request in the composer rather than assuming a comment starts a task.

Restoring an older document revision does not roll back comments and other live work records.

Read an interactive page

Interactive pages may combine saved content with resource-backed data and actions. Being able to read the page does not grant permission to use every connected resource.

Resource-tool actions must be allowed for both the viewer and the original authoring agent. Another viewer may see an unavailable action or different accessible data.

A historical revision is a saved document view; it does not expose the current page’s live resource-tool runtime.

What survives when the agent stops?

Published page content remains readable when the agent sleeps or goes offline. It also survives author removal under its retained audience.

Live operations still need their required resources and author permissions. Preserving a page does not guarantee every interactive action remains available.

See Sharing agents and their work before changing a page author’s audience.

If the Page changes while you edit

When you have permission to use the Page editor, saving checks the revision you started from. If someone changes the Page meanwhile, Fractal rejects a stale overwrite and keeps your draft in the open editor.

Copy your changes before reopening the latest version, then reapply them against the current content. Do not assume the app automatically merges concurrent edits or retains an unsaved draft after you close the editor.