Use cases
Real jobs an AI assistant does well in AR Clip, and what in the platform makes each one work. Use them as ideas for what to ask.
Work together in one scene
Everyone in a space works in the same live scene. An assistant connected over MCP is just one more person in it. Its changes show up in your editor as it makes them, and go into the edit history like everyone else's.
This makes a workshop easy: a room full of people, one scene, and an assistant doing the typing.
| You say | It does |
|---|---|
| "Put a table here and four chairs around it" | builds it while everyone watches |
| "Make the chairs the same blue as the logo" | finds the colour and applies it to all four chairs |
| "Undo the last three things" | undoes them one by one in your open editor — you can also undo them yourself |
You see each change as it lands, and can say "no, smaller" right away. The assistant can undo only while the project is open in an editor tab.
Run the session
Plugins have a project room: shared data that everyone in the project sees. It keeps one clock for everyone and records who wrote what. The room is for the meeting, not the project: nothing in it is published, and it cannot be undone.
The example plugins that come with AR Clip use it to run a session:
| Example plugin | What it does |
|---|---|
| Session timer | a countdown everyone sees on top of the viewport |
| Session voting | polls with one vote per person — the room records who wrote each vote |
An assistant can use them just like a person. It can start a timed round, open a vote between two options, read the result, and carry on building with the winner.
Two laptops' clocks can differ by minutes, but the countdown does not depend on them. "4:12 left" means the same for everyone in the room.
Build a game with you
You decide how it should feel. The assistant puts it together.
| The assistant is good at | You stay in charge of |
|---|---|
| setting up the scene and adding the objects | how it should look |
| adding the same event to twenty objects | whether the idea is fun |
| writing the script you would rather not write | difficulty and pacing |
| turning an event into a patch when it gets too complex | when to stop adding things |
Events, patches and scripts react to the same taps, keys and collisions. So an assistant can start simple and grow the logic where it is: a tap event today, a patch with a condition tomorrow, and a script when it needs real logic. Nothing has to be rebuilt.
Turn a brief into an AR scene
"A poster that shows the product spinning above it when you point a phone at it" is enough to build from. It means a scene, an image anchor with the printed size, a model and a rotation.
An assistant can set all of that up. What it cannot judge is what you should check anyway: whether the artwork tracks well, and whether the size looks right in the room.
Turn Figma designs into AR
With your Figma account connected, a Figma frame becomes a 3D layout or an interface card, with its sizes, colours and text kept. An assistant can take the link, import the frame, and connect the buttons to scene steps — the tedious part of making a design do something.
See Figma and Sketchfab.
Do the repetitive work
This is where an assistant saves you the most time:
- build forty objects from a list and lay them out on a grid;
- rename everything the same way, so scripts can find things;
- point every material at a new texture after the artwork changes;
- make a scene for each product in a catalogue;
- make the same experience in five languages.
Check a project before you publish
AR Clip comes with debugging plugins that look for problems that are easy to miss. An assistant can run the same checks:
| Check | What it finds |
|---|---|
| Scene doctor | objects outside the scene, broken parents, loops in the hierarchy, zero scale, NaN (invalid numbers) in a transform, links to deleted resources |
| Resource usage | where each resource is used, and which ones are not used at all |
| World inspector | the full object tree and the actual values in each component |
An assistant can also spot everyday mistakes by reading the scene:
- a model that should be solid but has no collider;
- a trigger handled both in an event and in a script;
- a state left selected;
- an animation driven by two methods at once.
Help a newcomer
A model that has read the brief can answer "how do I make this button open the next scene" with the real panel names and the real step. That is often faster than searching the docs.
Build multiplayer experiences
The player has rooms, shared state and synced physics. An assistant can set up the basics: who owns what, what is shared between players, and how other players are shown. People get this part wrong most often.
See Multiplayer.
Build projects from data
Plugins can create scenes and spaces with the editor's own functions, and tag what they made so they can find it again. So an assistant can turn a spreadsheet of products, a folder of photos or a list of locations into a finished project — and update it when the data changes.
The photo revival example plugin does something like this: it pairs images by file name and builds AR scenes from them.
What you still decide
Some things an assistant cannot judge for you:
- whether it works in the real place — lighting, marker size, how far away people stand;
- whether it is fun — no model can tell you the puzzle is boring;
- what to cut — assistants tend to add, not remove;
- anything with consequences — publishing, spending, sharing.
Next: Skills — the guides the built-in assistant reads.