What Grok Bot Is and What It Shares

Grok Bot is an agent app made by SpaceXSI (the company formerly called xAI), built with Cursor. It launched in beta on 11 August 2026. Inside it you create Bots: named, persistent AI agents that work for you over days and weeks, not just for one chat.

You work with a Bot the way you'd brief a production coordinator. You message it by typing, dictating or voice chat, give it a job and the sources it needs, and it works through the steps, reports progress and asks when it needs a decision. Before a risky action, such as sending an email or deleting a file, it pauses and shows you an approval card. Nothing in that action happens until you allow it.

Example: you message a Bot called Script Desk: "When new pages land in the Revisions folder, list which scenes changed and draft a summary for me. Don't send anything." It reads, compares and drafts. If it wants to email the summary to the department heads, it stops and asks you first.

The approval settings that make this pause dependable come in a later lesson. For now, remember the basic deal: the Bot does the work and you approve anything risky.

Every Bot needs somewhere to work. Grok Bot gives each user one cloud computer: a computer in a data centre (the official docs say these run in the United States) with:

• a browser for websites
• a shared folder called /workspace for files
• a terminal for running commands
• every login your Bots have used

Because it's in the cloud, it keeps running when your laptop is closed. A routine can check the Revisions folder at 6 a.m. while you're still asleep.

The key detail: all your Bots share this one computer. Each Bot gets its own screen, so you can watch what one Bot is doing, but the files, browser sessions and logins underneath belong to every Bot on your account. Other users can't reach your computer, but your Bots can all reach each other's things.

Example: your Script Desk Bot saves Sc42_blue_pages.pdf into /workspace. Your Post Notes Bot, on the same account, can open that file too, and it can use the Gmail login Script Desk signed into.

A security boundary is a wall that stops one thing reaching another. Separate Bots on one account are not one. The official docs say so directly: screens are not security boundaries, and Bots on one account can't be isolated from each other.

For a production this matters. Suppose you run two shows from one account: Farmhouse (your feature) and a commercial job. You make a Bot for each and think they're walled off. They aren't. The commercial Bot can open Farmhouse's unreleased script in /workspace and use the Drive login that holds your crew list.

So why keep separate Bots at all? Because a Bot with one job, one set of sources and its own memory makes fewer mistakes. That's about focus, not protection. Protection comes from other choices you'll make in setup:

• connect only the apps and logins a job needs
• keep personal and production accounts on separate Grok Bot accounts
• remove sensitive files from /workspace and sign out when a job ends

Use practice files in this course, not real scripts or crew lists, until your production has said yes.

A Bot reaches your work in two ways:

• Connected apps. Where a connector exists (for example Gmail, Google Drive, Sheets, Docs or Slack), the Bot uses it directly.
• Computer use. Where there's no connector, it clicks through the website in its browser, as you would.

It also keeps a memory: your preferences, facts you've told it, summaries and a dated work log. A few basics, such as your name and time zone, are shared across your personal Bots. Memory is not a source of truth. If the Bot "remembers" that the blue pages are current, it may be out of date. Before anything that matters, ask it to reopen the live file.

Two more pieces turn a one-off task into standing work:

• A skill is a saved, reusable procedure, such as "how we log a script revision."
• A routine runs a skill on a schedule ("every weekday at 8:00 AM") or when something happens, such as a Slack message, an email to the Bot's own address, or a webhook.

Example: the skill Log revision runs as a routine every time an email lands with new pages.

A script change travels through the breakdown, schedule, call sheets, shot tests and the edit. Keeping all of that current is the work a Bot can carry: logging revisions, updating affected breakdown entries, keeping a register of shot tests, tracking post notes and clearances.

What a Bot must not carry is the call: which draft is the baseline, whether a new prop becomes a requirement, what a reshoot costs, whether a shot is safe, and what goes into the picture. Those belong to the director, the producer or the right department lead.

Ben Affleck, Oscar winner and founder of the AI tools company InterPositive, says AI will fill in the parts of production that are "expensive and burdensome", and that it will always rest on human artistry. Richard Chuang, co-founder of Pacific Data Images, built the pipeline behind Shrek. A big studio asked him for a pipeline that would update its script, breakdown and content on its own. He called his own sketch rough and warned against taking such a pipeline for granted.

So the test for any task is simple: can a Bot do it, then stop where a person has to decide?

Every bot in this course works on one practice scene, so you can see each change move through the paperwork.

Scene 42. Night. Nora stands on a farmhouse porch and tells her brother she's selling the house. In take six, she gives an unplanned look back at the house. Nobody scripted it. It happened once, between two actors, in front of a lens. It's the one thing the scene can't lose, and it belongs to the actor.

The scene also has gaps, as real ones do. The rain was cut from the budget, and the wide that should give the brother's answer room is still a placeholder in the timeline.

In later lessons, revisions will arrive (including a duplicate and an older draft with a newer date), a new prop will appear, shot tests will come back and notes will pile up. Your Bots will log, compare and draft. At each decision point they'll stop and hand the call to the right person. The course's name for this habit is calling the cut: let the Bot carry the paperwork, and keep the call on what goes into the picture with people.

Use sample pages for scene 42, not a real unreleased script.