# Control the Studio from an agent

URL: https://docs.glossi.io/agents/studio

Ask Claude, ChatGPT or Cursor to place props, move the camera, light the scene and save shots in the Studio, and watch it happen live or let it work in the cloud.

Ask your agent for scene changes in plain language. With the project open in the Studio, you watch every change land in the viewport. Without it, the agent can open the project in a cloud Studio and work there.

> Add a small potted plant just behind the shoe, then add some film grain and a soft vignette.

> Move the camera round to the left side and a bit lower, and save it as a new shot called "Side low".

> Make the laces black.

This uses the same [Glossi connector](https://docs.glossi.io/agents/connect.md) as everything else your agent does. The tools are listed under Studio sessions and Studio scene in the [tool reference](https://docs.glossi.io/agents/tools.md#studio-sessions).

> **Enterprise.** Agent access is available on Enterprise.

## Work in the Studio you have open

1. [Connect your agent to Glossi](https://docs.glossi.io/agents/connect.md).
2. Open the project in the Studio and wait for it to finish loading.
3. Ask your agent for a change. With one Studio open, it uses that one; you don't need to name the project.

Keep the Studio tab open while the agent works. Closing it ends the agent's access to that Studio. You can keep using the Studio yourself at the same time.

While the agent is working, an **Agent** chip at the top of the viewport names what it is doing, for example "Agent · Place props", and how many changes are queued. It clears a moment after the agent stops.

Say "this" or "the selected one" and the agent checks what you have selected in the Studio first.

## Work in a cloud Studio

When you want the work done without opening the project yourself, ask the agent to do it in the cloud. It opens the project in a Studio running in the cloud (`open_studio_session`), makes the changes, and saves and closes it when it is done.

* **Starting takes 5 to 15 minutes.** The agent tells you each progress step as it happens.
* **It uses Studio time** while it runs, the same as a Studio you have open. A session left idle for 10 minutes saves and closes itself.
* **One per workspace.** A second cloud session is refused until the first is closed.
* **Opening the project yourself takes over.** If you open the project in the Studio while a cloud session has it, the cloud session saves and closes, and the agent carries on in your Studio.

## What the agent can do

| Area                  | Examples                                                                                                                                                                                                                                                                        |
| --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Look at the scene** | Read what's in the scene and where it sits, see what you have selected, and take a picture of the viewport to check its own work                                                                                                                                                |
| **Props**             | Search the prop catalog, add props around the product, move, turn and scale them, change their materials, remove them, and save a set of props as a layout to reuse                                                                                                             |
| **Camera and shots**  | Orbit, raise, pull back or frame a part; add, edit, select and delete shots and aim them at camera targets; pose the product for one shot only; leave a product out of one shot; change the frame to square, vertical or widescreen                                             |
| **Clips**             | Add, edit and delete clips, start a clip from a shot, leave a product out of one clip, animate the camera, the product or the lights, tune a generated animation, and check a clip's motion as a few frames                                                                     |
| **Product**           | Add or remove another product, switch, save, rename and delete variants, change a part's material and surface, show or hide parts, place and edit decals, turn fur on and tune it, stand a model upright for every project, and save what a part wears to your material library |
| **Look**              | Light the scene from a description or a photo, choose a lighting preset, switch or turn the HDRI, change the backdrop, and adjust post processing such as film grain, vignette, bloom and exposure                                                                              |
| **Template**          | Replace the scene with a template's backdrop, lighting, shots, clips and props, keeping the products                                                                                                                                                                            |
| **Ask the Assistant** | Hand one instruction to the Studio's own Assistant and let it make the change                                                                                                                                                                                                   |
| **Save and render**   | Save the project, or render it as the Studio has it now                                                                                                                                                                                                                         |

## Usage

Changing the scene with the `studio_` tools uses nothing extra beyond Studio time. Handing an instruction to the Assistant (`studio_prompt`) uses usage the same as a prompt in the Studio's own panel, and so do the tools that generate from a description: `studio_animate_product`, `studio_append_product_animation`, `studio_animate_camera` and `studio_adjust_lighting`. A call that fails is not charged. A result with `refused: true` still is, because the model ran. Renders use usage as they always do.

## How changes run

* **Live.** Every change is made in the Studio, the same as if you had used the panels, and saves with the project as usual.
* **Removing things asks first.** Removing a prop, shot, clip, decal, variant, product or prop layout, applying a template or prop layout, and overwriting a library material are destructive, so the agent asks you before it does them. Undo brings back a deleted shot if nothing else has changed since. Removed props, products and decals, deleted variants and prop layouts, and an applied template or layout don't come back with Undo. Deleting a variant also removes it from the model in your library, and the original variant can't be deleted.
* **Several changes at once.** The agent can send up to 25 changes in one `studio_batch`. They run in order and each is its own Undo step. When the agent waits for the batch, a failure cancels the changes after it. A batch that removes anything still needs your yes.
* **Sending without waiting.** The agent can send a change with `wait: false` and carry on, then collect results with `wait_for_studio_calls` before it looks again. Changes still run in the order sent, but a failed one doesn't stop the ones after it.
* **Looking before and after.** The agent reads the scene before moving things, and captures the viewport afterwards to check the change landed as you asked.

## Undo and history

The agent gives each change or batch a short label, such as "Warmer key light". `list_studio_history` lists recent changes with who made them (you, the Assistant or an agent) and what they touched.

Ask your agent to undo something it or the Assistant did earlier ("undo the backdrop change from before") and it finds the change in the history and reverts it with `undo_studio_group`, even if other changes came after. When more than one change could be the one you mean, it asks which. If a later change touched the same part of the scene, nothing is undone and the agent tells you which change is in the way. The undo is its own step, so Ctrl+Z brings the change back. An earlier change can only be undone in the Studio that made it, while it is still open.

`studio_undo` steps back the Studio's shared history one change at a time, like the Studio's own button. In a Studio you have open that can be your own last change, so the agent says what it undid.

## Troubleshooting

**"No Studio is open."** Open the project in the Studio, wait for it to load, and ask again. Or ask the agent to work on it in a cloud Studio.

**"Your open Studio isn't connected to agents yet."** Close the Studio, open the project again, and retry. If it keeps happening, contact [support@glossi.io](mailto:support@glossi.io).

**"This workspace already has a cloud Studio session open."** Ask the agent to close the other session first, or open the project in the Studio yourself.

**"The studio lost this call before reporting a result."** The Studio restarted or reconnected while a change was running. It may or may not have landed, so the agent should look at the scene before trying again.

**"The studio call arrived too late to run in order."** The change did not run, so the agent can send it again.

**A change failed because the session ended.** The Studio was closed while changes were waiting or running. Waiting ones did not run; a running one may have landed. Reopen the project, check the scene, and ask again.

**The agent changed the wrong thing.** Tell it what you meant, or fix it in the Studio. Naming the prop or shot helps, and so does selecting it in the Studio first.

## Related

* [Connect an AI agent](https://docs.glossi.io/agents/connect.md)
* [Agent tool reference](https://docs.glossi.io/agents/tools.md)
* [Studio tour](https://docs.glossi.io/studio/tour.md)