Grok Bot files and results: attach, inspect, keep evidence

A Bot that “finished” in chat has not finished. Ask for an artifact you can open, and keep the evidence next to it.

Attach sources on purpose

Use the attachment control or drag files into the composer. You can also paste images and links. Official documentation currently lists common inputs such as images, audio, video, PDF, plain text, Word, Excel, PowerPoint, CSV, JSON, YAML, source code, HTML, email, and Jupyter notebooks.

The desktop composer currently accepts up to six attachments at a time. Documents, images, and audio can be up to 25 MB each; videos up to 200 MB. Large, encrypted, damaged, or unusual files may not be readable.

Name the role of each file:

The PDF is the signed policy. The spreadsheet is this month’s transactions. Reconcile the spreadsheet against the policy, cite the policy section for every exception, and return a new spreadsheet plus a short summary. Do not modify the originals.

Links are not automatically in scope

Paste a link when the Bot can reach the page from its computer or a plugin. If the page is private, sign in through Agent Computer or install the relevant connector. Check the destination before entering credentials or approving an external action.

Ask for a reviewable result

Specify the artifact and what “good” means:

• A document with headings and source links
• A spreadsheet with defined columns
• A folder of screenshots and logs
• A draft message that has not been sent
• A short recommendation followed by evidence

For consequential work, require the Bot to separate:

1. Facts found in source systems
2. Assumptions or inferences
3. Actions already completed
4. Actions waiting for approval
5. Unresolved questions

Ask it to revise the existing artifact instead of spawning disconnected copies.

Shared computer files

Bots can read files other Bots save in /workspace. Use project folders and descriptive names. The conversation should still contain the final result or a clear path to it. Persistence and recovery are covered in Agent Computer.

Do not store secrets in /workspace “so the next Bot can use them.”

Preserve evidence

Depending on the task, ask for direct source links, screenshots of the relevant state, timestamps with timezones, input and output file names, a concise action log, and anything the Bot could not verify. A screenshot alone is weak for data that changes quickly; keep a link or export from the source system.

Sources and verification

Last verified: August 27, 2026.

• Files and results (xAI)
• Use the computer and apps (xAI)
• Approvals, security, and privacy (xAI)