Grok Bot Pages: reports and dashboards your Bot builds and keeps current

A Grok Bot Page is a finished, styled document — a report, memo, dashboard or tracker — that a Bot builds inside your chat and keeps editing when you ask. It starts private, can be shared at four levels, and can be refreshed by a routine so one link always shows current data. Pages shipped in the 0.75.2 changelog entry on October 22, 2026.

At a glance#

We have not built or shared a Page ourselves. Facts below come from Cursor's Pages help, the docs.x.ai files and results page, and the changelog through 0.78.1 (October 27).

How a Page gets made#

You never open an editor. You describe the Page in chat and the Bot produces it as a card with a title and an Open button.

1. Ask with purpose, sources and sections#

Say who the Page is for, what it should draw from, and which sections you expect. The official examples include a comparison of three quotes from an email thread with a table and short recommendation, a weekly support-ticket summary by topic, a 30-day signups-trials-conversions dashboard, and a launch tracker of tasks, owners and statuses.

2. Open the card#

On desktop, the Page fills the window and the chat shrinks into a side panel. On the phone, tapping the card opens it in the app. Since 0.75.2, a Page can capture the pointer and go full screen, keyboard shortcuts still work, and Back closes the Page while staying on that Bot.

3. Request changes in the side panel#

Ask for corrections in the panel beside the Page, not a fresh chat, so the Bot edits the same object. The earlier chat card then shows Updated. Since 0.78.1, the Bot applies several edits in one pass and leaves the Page untouched if any edit fails to fit, and diagram labels wrap instead of clipping.

4. Know what the controls do#

Filters and switches change only what you see. Nothing you click on a Page is saved, and viewers cannot alter content.

Finding Pages later#

Click the Bot's name at the top of the chat, then choose the Library tab. It lists the Pages, files and apps that Bot produced, and marks any Page shared with your team or by link.

Each row's More actions menu offers Open, Share… and Pin. Pinned items (since 0.75.2) sit in a Pinned section at the top and sync across devices. Hovering a row previews who sent the item, when, and who can see it — the fastest visibility check before you paste a link anywhere.

On teams, 0.77.0 shows Pages shared with the team under Shared with your team in a Shared Bot's Library, and 0.78.1 lists a team Page under every Bot that published it. See our Shared Bots guide for the admin side.

Sharing levels compared#

Open the Page and click Share, or pick Share… from its Library row. Choose an audience, then Copy link. Since 0.75.2, the Share menu displays current visibility. Viewers can read and use controls; only the Bot edits.

The public link is the risky one#

A public Page gets a pages.grok.bot address derived from its title. Renaming the Page later does not change the address, and custom addresses aren't available yet. If a routine keeps that Page current, whatever the Bot adds next is public too.

Error messages you might see#

The share menu explains blocked options: Public sharing is off for Enterprise teams, Pages in your personal space can't be team-shared, Couldn't update access (retry), or This page's access changed (someone else edited access while your menu was open). Team admins can also restrict who may share Pages with the whole team.

Unsharing and deleting#

To shrink the audience, reopen Share and pick a narrower option. Cursor's help says every shared Page also appears under Grok Bot Pages in Shared Canvases on your Cursor dashboard, where you can change access or delete; the changelog calls this the dashboard's Pages section.

Since 0.77.0 (October 26), an owner can delete a Page straight from the Library. That removes it for every person it was shared with, and link holders lose access. Neither source describes version history, restore, size limits or an export format, so assume a delete is final.

Pages on a schedule#

The docs say Bots can create or update Pages on routines. That turns a Page into a fixed address for anything you'd otherwise get as a new file each week. Every run spends usage, as our skills vs routines guide explains.

Ideas that fit the pattern (ours, untested):

• A Monday project status memo rebuilt from trackers and pull requests the Bot can read.
• A morning support or sales dashboard from a connected app, with the data's date range printed at the top.
• A vendor-quote comparison that updates when a new quote hits the Bot's inbox.
• A research brief that grows as the Bot finds sources, each linked.

More recurring setups are in our use cases guide.

Copy-paste brief for a living Page#

Create a Page titled "[Page title]" for [audience].

Pull only from: [named apps, files or URLs].

Sections: [list sections, tables or charts].

At the top, print the date, time and time zone the data was read.

Cite a source next to every number. If a source is missing or empty, say so on the Page instead of reusing old figures.

Keep the Page private. Do not share it.

Then propose a routine that refreshes this same Page every [schedule] and list what each run will read.

Do not create the routine until I approve.

For the general structure behind briefs like this, see how to write a workflow brief.

Pre-share checklist#

• You read the whole Page and spot-checked numbers against the cited sources.
• The title works as a public URL slug (it becomes part of a pages.grok.bot address).
• Nothing on it comes from a connected app the audience shouldn't see. Viewers see what the Bot placed there, not what their own access allows.
• You chose the narrowest sharing level that does the job.
• If a routine updates it, you know what future runs will add.

Open questions in the sources#

Enterprise is the main conflict: Cursor's help says Pages is not yet on Enterprise teams, while the docs describe Enterprise users sharing with users, groups or teams. Version requirements also differ — Cursor cites 0.60.0 desktop and 1.14.0 mobile, while the changelog lists Pages as new on October 22 — so a gradual rollout may decide when you see the feature. For the wider risk picture, read Is Grok Bot safe?.

Our take#

Pages are the best answer yet to "send me this report every week": one link, always current, with edits handled in the side panel. Keep them private or team-only by default and treat anyone-with-the-link as publishing. Pair a Page with a routine only after one manual version is accurate, and print the data timestamp on every Page so stale numbers can't pass as fresh.

Frequently asked questions#

What is a Page in Grok Bot?#

A Page is something a Bot builds for you to read: a report, memo, dashboard, tracker or explainer. Cursor's help says it can contain text, tables, charts and controls such as filters and switches, and the docs.x.ai files page adds heat maps and flow charts. Pages live in the Bot's Library and arrived in the 0.75.2 changelog entry of October 22, 2026.

Can I edit a Grok Bot Page by hand?#

Only the title. You change content by asking the Bot in the chat panel that sits beside the open Page, and the Bot edits that same Page so everyone with access sees the update. Filters and switches only change your own view and are never saved. Click the title of a Page you made to rename it.

Is a public Grok Bot Page visible to anyone?#

Yes. A Page shared with anyone who has the link gets its own address on pages.grok.bot, generated from its title, and opens without a sign-in. The address does not change if you rename the Page and you cannot pick a custom one. Public sharing is off on Enterprise teams. Treat a public Page like a published document.

How do I delete or unshare a Grok Bot Page?#

Open Share and choose a narrower audience, or go to your Cursor dashboard, where shared Pages are listed and can be unshared or deleted. Since 0.77.0 on October 26, a Page owner can also delete it from the Library, which removes it for everyone it was shared with. Anyone holding the link loses access after deletion.

Can a routine keep a Grok Bot Page updated automatically?#

The docs say you can ask Bots to create or update Pages on routines. When the Bot updates a Page, the older card in chat shows Updated and opens the latest version. Each routine run spends weekly usage like any other run, so match the schedule to how often the data actually changes.

Are Grok Bot Pages available on Enterprise?#