> ## Documentation Index
> Fetch the complete documentation index at: https://docs.summerengine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Approve what your AI agent asks: publishing and approval links

> How Summer approval links work: when your AI agent must ask first, how it asks before your game goes live on Summer Games, and what each approval state means.

Your agent asks you first in three cases:

* a switch in **Studio > Settings > [Agent permissions](https://docs.summerengine.com/mcp/permissions.md)** is off;
* the change always asks: agent permissions, auto top-up, entering a jam, the analytics event limit;
* Summer Games still asks: for now, you approve price, A/B test and member changes.

Your agent gives you a link. Nothing changes until you approve.

## Approve a request

**1. Open the link**

Your agent gives you a link like `https://www.summerengine.com/studio/approvals/<id>`. If you have Studio open in a tab, the same request shows there as a card.

**2. Check what will change**

The request says what your agent wants to do, with each value before and after.

**3. Approve, or turn it down**

Approve it, and the change happens. Turn it down, and nothing changes.

A request for your own yes expires after 24 hours. A request for a game owner's yes expires after 7 days. **Studio > Settings > Agent activity** lists every request and every change, with Undo for prices, sales, country prices, member roles, team names and the event limit.

## Approve going live

Your agent always asks you before a game goes live. It shows you the plan, the page and the build, and asks in the chat. Only after your yes does it take the game live with `summer_go_live`. The game is live as soon as Summer's automatic checks pass. There is no review to wait for.

When **Publish** is off for agents on your account, your agent can't take the game live. Publish it yourself in Studio.

![The agent asks. The request waits for you on the approval page with exactly what changes. You approve it, Summer's automatic checks run, then it is live. Not now cancels it and publishes nothing. If the page changes after the agent asked, the request is stale and the agent asks again.](https://mintcdn.com/summer-18f03259/u2XgseMDTiPPbFru/images/guide-art/publishing/approval-light.svg?fit=max\&auto=format\&n=u2XgseMDTiPPbFru\&q=85\&s=27e2ec94bfe426fea0eb935e0172a9d5)

## When you publish yourself

If you click **Publish** in Studio yourself, that is your yes. There is no extra step: the game goes live as soon as the automatic checks pass. See [Publish your game](https://docs.summerengine.com/build/publish.md).

## What the states mean

| State | Your agent sees | Meaning | What to do |
| - | - | - | - |
| **Awaiting owner approval** | `awaiting_approval` | Your agent asked. Nothing is published. | Open the link. |
| **Approved** | `done` | You approved it, and the change ran. | Nothing. |
| **Cancelled** | `cancelled` | You clicked **Not now**, or your agent withdrew it. | Ask your agent again when ready. |
| **Stale** | `stale` | The store page changed after your agent asked. | Ask your agent again, so you approve exactly what will change. |

## What your agent may do

With the default switches, your agent can read your games, edit the draft, upload art and builds, and start builds without asking. These defaults apply now. You can change them soon. Until then, price, A/B test and member changes ask you first. Going live always asks you, in the chat. It asks first before it deletes something for good or contacts people, such as a team invite.

Only you can set up payouts. On a game that is already live, only the owner can finish a web build or download.

Summer checks every agent call. A change Summer Games does not take from an agent yet comes back as `needs_approval` with a link for you.

## For agents

* Before a game goes live, call `summer_go_live` without `confirm`, show the owner the plan and ask. Call it with `confirm: true` only after they say yes. The game is live as soon as Summer's automatic checks pass; there is no review, so never tell the owner to wait for one.
* Any answer `needs_approval`: give the owner `approval.url`, then call `summer_jobs_wait` with `job.id` until it is `done`, `cancelled` or `stale`.
* If the job ends `stale`, read the current state again and ask again.
* `summer_store_status` shows every upload, what players get now, and any waiting request.

## Ask your agent

**Where is my game?** Your agent reads what is live and what waits for you. No changes.

Tell me where my game is on Summer Games. Use the Summer Engine MCP and read
my game with summer\_store\_status. Don't change anything.

Tell me: whether an approval is waiting for me (and give me its link), which
version players get on each platform, and whether the game is live.

***

Does this not help you? [Reach out on Discord!](https://discord.gg/summerengine)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.