Skip to main content
Agents write app code, so Summer does not trust it. Safety comes from how apps run, not from pop-ups. Every control below is enforced by Summer’s servers or the browser, not by the app’s own code.

At a glance

The sandbox

  • A separate site. App files come only from apps.summerengine.app. Summer refuses to serve apps from a host that shares cookies with Summer Studio, so an app can never read your Summer session.
  • A sandboxed frame. Studio loads the app in a frame with sandbox="allow-scripts allow-forms allow-popups allow-modals allow-downloads", never allow-same-origin. Every app response carries the same sandbox in its Content-Security-Policy, so the page has no cookies or storage even when someone opens its URL directly.
  • A short-lived grant. The frame URL holds a signed grant for one app version and one person. It expires after 10 minutes, and Studio renews it while the app is open. A URL without a valid grant gets nothing.
  • A strict Content-Security-Policy. Scripts, styles and fonts load only from the app host. Images and media load only from the app host and Summer’s asset storage. connect-src is 'none' unless the team allows domains. Forms cannot post anywhere, and frame-ancestors names only Summer Studio.
  • No device access. Camera, microphone, location, payments, USB, serial, HID and Bluetooth are turned off for every app. Responses send no referrer.

What an app can reach

An app reaches Summer only through the SDK (window.summer), and only for what its manifest declares. The list of permissions and the calls each one opens is in the manifest and the SDK reference.
  • People see an app’s permissions on the app page under This app can.
  • A call the manifest does not allow fails with permission_missing. Summer checks this in the Studio page and again on the server.
  • A publish whose code calls something the manifest lacks goes through with checks, so the agent fixes the manifest before anyone uses the app.
  • team.members() never returns email addresses.
  • Calls are rate limited per person and app: 600 a minute, and 60 paid calls a minute.

Money

  • Paid calls (generations and ai.complete) spend the credits of the person using the app, never the app maker’s.
  • Members have a daily spending limit per app. A call over it fails with spend_cap_reached. Owners and admins have no limit and can change the members’ limit.
  • summer.app.viewer() returns what the person spent in the app today and their limit, so an app can show it.

Agents

  • Agents use the same rules as people: every apps.* operation runs as the signed-in person, with their team membership.
  • apps.delete asks the person to confirm, and apps.rollback and apps.update_starter ask the app’s owner. Nothing changes until they approve.
  • Your agent permissions in Summer Studio decide which other operations an agent may run without asking. See Agent permissions.

Switches

  • Owners and admins can turn off one app, or Summer Apps for the whole team. A turned-off app answers app_disabled (agents see forbidden) and its files are no longer served.
  • Summer can turn Summer Apps off for everyone at once in an emergency.
Found a security problem in Summer Apps? Tell us on Discord or at support@summerengine.com. For something sensitive, write to founders@summerengine.com.