Frequently asked questions

From the Roblox Creator Store, and only from there. Public Studio installation is unavailable right now — Plugin availability says what that means. Roblox splits installation into two steps: you get the plugin on the web, then install it from inside Studio's Toolbox.

Retired. A file you drop into a folder by hand never updates, is not signed by anything, and gets no help from Studio's plugin management window. The Creator Store install is the supported path. Building the plugin yourself is still possible and documented under Build the plugin from source, but that is a development path, not an install path.

No, but it helps. Apple writes the Luau for you and explains anything it wrote in plain language (just ask it to explain what it wrote). Creators who can read a little code iterate faster, and plenty of people have learned scripting from Apple's explanations of its own work.

Yes: the Apple Discord server. Ask in #help, report bugs in #bug-reports, share your games in #showcase, and follow #changelog for every release. You can also link your account there and build with /build.

Current production Roblox Studio on Windows and macOS. The plugin uses only stable, documented Studio APIs, so ordinary Studio updates don't break it. If Roblox ships a breaking change, the changelog and the plugin panel will both say so.

No, by design. Apple builds inside your open place; publishing to Roblox stays a human decision made by you, in Studio, with your own account. Apple has no publishing permission over your account and does not ask for one.

There is one credential you can give it, and only if you want to: an Open Cloud API key, connected under Settings → Connections, which lets Apple upload images and audio it generates into your Roblox account instead of ours. It is stored encrypted, never shown again, used only for the permissions you ticked, and you can disconnect it at any time. What to do if Roblox refuses it.

Apple works on the place open in the paired Studio window. In Team Create sessions its edits appear to teammates like any collaborator's edits. One pairing belongs to one Studio window; teammates who want their own Apple chats should use their own accounts and projects.

The agent notices it lost its hands and pauses the run with a clear message. Work that never ran is never charged — Credits settle against the compute a call actually reported, and a call that did not happen reports nothing. Reopen the place, reconnect, and ask Apple to continue — the plan and history are still in the project.

Three exits, in order of size: press Ctrl+Z in Studio to take back the last change (one undo step per change Apple made, so a multi-step run needs one press per step); restore the automatic checkpoint taken before the run, which undoes the whole run in one action; or just tell Apple what you hate — it can usually fix a wrong turn faster than a rollback.

Yes. There is an HTTP API at /v1 on the same host as the app, with scoped keys: chat completions, your projects and their transcripts, starting an agent run, a server-sent event stream of run state, and a Model Context Protocol endpoint for MCP clients.

Mint a key under Settings → Connections → API keys in the app — you see the secret once, and you can rotate or revoke it from the same panel. The surface documents itself: GET /v1 lists every route and the scope it needs, and GET /v1/openapi.json is the machine-readable description. Both accept any valid key. There is no separate docs page for it yet, and no published client library — the API is the thing that exists.

Email apple.labs.app@gmail.com. Include the project name and roughly when it happened; screenshots welcome. Feedback lands directly with the people who build the product — there is no ticket abyss.