Summer Apps

A Summer App is a tool for your game team that lives inside Summer Studio. Your agent builds it in minutes; your whole team uses it. Examples: a weapon balance table, an item and quest database, a loot table editor, a level progress tracker, a grid to pick the best of three sound effects, a live-ops view of your games. See Apps for game teams.

​

What an app is

​

Where apps live

• Studio > Apps lists your team’s apps in Pinned, Scratch, Team apps and Archived. Starter apps adds ready-made ones to your team: Pick one, Asset tracker, Balance table and Live ops.
• An app opens at summerengine.com/studio/apps/<appId>.
• New apps start in Scratch. Choose Keep in the app’s menu to move it to your team’s apps. A Scratch app nobody opens for 14 days is archived. You can restore it for 30 more days.
• Pin to sidebar puts an app in your Studio sidebar.
• In Summer Engine, apps open in the Studio tab. Docking an app next to your scene comes with the next Summer Engine update. See Engine and docks.

​

How to get one

Ask your agent: Claude Code, Codex, Cursor, Claude or ChatGPT with the Summer Engine MCP. Or describe it to Summer in Studio chat: choose Build a new app in Studio > Apps. Next: Build your first app.

​

Pages in this section

• Build your first app: the walkthrough for the person who asks.
• Build an app with your agent: the build loop, what breaks apps and prompts that work.
• Agents and apps: data as an API, agent tools, events and the MCP tools.
• SDK reference: window.summer inside an app, with exact types.
• Manifest: name, permissions, data collections, events and tools.
• Design kit: the UI kit and the rules that make apps look right.
• Engine and docks: apps that change your project. Coming with the next Summer Engine update.
• Security: what an app can and cannot do.
• Apps for game teams: economy balance sheet, item and quest database, weapon balance table, loot table editor, level progress tracker.