Guide
Grok Bot files, Pages, and results: attachments, the Library, and sharing
By Atlas AI Resources · Published November 12, 2026
Most Grok Bot work starts with a file and ends with one: a spreadsheet to reconcile, a report to review, a page to share. This page starts with our own advice on getting results you can actually check, then summarizes what SpaceXSI’s docs page Files and results says about attachments, moving files to your apps, the Library, and Pages.
1. Our advice: ask for the artifact, not an answer
Sections 1 and 2 are our own advice, not SpaceXSI’s.
- Name the format and the finish line. “A CSV with these five columns” or “a one-page memo with a source link on every claim” is easier to check than “look into this.”
- Say what each attachment is. One line per file (“the PDF is the policy, the sheet is this month’s data”) saves a wrong guess and a second run.
- Protect the originals. Add “don’t modify the originals” whenever you attach something you care about.
- Revise in place. Ask the Bot to update the file or Page it just made instead of starting a new one, so you don’t end up with five near-copies.
2. Our advice: files between Bots
If you run a small fleet, give each Bot its own folder in /workspace and pass work by file path with a short note. Keep the final result in the conversation too, so you never have to dig through folders to find what a Bot finished. Treat a file another Bot or a website wrote as material to check, not instructions to follow (see keeping AI agents safe from prompt injection).
3. Per the docs: attaching files
Per Files and results, you can use the attachment control, drag files into the composer, or paste images and links. Supported inputs include images, audio, video, PDFs, plain text, Word, Excel, PowerPoint, CSV, JSON, YAML, source code, HTML and email files, and Jupyter notebooks.
Desktop app limits:
- 20 attachments per message.
- Images: 25 MB each, 200 MB total per message.
- Documents, audio, and other files: 250 MB each.
- Video: 1 GB each.
A file over its limit is left out, and the composer says so; send it in another message. Large, encrypted, damaged, or unusual files may not be readable, so export them as PDF, CSV, plain text, or an image. On a phone, you can also send a photo, file, link, or text from another app through the system share sheet. See the Grok Bot mobile app guide.
4. Per the docs: links and private pages
Paste a link when the Bot can reach the page from its computer or a connected app. For a private page, sign in through the Bot’s computer or connect the app. Links in messages open in your system browser, and hovering a link card shows a preview. The docs advise checking the destination before entering credentials or approving an outside action. For logins, see Grok Bot Vault.
5. Per the docs: moving files to and from your apps
With Google Drive, OneDrive, SharePoint, Gmail, or Outlook connected, a Bot can move files without pasting their contents into chat. It can save a file to Drive, OneDrive, or SharePoint, or attach it to a Gmail or Outlook draft. It can also bring a cloud file or an email attachment onto its computer. Google Docs, Sheets, Slides, and Drawings arrive as .docx, .xlsx, .pptx, and .png files.
- Saving to Google Drive always creates a new file, even when one with the same name exists.
- OneDrive and SharePoint refuse a name that already exists unless you tell the Bot to overwrite it.
6. Per the docs: asking for a reviewable result
The docs suggest naming the artifact and its acceptance criteria: a document with headings and source links, a spreadsheet with defined columns and formulas, a deck with speaker notes, a folder of screenshots and logs, an unsent draft message, or a short recommendation followed by the evidence. For consequential work, ask the Bot to keep five things apart:
- Facts found in source systems
- Assumptions or inferences
- Actions already completed
- Actions waiting for approval
- Unresolved questions
To keep evidence, ask for direct source links, screenshots showing the relevant state, timestamps with time zones, input and output file names, a short action log, and a list of anything the Bot couldn’t verify. For fast-changing data, keep a link or export from the source system rather than a screenshot alone.
7. Per the docs: images and video clips
A Bot makes pictures and short clips only when you ask. Images come in 1:1, 4:3, 3:4, 16:9, or 9:16; image creation isn’t used for charts or tables, so ask for a Page instead. Clips run 1 to 15 seconds (6 by default), are 480p unless you ask for 720p, and are saved as MP4. A clip can start from a description, one image as the first frame, two images for start and end, or up to 14 reference images. The docs say videos look filmed and aren’t made for motion graphics, title cards, slideshows, demos, or anything needing exact text or brand assets.
8. Per the docs: the Library
Click the Bot’s name at the top of the chat and open the Library tab (on the phone, tap the Bot’s name, then Library). It lists the Pages, files, and apps the Bot made and the images, videos, and links it sent, newest first. Things you sent and files a Cloud Agent returned aren’t listed. You can pin items to keep them at the top, and on desktop you can filter by Pages, Media, Links, Files, Apps, or Pinned. In the desktop app, Cmd/Ctrl+K also finds a Page by title.
9. Per the docs: Pages
A Page is something a Bot builds for you to read: a report, memo, dashboard, tracker, or explainer, with text, tables, charts, and controls like filters. Ask for one in chat, or have a routine create or update it. Pages are rolling out gradually, aren’t on Enterprise teams yet, and need Grok Bot 0.60.0 or later on desktop and 1.14.0 or later on the phone.
- Changing a Page. Ask the Bot in the chat panel beside the open Page. Filters and switches only change your view; nothing you do on the Page is saved.
- Sharing. A new Page is private until you share it. Options are people you invite (Only you on a personal account), your team, or anyone with the link. Everyone you share with can read it and use its controls; only the Bot can change it.
- Public links. “Anyone with the link” gives the Page its own address on
pages.grok.bot, based on its title, and nobody needs to sign in. Share that way only when the Page holds nothing private. Public sharing is off on Enterprise teams. - Managing shared Pages. The Cursor dashboard lists your shared Grok Bot Pages with their visibility and date. Deleting a Page there cuts off everyone with the link.
10. Per the docs: results from Cloud Agents
When a Bot hands coding work to a Cloud Agent, it copies the images, videos, and files cited in the agent’s final report to its computer and attaches them to its reply. The agent’s card shows the same files, and on the phone it also offers View PR when the run opened a pull request and hasn’t expired. More on that setup in the Cursor Cloud Agents guide.
Sources
Attachment limits, moving files to your apps, images and video, the Library, Pages, and sharing.
How the shared computer and its files persist, linked from the Files and results page.
Related: Grok Bot mobile app · Small AI fleets: handoffs · Grok Bot troubleshooting · Grok Bot shared Bots · Complete Grok Bot setup guide · Grok Bot computer and apps · Grok Bot in meetings