Agent Setup

​

Point your agent at Summercraft

Fetch https://docs.summerengine.com/agent-setup/prompt.md and follow it exactly,
top to bottom. It is the canonical instruction set for building a multiplayer
Summer game in GDScript with Summer Engine and the Summer SDK, then publishing
it to Summercraft.

Context you need before you start:
- Summercraft (https://summercraft.ai) accepts Summer SDK games for review.
  The submission API lives at https://summercraft.ai/api/*; uploaded games are
  not playable on the platform yet.
- You will install and use Summer Engine, build a GDScript-only game that
  extends SummerGame, export a .pck with the Summer Engine binary, and publish it in four
  API calls: create game -> get presigned upload URL -> PUT the .pck ->
  finalize (the server re-verifies your sha256).
- Publishing needs a Summercraft access token in SUMMERCRAFT_ACCESS_TOKEN.
  Build and export first; stop and ask me for the token before the publish step.
  The prompt contains the instructions to show me for getting one.
- Each publish step is limited to 1 request per hour per account, so validate
  everything locally before touching the API.
- After finalize the release is "pending_review" in a manual human review
  queue. There is no auto-publish, and browser/desktop play of uploaded Summer
  games is not live yet - say so honestly when you report back.
- Any docs page is fetchable as raw markdown by adding .md to its URL; the
  index is at https://docs.summerengine.com/llms.txt.

If the prompt URL is unreachable, stop and tell me instead of improvising.

​

What the agent will do

1. Check prerequisites — Summer Engine for local validation/export, curl, a sha256 tool, and (only at publish time) your access token.
2. Build a multiplayer-native game — extends SummerGame, all gameplay authority on server paths, player state via set_synced, local SDK stubs so everything parses and smoke-runs without the platform runtime.
3. Validate locally — headless smoke run, banned-API self-check, pack-content check. The upload budget is 1/hour, so the prompt front-loads every check.
4. Export a game-only .pck — the preset excludes stubs and project config; ships GDScript as readable source.
5. Publish through the live API — create game → presigned upload → server-verified finalize. See Exporting and Uploading for the full reference.
6. Report honestly — release pending_review in the manual queue; approval changes its catalog status to published, but does not make it playable yet. Rejection comes with a reason on summercraft.ai/creator.

​

The one thing the agent cannot do: sign in

1. Sign up / sign in at summercraft.ai.
2. In that tab, open dev tools → Application → Cookies → summercraft.ai and find the cookie whose name ends in -auth-token (possibly chunked into .0/.1 — concatenate the values in order).
3. URL-decode the value; if it starts with base64-, base64-decode the rest. The JSON inside has an access_token field — that string is the Bearer token.
4. Hand it to your agent as the SUMMERCRAFT_ACCESS_TOKEN environment variable. It expires after about an hour — enough for one publish. Re-extract it when it expires.

​

Platform status

​

For agents reading this page directly